Any Slacker running tripple boot?

NightSky · 06-08-2015, 09:37 PM

Code:

fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x89ca89ca

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1050623      524288   83  Linux
/dev/sda2         1050624   158337023    78643200    5  Extended
/dev/sda3       158337024   472909823   157286400   83  Linux
/dev/sda4       472909824   488397167     7743672   83  Linux
/dev/sda5         1052672     9441279     4194304   82  Linux swap
/dev/sda6         9443328    19929087     5242880   83  Linux
/dev/sda7        19931136   114302975    47185920   83  Linux
/dev/sda8       114305024   156248063    20971520   83  Linux

Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb90db90d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   625121279   312560608+   7  HPFS/NTFS/exFAT

Code:

bash-4.2# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda8        20G  362M   19G   2% /
/dev/sda7        45G  5.2G   37G  13% /usr
/dev/sda3       148G  5.1G  135G   4% /home
/dev/sda4       7.2G   17M  6.8G   1% /usr/local
/dev/sda6       4.8G  229M  4.4G   5% /tmp
/dev/sda1       488M   17M  437M   4% /boot
tmpfs           1.6G     0  1.6G   0% /dev/shm
/dev/sdb1       299G   12G  287G   4% /fat-c

Code:

wrote /etc/lilo.conf, 69 lines, 2069 chars
bash-4.2# /sbin/lilo -v
LILO version 24.0 (released 07-Juni-2013)
  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)
  * Copyright (C) 1999-2007 John Coffman  (until v22)
  * Copyright (C) 2009-2013 Joachim Wiedorn  (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software 
distributed under the BSD License (3-clause). Details can be found in 
the file COPYING, which is distributed with this software.
Compiled at 17:40:54 on Oct 27 2013

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-huge-3.10.17
Added Linux  *

Boot other: /dev/sdb1, on /dev/sdb, loader CHAIN
Added Windows

Syntax error at or above line 70 in file '/etc/lilo.conf'
bash-4.2#

I have 3 hard drive, Slackware64 - primary, WindowsXP secondary, and I need ubanto on the 3rd hard drive which I haven't installed because I don't have first 2 running. Used to run dualboot long time ago with loadlin. Thank you

JackHair · 06-08-2015, 10:28 PM

I run 3 OS's on different drives too. But my boot-menu is my motherboards. I just press F12 at post when I want to boot Windows or LFS. When I do nothing it boots Slackware.

justwantin · 06-09-2015, 12:26 AM

I once had quad boot on three drives. Windows and one linux on hda, the other two on hdb. IIRC there was a third hdd in that box. That was back in the days of installfests and trying to get anything slavageable to run Linux and a time ago when I just had to try every distro found on magazine cover CD's/DVD's. I Just dual boot Slack current and Salix 14.1 now and share the same /home and /usr/local. I've installed Salix on other folks machines and its handy to have a reference when talking to them or if I have to build something for them. Never try other distros now but run Porteus on an old netbook as it runs faster. I won't touch anything but those three and Slackwarearm on SOC's.

syg00 · 06-09-2015, 12:46 AM

When I have Slack, it is always multiboot - usually more than 2. I gave up attempting to use lilo over a decade ago.
Ubuntu will install grub to the MBR and (using os-prober) find your other systems. Easiest solution IMHO.

NightSky · 06-09-2015, 01:06 AM

Never tried another linux OS... its taken me so long to learn to use slackware, as much as I do, and its become easier every year. I'm wanting to try building custom ROM for a not so popular phone and all the linux tutorials referrals are to Kde & Genome Ubanto Desktops. I know Slackware has tons of developing tools but I never liked Kde and don't know gnome. Just XFCE. Figured I would put Ubanto with gnome on its own hard drive. WindowsXP is my lazy goto when I don't feel like researching, compiling, & trying to figure out how to get something I want to do done. Sometimes I just don't have the time to learn tons of stuff just to get one thing working.

kikinovak · 06-09-2015, 01:07 AM

Here's my lilo.conf on buildbox.microlinux.lan:

Code:

image = /boot/vmlinuz-generic-3.10.17
  initrd = /boot/initrd.gz
  root = /dev/sda2
  label = Slack64-14.1
  read-only
image = /mnt/sda3/boot/vmlinuz-generic-smp-3.2.45-smp
  initrd = /mnt/sda3/boot/initrd.gz
  root = /dev/sda3
  label = MLES-14.0-32bit
  read-only
image = /mnt/sda5/boot/vmlinuz-generic-3.2.45
  initrd = /mnt/sda5/boot/initrd.gz
  root = /dev/sda5
  label = MLES-14.0-64bit
  read-only
image = /mnt/sda6/boot/vmlinuz-generic-smp-3.10.17-smp
  initrd = /mnt/sda6/boot/initrd.gz
  root = /dev/sda6
  label = MLES-14.1-32bit
  read-only
image = /mnt/sda7/boot/vmlinuz-generic-3.10.17
  initrd = /mnt/sda7/boot/initrd.gz
  root = /dev/sda7
  label = MLES-14.1-64bit
  read-only
image = /mnt/sda12/boot/vmlinuz-generic-smp-3.10.17-smp
  initrd = /mnt/sda12/boot/initrd.gz
  root = /dev/sda12
  label = MLED-14.1-32bit
  read-only
image = /mnt/sda13/boot/vmlinuz-generic-3.10.17
  initrd = /mnt/sda13/boot/initrd.gz
  root = /dev/sda13
  label = MLED-14.1-64bit
  read-only

And they're not all installed yet:

Code:

# fdisk -l

  Disque /dev/sda*: 250.1*Go, 250059350016*octets
  255*têtes, 63*secteurs/piste, 30401*cylindres, total 488397168*secteurs
  Unités = secteur de 1 * 512 = 512*octets
  Taille de secteur (logique / physique)*: 512*octets / 512*octets
  taille d'E/S (minimale / optimale)*: 512*octets / 512*octets
  Identifiant de disque*: 0x0004e487

  Périphérique Amorce  Début        Fin      Blocs     Id  Système
  /dev/sda1              63     8000369     4000153+  82  swap
  /dev/sda2         8000370    82140344    37069987+  83  Linux
  /dev/sda3        82140345   105579179    11719417+  83  Linux
  /dev/sda4       105579180   488392064   191406442+   5  Étendue
  /dev/sda5       105579243   129018014    11719386   83  Linux
  /dev/sda6       129018078   152456849    11719386   83  Linux
  /dev/sda7       152456913   175895684    11719386   83  Linux
  /dev/sda8       175895748   199334519    11719386   83  Linux
  /dev/sda9       199334583   222773354    11719386   83  Linux
  /dev/sda10      222773418   246212189    11719386   83  Linux
  /dev/sda11      246212253   269651024    11719386   83  Linux
  /dev/sda12      269651088   324336284    27342598+  83  Linux
  /dev/sda13      324336348   379021544    27342598+  83  Linux
  /dev/sda14      379021608   433706804    27342598+  83  Linux
  /dev/sda15      433706868   488392064    27342598+  83  Linux

travis82 · 06-09-2015, 01:08 AM

I have 1 TB hard drive and quad boot on it: Windows 7, Slackware, MLED and Debian and manage them with EasyBCD. If you plan to keep windows for long time it's better to use it.

NightSky · 06-09-2015, 01:12 AM

Quote:

Originally Posted by JackHair

I run 3 OS's on different drives too. But my boot-menu is my motherboards. I just press F12 at post when I want to boot Windows or LFS. When I do nothing it boots Slackware.

How does this option work? How do I setup my ASUS P5LD2 mobo bios options to make this work for me? Thanks

astrogeek · 06-09-2015, 01:18 AM

I have a 500GB 320GB plus 2TB with...

Slackware 14.1 (Primary on 500GB 320GB)
Slackware64 14.1 (also on 500GB) (intended but never installed)
Windows7 (Preserved, shrunk partition with gparted, on 320GB - forgot this was there!)
Slackware64 -current (on 2TB, manages MBR)
FreeBSD 10.1 (on 2TB)

Boot is managed by Lilo under Slackware 14.1 on 500GB 320GB MBR, plus each OS manages its own bootloader on its own partition. From the 500GB 320GB MBR I can boot directly or chain to each OS on itself, and also chain to MBR and each OS on 2TB drive. From 2TB MBR I can chain back to the 500GB 320HB.

I love the flexibility of Lilo!

UPDATE: I have posted the Lilo configs for this system in post #53 in this thread. In doing so I found that it was a little different than what I posted from memory here, so have updated this post accordingly. Take this as evidence of the robustness of a lilo managed multi-disk/multi-boot system - it just works and I forget what is there! I was completely unaware that I had a bootable Windows 7 instance, need to fix that...

JackHair · 06-09-2015, 01:33 AM

Quote:

Originally Posted by NightSky

How does this option work? How do I setup my ASUS P5LD2 mobo bios options to make this work for me? Thanks

You'll have to check your manual for that. I run a Gigabyte mobo which will be different. With the BIOS bootlogo disabled it tells me at post what keys do what though.

justwantin · 06-09-2015, 01:48 AM

Quote:

I gave up attempting to use lilo over a decade ago.

You gave up too quickly! :^)

