linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 011 release
Date: Sun, 28 Dec 2003 02:04:49 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107258905725950@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107231392813609@msgid-missing>


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

  reply	other threads:[~2003-12-28  2:04 UTC|newest]

Thread overview: 6+ 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-28  2:19 ` Rob Love
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=marc-linux-hotplug-107258905725950@msgid-missing \
    --to=jamagallon@able.es \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).