Matthew Burgess wrote:
Alexander E. Patrakov wrote:
2) There is no "udev_retry" initscript. The idea is that, if a program
specified in the "RUN" rule exits with nonzero status (presumably
because it needs /usr), udev places a symlink into /dev/.udev/failed.
The udev_retry initscript should run after mountfs and re-trigger the
failed uevents in hope that they won't fail again.
I really don't think this is necessary. Folks should be knowledgable
enough to realise that calling out to anything on a non / partition may
fail before the mountfs script has run, if /usr is on a separate
partition of course. Obviously, if there are other cases where a rule
may initially fail,
Think about ALSA: alsactl is in /usr/sbin. BLFS currently uses a
compilcated loop (that wasn't even done correctly from the first try!),
while linux-hotplug-devel prefers to solve this with the udev_retry
bootscript. The .udev/failed directory was invented specifically for
this purpose.
3) Linux-2.6.15 is used, which means that some deices (e.g., IDE
CD-ROMs and input devices) won't get modaliases or won't generate
uevents properly.
There is already a note in the book concerning how to handle devices
whose drivers don't work correctly under udev (i.e.
/etc/sysconfig/modules, etc.).
There are no words about what should and what should not be expected to
work. I will provide them later.
Issue with "more than one CD-ROM" also exists, but has no clear
upstream solution (they say: dynamically generate rules for persistent
CD-ROM naming, but provide no implementation).
Ewww, how does one dynamically generate udev's rules file so early on in
the boot process (no, I don't want an initramfs!).
They say that one should make a rule that is called when an unknown
CD-ROM drive is encountered, and runs a shell script that writes a new
file with one rule specifically for this CD-ROM. This rule should
specify a unique symlink and GOTO past that catch-all "unknown CD-ROM" rule.
OTOH, I would be happy with the following:
/dev/cdroms/SAMSUNG_CD-ROM_SC-148F
/dev/cdroms/PHILIPS_CDD5301_5VO1306DM00190
(these are results of running the ata_id program on my CD-ROMs).
Or even with HAL, that actually creates the mount points and fstab
entries for both my CD-ROMs.
ACTION=="add", SUBSYSTEM=="firmware", RUN+="/sbin/firmware_helper"
/sbin/firmware_helper: No such file or directory
11) The deprecated udev_run_hotplugd helper is needed for
compatibility with BLFS (look at HAL).
Why? I thought Kay was actively helping the HAL guys out? Why has he
caused it to break by deprecating the udev_run_hotplugd helper?
That's just obsolete BLFS setup. HAL is able to work without the
hotplug.d hook, but BLFS doesn't configure it to work this way.
make EXTRAS="`echo extras/*/`"
instead of explicitly listing extras.
I'd rather not, as it'll install at least the dasd helper which is
useless on anything other than s390 boxes as far as I can tell.
The "iseries" rules in our file are also useless on anything other than
s390 boxes.
13) The need for persistent device naming is not explained (Ticket #1672)
OK, if you could come up with some suggested text it may get fixed
quicker :-)
Will do that later today or tomorrow. Should it go under "device and
module handling", under "configuring the network script", or split
between both? My preference is to split.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
