Problems in dual boot
in [Slackware]
|
Prev: Cannot enable desktop effects in KDE 4.3.4 on Slackware 64 13.0
Next: Looking for recommendations on how to perform a massiveupgrade.
From: Grant on 30 Jan 2010 21:12 On Sat, 30 Jan 2010 23:10:37 +0100, Martin <no(a)spam.invalid> wrote: >Grant wrote: > >> >> other = /dev/sda1 >> label = WinVista >> table = /dev/sda >> >> other = /dev/sda2 >> label = Win7rc >> table = /dev/sda >> # >> > > >Ooops, I've always added a "loader" statement like so: > >other = /dev/hda1 > label = Other > table = /dev/hda > loader = chain > >Is that not required anymore? Don't think so, I forget what the chain option might do. Haven't used it this century. Grant. -- http://bugs.id.au/
From: Martin on 31 Jan 2010 07:03
Grant wrote: > On Sat, 30 Jan 2010 23:10:37 +0100, Martin <no(a)spam.invalid> wrote: > >> loader = chain >> >>Is that not required anymore? > > Don't think so, I forget what the chain option might do. Haven't > used it this century. Century might be the explanation. Because in the previous century the loaders were shipped outside of lilo (in the form of little binaries like chain.img, os2.img etc.). I reckon when they moved the loaders into lilo itself, they kept the loaders statement in order not to break existing setups. I've just tried other = /dev/hda1 label = Other table = /dev/hda loader = this_is_a_test and it works perfectly. ;-) Martin |