[ANNOUNCE] udev 011 release

[ANNOUNCE] udev 011 release

[Greg KH]

I've released the 011 version of udev.  It can be found at:
 	kernel.org/pub/linux/utils/kernel/hotplug/udev-011.tar.gz

rpms built against Red Hat FC1 are available at:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-011-1.i386.rpm
with the source rpm at:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-011-1.src.rpm

udev is a implementation of devfs in userspace using sysfs and
/sbin/hotplug.  It requires a 2.6 kernel to run.  Please see the udev
FAQ for any questions about it:
	kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ

The major changes since the 010 release are:
	- The _long_ time delay on startup if you used the udev init
	  script is now gone.  We now fork a new process of udev for
	  every device in the sysfs tree, causing any slow udev proceses
	  (due to the type of device) to be not noticeable by the user.

	- The RPM package is built against klibc.  If you have any
	  problems with this image, please let me know.

	- The big "always wait 1 second" problem with the 010 release is
	  now pretty much fixed.  I still need some libsysfs changes to
	  work around some of the delays I had to hard code in, but for
	  any device that is not a partition, and has a "device"
	  symlink, udev will not sleep at all.  If a device does not
	  have a "device" symlink, we will wait around for a few seconds
	  to see if one is going to be created or not, and then move on.
	  It's the only sane way of handling the issue of not knowing
	  what kinds of devices have symlinks and which ones do not.

	- fixed a few bugs when devices did not have a "device" symlink.
	  Rules were getting applied when they should not have been.

	- LABEL and CALLOUT rules now no longer require the BUS key.  If
	  the BUS key is not present, the LABEL or CALLOUT rule will be
	  always be checked.  This allows us to use these types of rules
	  for devices without a "device" symlink.

	- a few other minor tweaks and bug fixes too.

Thanks again to everyone who has send me patches for this release, a
full list of everyone, and their changes is below.

udev development is done in a BitKeeper repository located at:
	bk://linuxusb.bkbits.net/udev

Daily snapshots of this tree used to be found at:
	http://www.codemonkey.org.uk/projects/bitkeeper/udev/
But that box seems to be down now.  Hopefully it will be restored
someday.  If anyone ever wants a tarball of the current bk tree, just
email me.

It's time to go cook the Tofurky...

thanks,

greg k-h

Summary of changes from v010 to v011
======================

<mbuesch:freenet.de>:
  o proper cleanup on udevdb_init() failure

<mh:nadir.org>:
  o patch udev 009-010 rpm spec file

<svetljo:gmx.de>:
  o fix udev sed Makefile usage

Greg Kroah-Hartman:
  o add documentation about the BUS key being optional for the LABEL rule
  o add tests for LABEL rule with a device that has no bus
  o Don't require the BUS value for the LABEL rule
  o If a LABEL rule has a BUS id, then we must check to see if the device is on a bus
  o add documentation about the BUS key being optional for the CALLOUT rule
  o If a CALLOUT rule has a BUS id, then we must check to see if the device is on a bus
  o Don't require the BUS value for the CALLOUT rule
  o add test for callout rule with a device that has no bus
  o 010_bk stamp
  o added different build options to the rpm udev.spec file
  o add pci to the bus_files list
  o check for empty line a bit better in the parser
  o more init script cleanups, the stop target now calls udev to cleanup instead of just removing the whole /udev directory
  o make udev init script run udev in the background to let startup go much faster
  o fix long delay for all devices in namedev
  o v010 release TAG: v010



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [ANNOUNCE] udev 011 release

[J.A. Magallon]

On 12.25, Greg KH wrote:
> I've released the 011 version of udev.  It can be found at:
>  	kernel.org/pub/linux/utils/kernel/hotplug/udev-011.tar.gz
> 

udev rc script reads:

# chkconfig: 2345 20 80

If it is supposed to create device nodes on an empty /dev, I think it should
be run at runlevel 1, or even run apart from normal initscripts, from rc or
the like ?
For example, on a Mandrake cooker box, rc2.d looks like


K05portsentry@  K35dhcpd@       K80gmond@                   S12syslog@
K08lircmd@      K35lircd@       K80nscd@                    S15gpm@
K09dm@          K44rawdevices@  K81ganglia-monitor-script@  S18sound@
K09smb@         K45named@       K86nfslock@                 S20random@
K10devfsd@      K50xinetd@      K89portmap@                 S20udev@
K10ntpd@        K54pxe@         K89upsmon@                  S60cups@
K10xfs@         K60atd@         K90upsd@                    S60nfs@
K15proftpd@     K60saslauthd@   K95harddrake@               S75keytable@
K20bootparamd@  K65identd@      S01hotplug@                 S80postfix@
K20partmon@     K70acpi@        S03iptables@                S90crond@
K21bpmaster@    K70alsa@        S05lm_sensors@              S95kheader@
K25sshd@        K75netfs@       S05sensors@                 S95microcode_ctl@
K35atalk@       K80gmetad@      S10network@                 S99local@

This means that it will try to run, for example, gpm before the device for
the mouse is created (as I said, if you booted with an empty /dev you want
to populate with device nodes).

