From: "J.A. Magallon" <jamagallon@able.es>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 011 release
Date: Sun, 28 Dec 2003 03:04:49 +0100 [thread overview]
Message-ID: <20031228020449.GA26527@werewolf.able.es> (raw)
In-Reply-To: <20031225005614.GA18568@kroah.com> (from greg@kroah.com on Thu, Dec 25, 2003 at 01:56:14 +0100)
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))
next prev parent reply other threads:[~2003-12-28 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 0:56 [ANNOUNCE] udev 011 release Greg KH
2003-12-28 2:04 ` J.A. Magallon [this message]
2003-12-28 2:19 ` Rob Love
2003-12-29 22:48 ` 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=20031228020449.GA26527@werewolf.able.es \
--to=jamagallon@able.es \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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