Hartmut Figge wrote:
>image=/vmlinuz
>root=/dev/hda2
>label=debian
>...
>image=/vmlinuz
oops, should read image=/slack/vmlinuz
>root=/dev/hdc5
>label=slack
>...
A similar configuration works well for me with DLD on hda and SuSE on
hdb - and yes, i´m yet thinking
[EMAIL PROTECTED] wrote:
> I'm trying to boot two Linux OS's with lilo, but with no success so far.
[snip]
> /dev/hda2 * 306 306 588 570528 83 Linux native
[snip]
> /dev/hdc5 *11 10951439+ 83 Linux native
[snip]
> /dev/hda2 is where the Debi
>
>`LILO: slack' starts the Slackware OS but loads the Debian kernel image.
>Note that whereas /vmlinuz in Debian is a symlink to /boot/vmlinuz-2.x.x, in
>Slackware /vmlinuz is the kernel image itself.
I've never been able to divine the solution to this either, when using a
2nd or 3rd disk, so I
On Tue, Feb 09, 1999 at 07:00:38PM +0100, [EMAIL PROTECTED] wrote:
> I'm trying to boot two Linux OS's with lilo, but with no success so far.
Should really be easy.
> A primary master IDE HDD of ~1.2GB partitioned as follows:
> Disk /dev/hda: 64 heads, 63 sectors, 620 cylinders
> Units = cylinder
Hi,
I'm trying to boot two Linux OS's with lilo, but with no success so far.
I've gone through all lilo docs and mini-howtos (which are mainly devoted to
Linux + other OS's), and tried several different configurations for
/etc/lilo.conf
Here are some details:
A primary master IDE HDD of ~1.2GB p
5 matches
Mail list logo