And a couple questions.
a) Should not ordering be reversed here:

  start)
    if [ ! -d $udev_dir ]; then
        mkdir $udev_dir
    fi
    if [ ! -d $sysfs_dir ]; then
        exit 1
    fi
  If we have not /sys, there's no sense on creating /udev, so I would check first
  for /sys.

b) What is the sense of removing devices when udev is stopped ? As I understand
  it, udev is not 'running', it is just a command to create device nodes, called 
  by hotplug. What is more logical, chkconfig --level 12345 or --level 1 ?
  One more reason to split it from normal init scripts. 

TIA

-- 
J.A. Magallon <jamagallon()able!es>     \                 Software is like sex:
werewolf!able!es                         \           It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.6.0-jam1 (gcc 3.3.2 (Mandrake Linux 10.0 3.3.2-3mdk))


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [ANNOUNCE] udev 011 release

[Rob Love]

On Sat, 2003-12-27 at 21:04, J.A. Magallon wrote:

> This means that it will try to run, for example, gpm before the device for
> the mouse is created (as I said, if you booted with an empty /dev you want
> to populate with device nodes).

Yah, I guess it ought to go lower, so long as sysfs is sufficiently
mounted before it runs.

The reason I put it at 20 was that it really does not matter.  udev is
not a functional replacement for a static /dev while we do not have
initramfs.  Once we have udev working during early boot, we won't need
the initscripts.

> And a couple questions.
> a) Should not ordering be reversed here:
> 
>   start)
>     if [ ! -d $udev_dir ]; then
>         mkdir $udev_dir
>     fi
>     if [ ! -d $sysfs_dir ]; then
>         exit 1
>     fi
>   If we have not /sys, there's no sense on creating /udev, so I would check first
>   for /sys.

Makes sense.

> b) What is the sense of removing devices when udev is stopped ? As I understand
>   it, udev is not 'running', it is just a command to create device nodes, called 
>   by hotplug.

Because if you have your udev on a persistent storage media (e.g., ext3,
like most of us) then it is nice to clear it out across reboots.

	Rob Love




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [ANNOUNCE] udev 011 release

[Rob Love]

On Sat, 2003-12-27 at 21:04, J.A. Magallon wrote:

> This means that it will try to run, for example, gpm before the device for
> the mouse is created (as I said, if you booted with an empty /dev you want
> to populate with device nodes).

Yah, I guess it ought to go lower, so long as sysfs is sufficiently
mounted before it runs.

The reason I put it at 20 was that it really does not matter.  udev is
not a functional replacement for a static /dev while we do not have
initramfs.  Once we have udev working during early boot, we won't need
the initscripts.

> And a couple questions.
> a) Should not ordering be reversed here:
> 
>   start)
>     if [ ! -d $udev_dir ]; then
>         mkdir $udev_dir
>     fi
>     if [ ! -d $sysfs_dir ]; then
>         exit 1
>     fi
>   If we have not /sys, there's no sense on creating /udev, so I would check first
>   for /sys.

Makes sense.

> b) What is the sense of removing devices when udev is stopped ? As I understand
>   it, udev is not 'running', it is just a command to create device nodes, called 
>   by hotplug.

Because if you have your udev on a persistent storage media (e.g., ext3,
like most of us) then it is nice to clear it out across reboots.

	Rob Love




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [ANNOUNCE] udev 011 release

[Rob Love]

On Sat, 2003-12-27 at 21:04, J.A. Magallon wrote:

> This means that it will try to run, for example, gpm before the device for
> the mouse is created (as I said, if you booted with an empty /dev you want
> to populate with device nodes).

Yah, I guess it ought to go lower, so long as sysfs is sufficiently
mounted before it runs.

The reason I put it at 20 was that it really does not matter.  udev is
not a functional replacement for a static /dev while we do not have
initramfs.  Once we have udev working during early boot, we won't need
the initscripts.

> And a couple questions.
> a) Should not ordering be reversed here:
> 
>   start)
>     if [ ! -d $udev_dir ]; then
>         mkdir $udev_dir
>     fi
>     if [ ! -d $sysfs_dir ]; then
>         exit 1
>     fi
>   If we have not /sys, there's no sense on creating /udev, so I would check first
>   for /sys.

Makes sense.

> b) What is the sense of removing devices when udev is stopped ? As I understand
>   it, udev is not 'running', it is just a command to create device nodes, called 
>   by hotplug.

Because if you have your udev on a persistent storage media (e.g., ext3,
like most of us) then it is nice to clear it out across reboots.

	Rob Love




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [ANNOUNCE] udev 011 release

[Greg KH]

On Sun, Dec 28, 2003 at 03:04:49AM +0100, J.A. Magallon wrote:
> 
> And a couple questions.
> a) Should not ordering be reversed here:
> 
>   start)
>     if [ ! -d $udev_dir ]; then
>         mkdir $udev_dir
>     fi
>     if [ ! -d $sysfs_dir ]; then
>         exit 1
>     fi
>   If we have not /sys, there's no sense on creating /udev, so I would check first
>   for /sys.

Care to send a patch?  :)

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel