From: devzero@web.de
To: Tomas Carnecky <tom@dbservice.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Show module version sysfs file for built-in modules?
Date: Wed, 29 Jul 2009 20:40:39 +0200 [thread overview]
Message-ID: <844950876@web.de> (raw)
what about this ?
neoware:/sys/module/8139too # cat /sys/module/8139too/version
0.9.28
neoware:/sys/module/8139too # modinfo 8139too |grep "^version:"
version: 0.9.28
the latter should work completely without consulting the kernel for that information.
regards
roland
>List: linux-kernel
>Subject: Show module version sysfs file for built-in modules?
>From: Tomas Carnecky <tom () dbservice ! com>
>Date: 2009-07-24 19:08:51
>Message-ID: 5A77D882-B628-4105-85A3-ADE423BBD9F8 () dbservice ! com
>[Download message RAW]
>
>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)
vwhich checks /sys/modules/scsi_transport_iscsi/version and refuses to
>start if that file doesn't exist.
>
>thanks
>tom
________________________________________________________________
Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate
für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/02/
next reply other threads:[~2009-07-29 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 18:40 devzero [this message]
2009-07-29 19:08 ` Show module version sysfs file for built-in modules? Alan Jenkins
-- strict thread matches above, loose matches on Subject: below --
2009-07-29 21:48 devzero
2009-07-24 19:08 Tomas Carnecky
2009-07-29 5:23 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=844950876@web.de \
--to=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@dbservice.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox