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

Re: Loading 2 LinuxOS with LILO



On Tue, Feb 09, 1999 at 07:00:38PM +0100, homega@vlc.servicom.es 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 = cylinders of 4032 * 512 bytes
> 
>    Device Boot   Begin    Start      End   Blocks   Id  System
> /dev/hda1            1        1      305   614848+   6  DOS 16-bit >=32M
> /dev/hda2   *      306      306      588   570528   83  Linux native
> /dev/hda3          589      589      620    64512   82  Linux swap
> 
> A secondary master UDMA HDD of ~4.3GB as follows:
> Disk /dev/hdc: 15 heads, 63 sectors, 8894 cylinders
> Units = cylinders of 945 * 512 bytes
> 
>    Device Boot   Begin    Start      End   Blocks   Id  System
> /dev/hdc1            1        1     6936  3277228+   5  Extended
> /dev/hdc2         6144     6937     7214   131355   82  Linux swap
> /dev/hdc5   *        1        1      109    51439+  83  Linux native
> /dev/hdc6          110      110     1193   512158+  83  Linux native
> /dev/hdc7         1024     1194     1627   205033+  83  Linux native
> /dev/hdc8         1024     1628     2278   307566   83  Linux native
> /dev/hdc9         2048     2279     3362   512158+  83  Linux native
> /dev/hdc10        3072     3363     5530  1024348+  83  Linux native
> /dev/hdc11        5120     5531     6614   512158+  83  Linux native
> /dev/hdc12        6144     6615     6936   152113+  83  Linux native
> 
> /dev/hda2 is where the Debian 2.0 root partition is installed, as well as
> lilo;  /dev/hdc5 is where Slackware 3.5 root partition is installed.  The
> other Linux native partitions are directories both SOs are sharing (/home,
> /usr/local, /tmp, ...) or will be sharing (/usr/doc).
ok.

> The only successful attempt for a /etc/lilo.conf file has been:
> 
> boot=/dev/hda2
> root=/dev/hda2
> install=/boot/boot.b
> map=/boot/map
> vga=normal
> prompt
> delay=20
> image=/vmlinuz
> label=debian
> read-only
> 
> image=/vmlinuz
> label=slack
> root=/dev/hdc5
> 
> other=/dev/hda1
> label=win
> table=/dev/hda
> 
> `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.
Lilo won't take the kernel image from the device but from a filesystem.

You need to do (running debian)

mkdir /slack
mount -o ro /slack /dev/hdc5

and replace the corresponding section above by
 image=/slack/vmlinuz
 label=slack   
 root=/dev/hdc5


Nils

--
Plug-and-Play is really nice, unfortunately it only works 50% of the time.
To be specific the "Plug" almost always works.            --unknown source

Attachment: pgpIvPR2nZwc1.pgp
Description: PGP signature


Reply to: