[RFC] LFS profile textdump-to-config conversion

Kevin P. Fleming kpfleming at linuxfromscratch.org
Sun Feb 6 17:05:16 PST 2005


Here is the list of files that the LFS profile creates that are 
candidates for extraction from the XML and placement into a distributed 
"template" directory:

/etc/fstab
/etc/group
/etc/hosts
/etc/inittab
/etc/inputrc
/etc/kbd/bs-sends-del
/etc/ld.so.conf
/etc/modprobe.conf
/etc/nsswitch.conf
/etc/passwd
/etc/profile
/etc/resolv.conf
/etc/sysconfig/clock
/etc/sysconfig/console
/etc/sysconfig/network-devices/ifconfig-eth0/ipv4
/etc/sysconfig/network
/etc/syslog-ng/syslog-ng.conf
/etc/vimrc
/home/lfs/.bash_profile
/home/lfs/.bashrc
/boot/grub/menu.lst

A great many of these files are composed at runtime from static text and 
entities provided via general.ent. What I'm proposing would eliminate 
the need for those entities to even exist, in preference to just telling 
the user that the entire "template" exists in the profile in the 
'skeleton' directory and that they should review and edit the contents 
of that subtree before running the profile, just as they would if they 
were building LFS by hand.

The list of entities that would be removed from general.ent would be:

broadcast
domain
fs_type
gateway
grub-install-location
grub-root
hostname
lfs_partition
locale_country
locale_language
nameserver-ip
network-card-module
network-interface
on_boot
prefix
swap_partition
IP
UTC

All of these entities are present in the profile _only_ so they can be 
used to create the config files when the profile is executed; if the 
user just places the values directly into the skeleton files, the 
entities will not be needed.

There are two issues that I'm aware of:

- Currently the grub menu.lst file gets built incorporating the 
"LFS-version" and "linux-version" entities, but that would no longer be 
the case. The simple solution is to manually update the skeleton 
menu.lst file whenever these entities are changed in general.ent, but 
that's a maintenance burden. The _simpler_ solution is to just stop 
incorporating the version info into menu.lst, but that's not as helpful 
to the end user.

- This is a pretty major change to the profile's configuration system, 
so we will all need to be prepared for the support changes needed when a 
profile with this new system is released.



More information about the alfs-discuss mailing list