I've always used lilo. Never seemed that difficult, maybe I just had simpler set ups than you over the years. Never saw the need for all those extra options if I was just passing through.

chris.willing · 06-09-2015, 02:37 AM

Quote:

Originally Posted by NightSky

Code:

bash-4.2# /sbin/lilo -v

[snip]

Syntax error at or above line 70 in file '/etc/lilo.conf'
bash-4.2#

I have 3 hard drive, Slackware64 - primary, WindowsXP secondary, and I need ubanto on the 3rd hard drive which I haven't installed because I don't have first 2 running. Used to run dualboot long time ago with loadlin. Thank you

From the other posts here, its plain that many people are using lilo and other bootloaders to multi boot. Your particular problem may have something to do with line 70 of your /etc/lilo.conf - about which no one here can advise since we can't see that file ...

chris

justwantin · 06-09-2015, 06:09 AM

Would this be of help?

I originally wrote it for a friend and later put it on a web page.... a long time ago. http://turtlespond.net/help/dual_boot.html . I never pulled it off the server because it often gets hits so maybe it is still usefull to some people.

oldtechaa · 06-09-2015, 06:36 AM

I agree with Chris.Willing. If you don't mind sharing your lilo.conf, that would be most helpful. While the boot menu of the BIOS is helpful as a backup for if you mess up your bootloader or something, over hundreds of reboots it gets to be more than it's worth. I have a dual-boot(on separate drives) and I know someone who has a quadruple boot but all on one drive.

With the lilo.conf we should be able to help more.

enorbet · 06-09-2015, 08:15 AM

I have 3 hard drives and 7 OpSys. Two drives are boot drives selected by BIOS boot order. That last bit isn't necessary but I like redundancy. /dev/sda has Lilo and can boot all systems. /dev/sdb has Grub2 which I dislike but wish to keep my hand in play with options, and I only allow it to boot 3 systems. To me Grub2 is a lot of crap just to allow pretty splash screens. I despise it's automated "discover features" and have that disabled so splash screens seems to be the only other thing that Lilo can't do as well and frankly B&W Text is fine by me especially for as little as I see it. Lilo is simple and effective. My only concerns are that at some point UEFI will drop legacy support and make me have to give eLilo a spin. For such fundamentals I see no valid reason to overly complicate or re-invent the wheel. Lilo is simply solid.