-snip lengthly messages-
Hi all,
I have been following this thread and I have a suggestion that I believe
to be a good compromise.
When installing the Udev package in LFS, add a file called 99default to
the /etc/udev/rules.d directory which basically just puts all the
devices in their default/recommended/etc directory (eg alsa devices into
/dev/snd) with the default udev user/group/permissions. Then add a file
(eg 25lfs-basic) which sets the recommended/needed
user/group/permissions for a basic LFS install. In BLFS, users, groups
and a rule file can be added as needed.
The 99default file should probably contain any device encountered with
linux on any arch (within reason) so that no modifications are necessary
to use it with the multiarch books.
This has the following advantages that I can see:
- Gives the user an educational experience with setting up of device
owner, group and permissions
- Requires little in the way of maintainence as the 99default should
not need to be modified at all once setup properly
- Tweaking can be done to the rule files added by LFS/BLFS without
breaking Udev too much (for some reason my last LFS install had broken
udev rules...)
- A basic install of LFS will be relatively functional (apart from
device permissions/groups/users) with the device files where programs
(and me) expect them to be. A simple chmod can be used to make the
devices functional in the short term (ie, playing music via statically
linked mplayer while installing base packages for X / Multimedia etc).
- LFS can remove any users and groups that are not necessary for a
basic install
- BLFS has leeway to add users and groups and rules files without
needing to worry too much about breaking devices or modifying files
added by LFS
- The /dev tree is clean and usable as is (relatively) at first boot
even without touching any files after installing LFS.
- Device nodes for any hardware that has kernel drivers would be in the
correct place in the /dev tree so that (as root) no modifications are
needed to get the system up and running (anyone ever encountered a
package that didn't expect the alsa devices to be as /dev/snd/pcm0?)
Any suggestions, comments, counter-arguments, flames etc are welcome :)
Emu
(I can't believe that I need to shutdown half of Norton internet
security to send an email via tls...)
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
