Discussion required on future lfs-bootscript fixes
conathan at conet.dyndns.org
conathan at conet.dyndns.org
Mon Nov 24 16:22:38 MST 2003
I was poking around bug 325, and there seems to be a few fixes forgotten
over the ages. (I could make patches for the following, but I'm not sure
if I would be able to test them out to see if they work right, or dont
haev sufficient knowledge to know if it's the right fix).
Just wanted some input here.
Comment #1
When collecting K* links, there's a bug that causes you not being able to use
more than two digits for the links, else you'll get errors that there is not
corresponding S* link in the previous level.
[fix on comment#2, but probably better just if you cant find the file,
look for 3 digit]. Then again, using multiple digits on the start/stop
scripts could cause problems...
Comment #3
add the -d option to mountfs's umount command to free up loop devices.
As far as I can tell, this shouldnt cause any problems...
Comment #4
Write more docs regarding usage of the scripts, especially the network
script's ability to use /etc/sysconfig/network-devicese/ifup-devicename
script to do the work rather than the default ifconfig command run by the
ifup script (same for ifdown-devicename)
Sounds simple enough, make a README file?
Comment #6
update for cleanfs:
find /var/run -not -type d -exec rm {} \;
[There was a script on comment 13 which didnt use find, probably easy
enough to drop in]
Comment #8
If you use a serial console "stty size" (line 16) always reports "0 0".
Also postes what seems to be a good fix,
Comment #12
setting domainname
Seems simple enough, but there may be a resason this was not added in the
first place
Comment #14
Make scripts compliant with ash,
seems to mostly replace the word source with a simple execution of a file,
but that rc file in /etc/sysconfig is not executable... [and scripts may
have changed over the year (well, maybe not)].
More information about the lfs-dev
mailing list