Alexander E. Patrakov wrote:
Matthew Burgess wrote:
Alexander E. Patrakov wrote:
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.
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.
OK, thanks. One udev_retry script coming up!
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.
Rather than doing that, we could always just hold off on merging the
udev_update branch until linux-2.6.16 is released. Those trying out the
branch know (or should do!) that it might lead to breakage.
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).
>
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).
Hmm, how does cdrom_id differ, if at all? That way we'd cope with both
SCSI and ATA CD-ROMS, right?
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
Err, yes, I meant /lib/udev/firmware_helper of course!
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.
Then it's a BLFS issue. Granted, before this branch was developed, they
couldn't be expected to know about the issue. Alexander, would you mind
getting a patch ready to apply to BLFS once the udev_update branch is
merged to trunk? Bruce, would you accept such a patch?
The "iseries" rules in our file are also useless on anything other than
s390 boxes.
OK, those rules are gone too.
13) The need for persistent device naming is not explained (Ticket
#1672)
Should it go under "device and
module handling", under "configuring the network script", or split
between both? My preference is to split.
The split sounds best, though of course we can see what it looks like
and decide for definite then.
Thanks again for your help Alexander.
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
