From: Daniel Stekloff <dsteklof@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Patrick Mochel <mochel@osdl.org>, Greg KH <greg@kroah.com>
Subject: [ANNOUNCE] libsysfs v0.1.0
Date: Mon, 7 Jul 2003 10:55:08 +0000 [thread overview]
Message-ID: <200307071055.08175.dsteklof@us.ibm.com> (raw)
I'd like to announce libsysfs - a small library built over sysfs, the virtual
filesystem that exports system devices in the Linux 2.5+ kernels. You can
find the initial version of the library in a small package called sysutils
at:
kernel.org/pub/linux/utils/kernel/hotplug/sysutils-0.1.0.tar.gz
The library grew from the requirements of several applications all needing
access to system device information in sysfs. We felt it was better to
provide a library of common code rather than having each application create
their own access. Greg KH's udev application, a User Space replacement for
devfs, is one of the applications needing sysfs access. You can see Greg's
original announcement here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105003185331553&w=2
The library doesn't implement any device or bus specifics but simply provides
generic bus, class, and device access as represented in sysfs. Included with
the library in the sysutils package are two small commands that hopefully
make viewing sysfs and system device information easier.
- systool is a command that can list devices by bus, by class, or by device
root - as represented through sysfs. Here's example output showing all
devices off root device pci2, children are indented following each device:
[stekloff@... stekloff]$ systool -r pci2
Root Device Tree: pci2
pci2 Host/PCI Bridge
02:01.1 Adaptec AIC-7899P U160/m (#2)
host1 aic7xxx
1:0:8:0 SCSI Processor
1:0:8:0:gen SCSI Processorgeneric
1:0:0:0 SCSI Direct-Access
1:0:0:0:gen SCSI Direct-Accessgeneric
02:01.0 Adaptec AIC-7899P U160/m
host0 aic7xxx
- lsbus is a small command for simply viewing sysfs bus information. Here's
example output showing all PCI drivers and their devices:
[stekloff@... stekloff]$ lsbus -D pci
Bus: pci
Drivers:
aic7xxx
Devices:
02:01.0
02:01.1
RZ1000 IDE
PIIX IDE
eepro100
pcnet32
Devices:
00:05.0
serial
agpgart-via
agpgart-sis
agpgart-intel
agpgart-amdk7
agpgart-ali
All comments, suggestions, and contributions are welcome.
Thanks,
Dan
next reply other threads:[~2003-07-07 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 10:55 Daniel Stekloff [this message]
2003-07-07 18:40 ` [ANNOUNCE] libsysfs v0.1.0 Horst von Brand
2003-07-07 19:12 ` 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=200307071055.08175.dsteklof@us.ibm.com \
--to=dsteklof@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/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