lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <5A77D882-B628-4105-85A3-ADE423BBD9F8@dbservice.com>
Date:	Fri, 24 Jul 2009 21:08:51 +0200
From:	Tomas Carnecky <tom@...ervice.com>
To:	linux-kernel@...r.kernel.org
Subject: Show module version sysfs file for built-in modules?

Some userspace tools check /sys/modules/XYZ/version to determine  
whether the required module is available and the version compatible  
with the userspace tool. But that sysfs file is not shown when the  
module is built into the kernel (as opposed being a loadable module).  
Is there a reason for that behavior? Or is there another way for  
userspace to check the presence and version of a module?
The userspace tool in question here is the open-iscsi daemon (iscsid)  
which checks /sys/modules/scsi_transport_iscsi/version and refuses to  
start if that file doesn't exist.

thanks
tom

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