Bug#31778: lilo config segfaults in 2.1.4
On Wed, Jan 13, 1999 at 09:39:11PM -0500, Adam Di Carlo wrote:
> On Tue, 12 Jan 1999 09:40:11 +0100, Bernd Eckenfels <ecki@lina.inka.de> said:
> > I guess this is a boot floppy bug, liloconfig from the lilo package
> > is not called on fresh system installs. Its a shallscript. (cant
> > segfault)
>
> It seems to me that lilo configuration is one of the biggest sore
> spots of the installation process, *especially* for those who have
> dual-boot setups.
>
> I don't know if this is an x86-only problem -- I suspect it is.
>
> Hopefully someday we'll be able to move to grub, for x86 at least.
> This can boot the hurd too. But what is our strategy about this for
> slink?
There has been a thread about this recently on debian-hurd. The
conclusion was that the GRUB is not ready to replace LILO (yet). The main
show-stopper is its hard config style. There's work in progress on a
grubinst probgram but is far from finished. We may look at it again on
potato.
Also there's work in progress on an improved liloconfig on the lilo
package. We may as well use that for potato instead of our dbootstrap
code.
For slink the best we can do is patch our code as well as we can to not
segfault. (Wish I knew why it's segfaulting!).
--
Enrique Zanardi ezanardi@ull.es
Reply to: