Several udev questions

[Ondrej Zajicek <santiago@mail.cz>]

[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]

Hello

I installed latest udev (091). It works nice, loading of all needed
modules took ~8 sec (old hotplug system took ~30 sec, udev 056 ~18 sec,
without any hotplug mechanism ~3 sec) and i have several questions and
notes:

1) When i start system, i mount /dev, started udevd and udevtrigger. I
don't explicitly copy (from /lib/udev/devices) or create any device
nodes. It looks like all needed nodes are created in this way, although
documentation (README) suggests copying some nodes before udevd start.
What is the correct way - is the documentation obsolete, or am i miss
something important?

2) What is recommended time of start of udevd? I think it should be
started early during boot process (i run it just after remounting root
to rw) to create all needed devices. But if i want to do logging, i have
to start syslogd before ulogd. But it is usually expected to run syslogd
more late, especially after mounting of other filesystems from fstab (in
case of /var on separate partition).

Maybe there should be something like kernel's dmesg buffer to store ulogd
messages generated before start of syslog.

3) When i insert CF (and other) media with partition table, there is no
hotplug event (for new partitions). I found some hacks like adding all
possible partitions for that devices. Is the correct solution for this
problem that kernel should send hotplug events in that case?

3) example configuration in /etc/udev/slackware has KERNEL= instead of
KERNEL==

4) MODE=644 for event devices (in /etc/udev/frugalware/udev.rules)
is pretty crazy.

5) What is a good place to load useful, subsytem specific but not
dependent modules like sd_mod for SCSI disks, lp for parport devices,
snd_pcm_oss for soundcards?

 - in /etc/modules or something similar?
   disadvantage - not very hot-plug.

 - In module-init-tools (modprobe) configuration as install rule?
   disadvantage - as there is no concept of subsystem membership so there
   have to be one rule for one specific hardware driver, not one for class
   of drivers.

 - in udev.rules file?

I am not in mailing list so please cc me.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@mail.cz, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]