[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New LILO version, was Re: Woody upgrading problems, LILO and debconf



On Friday 25 May 2001 15:22, Dale Scheetz wrote:
> > Well the way it effectively operates is to just ask if you want to
> > install a boot block with the new lilo.
>
> It isn't clear to me that I would ever want to do that on an upgrade ;-)

Well in the past the boot.b files got replaced and you'd want to do that if 
you wanted to boot again...

> > Someone made the really good suggestion of having the boot.b type files
> > in /usr/lib/lilo (or some such directory) and have them copied in when
> > the lilo command is run.
>
> Why does boot.b need to be replaced, and how does this relate to the mbr
> issues?

boot.b needs to match the version of lilo, otherwise it can't be installed.

> >                 If I implement that suggestion then I will make it not
> > run liloconfig on postinst unless there is no /etc/lilo.conf.
>
> My /etc/lilo.conf is a symlink to /boot/lilo.conf, which is a separate
> partition used by several root filesystems. I would suggest you do the
> following in the postinst script:
>
> if [ "$1" != "upgrade" ] ; then
>   liloconfig
> else
>   echo "<some message about running lilocnfig>"
> fi
>
> then the rest of the installation details need not be known or accounted
> for, and are left to the sysadmin.

That's something to consider.

-- 
http://www.coker.com.au/bonnie++/     Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/       Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/     My home page



Reply to: