Herbert, I am confusedi by your comment. (I know you know better but it does not make sense to me.)
On Sun, Feb 03, 2002 at 09:39:39AM +1100, Herbert Xu wrote: > Osamu Aoki <[EMAIL PROTECTED]> wrote: > > >> > # cd /etc; mv fstab fstab.old > >> > # sed 's/ext2/ext3,ext2/g' <fstab.old >fstab # forged to be better :) > >> > >> mkinitrd -o /boot/initrd.img-2.4.17-686-smp /lib/modules/2.4.17-686-smp > >> lilo > > > It does not harm but kernel-image already comes with initrd image and it > > runs lilo during "install". Is there any specific reason why this > > command needs to be run again? > > Because you've changed fstab which contains the root filesystem type... I did not remount. So root FS is still ext2 until reboot. Besides, file location of all files (kernel image, initrd image is stationally) I thought lilo care only physical location. That is the reason behind why it can put kernel image in DOS partition. > You could also simply reinstall kernel-image of course. I did install kernel-image before editing fstab. Is not it enough? I greped source of lilo and I only see "fstab" in configuration scripts (liloconfig, lilo_find_mbr) which are not used and will not be affected by my fstab edit. I am sorry to bug you :-( (I think my system is working fine by the process I described.) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
