* Re: [ANNOUNCE] udev 011 release
2003-12-25 0:56 [ANNOUNCE] udev 011 release Greg KH
@ 2003-12-28 2:04 ` J.A. Magallon
2003-12-28 2:19 ` Rob Love
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: J.A. Magallon @ 2003-12-28 2:04 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ANNOUNCE] udev 011 release
2003-12-25 0:56 [ANNOUNCE] udev 011 release Greg KH
2003-12-28 2:04 ` J.A. Magallon
@ 2003-12-28 2:19 ` Rob Love
2003-12-28 2:19 ` Rob Love
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Rob Love @ 2003-12-28 2:19 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ANNOUNCE] udev 011 release
2003-12-25 0:56 [ANNOUNCE] udev 011 release Greg KH
2003-12-28 2:04 ` J.A. Magallon
2003-12-28 2:19 ` Rob Love
@ 2003-12-28 2:19 ` Rob Love
2003-12-28 2:19 ` Rob Love
2003-12-29 22:48 ` Greg KH
4 siblings, 0 replies; 6+ messages in thread
From: Rob Love @ 2003-12-28 2:19 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ANNOUNCE] udev 011 release
2003-12-25 0:56 [ANNOUNCE] udev 011 release Greg KH
` (2 preceding siblings ...)
2003-12-28 2:19 ` Rob Love
@ 2003-12-28 2:19 ` Rob Love
2003-12-29 22:48 ` Greg KH
4 siblings, 0 replies; 6+ messages in thread
From: Rob Love @ 2003-12-28 2:19 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ANNOUNCE] udev 011 release
2003-12-25 0:56 [ANNOUNCE] udev 011 release Greg KH
` (3 preceding siblings ...)
2003-12-28 2:19 ` Rob Love
@ 2003-12-29 22:48 ` Greg KH
4 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2003-12-29 22:48 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 6+ messages in thread