On Sat, Nov 20, 2004 at 01:21:16AM -0600, Ron Johnson wrote:
> On Sat, 2004-11-20 at 01:57 -0500, Kevin Mark wrote:
> > On Fri, Nov 19, 2004 at 08:55:42PM -0600, Ron Johnson wrote:
> > > On Fri, 2004-11-19 at 19:32 -0700, Jamin W. Collins wrote:
> > > > On Fri, Nov 19, 2004 at 02:43:31PM -0500, Christian Convey wrote:
> > > > > Hey guys,
> > > > >
> > > > > I'm considering installing the 'udev' package as part of my Sarge 2.6
> > > > > installation. My motivation is that I'm often baffled when trying to
> > > > > figure out which USB device is associated with USB devices I plug in.
> > > > >
> > > > > Is there a general concensus about whether udev makes life better or worse?
> > > >
> > > > Don't know about a "general concensus" but I'm quite happy with udev's
> > > > operation and having consistent device names for my USB and Firewire
> > > > devices.
> > >
> > > What kind of names? Can you give some examples? When I insert
> > > a pen drive, for example, /var/log/syslog says that it is /dev/sdc1
> > > instead of something devfs-like /dev/usb/port01/drive01/part01.
> > >
> > > --
> >
> > in udev.rules I have:
> > BUS="usb" , KERNEL="sd?1",SYSFS_serial="07381C501259, NAME="usbkey"
> > I then can:
> > mount /dev/usbkey /mnt/usbkey
> > or some other magic for automounting.
>
> Ok. Where does the SYSFS_serial come from?
>
> And are you missing a closing parenthesis on SYSFS_serial?
yup. opps.
I googled for udev. here is one way using the udev tools:
<bash>
find /sys| while read line; do
echo $line;
udevinfo -a -p $line;
done
</bash>
this will spit out lots of info. Udev creates a new file system: /sys.
its like /proc, it takes up no space and its contains information.
-Kev
--
counter.li.org #238656 -- goto counter.li.org and be counted!
(__)
(oo)
/------\/
/ | ||
* /\---/\
~~ ~~
...."Have you mooed today?"...
Attachment:
signature.asc
Description: Digital signature