Red Hat Bugzilla – Bug 53973
creating lilo.conf within kickstarting fails
Last modified: 2007-04-18 12:37:19 EDT
Description of Problem:
I'm just sitting some hours to find a maybe curious error: I did
kickstarting some RH dists with creating a customized lilo.conf; but with
roswell there is something wrong:
Within the %post section I try to write a new /etc/lilo.conf after trying
to move the rh one away:
# create a better (customized) /etc/lilo.conf
mv $FILE $FILE.orig
cat << EOT | sed 's/X//' > $FILE
X# $FILE of $HOSTNAME
X# end of file.
chmod 600 $FILE ; /sbin/lilo
rm -f /boot/boot.[0-9]*
But on VC3 I only can read /etc/lilo.conf: No such file or directory ??????
although there are some lilo.conf files within /mnt/sysimage/etc:
/mnt/sysimage/etc/lilo.conf (the kickstart one concatenated with the one
/mnt/sysimage/etc/lilo.conf.rpmsave (the customized on)
Could you please - I think it's an anaconda specific issue - give me a hint
what's going on here? We don't want to use grub in the future because we
trust the old lilo more. If it's an anaconda error, please fix that bug.
I think lilo or grub have to do all their work before entering the %post
section, otherwise you've changed the definition of the %post section of the
%post was mistakenly occurring prior to the boot loader installation... already
fixed in cvs
is the cvs accessible to the public yet?