13 + 13.37
notbob
need some guidance. Note I said guidance and am not asking fer
step-by-step.
Issue: I want to leave my finely tweaked slack 13 box untouched while
having the option of booting to the new leet slack which I jes burned
to dvd. I've gone the plug-in HDD bay route so long, am clueless to
duel booting two different versions of slack. I've installed slack as
duel boot on several M$ boxes, but never seen install options for duel
booting diff linux. Is it jes a case of editing lilo? Jes point me
in a direction and I'll do the legwork. Thanks, gang. ;)
nb
--
vi ...the root of evil
Aragorn
enlightened humanity with the following words...:
Just make sure you install the new distro's LILO inside the "/boot" or
root partition's boot sector, not in the master boot record of the hard
disk. Then, set up the LILO of your Slack 13 disk to chainload the
other LILO, or use the method you use to boot Microsoft systems. As
long as the Slack 13.37's LILO is inside a partition, it doesn't really
matter how you call upon it.
The LILO documentation should help you further on your way. ;-)
--
Aragorn
(registered GNU/Linux user #223157)
goarilla
I think you are overcomplicating aragorn.
Why not just install slack 13.37 to a different partition, don't install
lilo and add a new stanza to the existing lilo.conf and change the root
partition to the partition you installed the new slack in.
eg:
image = /boot/vmlinuz
root = /dev/sda1
label = slack-13.1
initrd = /boot/initrd.gz
read-only
image = /boot/vmlinuz
root = */dev/sda2*
label = slack-13.37
initrd = /boot/initrd.gz
read-only
Then run lilo on the old systeem reboot and select the new slack.
Eef Hartman
> image = /boot/vmlinuz
> root = /dev/sda1
> label = slack-13.1
> initrd = /boot/initrd.gz
> read-only
>
> image = /boot/vmlinuz
> root = */dev/sda2*
> label = slack-13.37
> initrd = /boot/initrd.gz
> read-only
Not quite: the two kernels and initrd's must be in the _same_ /boot
directory (probably the one from 13.1), so have different names.
/boot can be in its own partition too, but still lilo must be
able to see BOTH kernels and initrd's at the same time, like this:
> image = /boot/vmlinuz-2.6.<version from 13.1>
> root = /dev/sda1
> label = slack-13.1
> initrd = /boot/initrd-2.6.<version>.gz
> read-only
>
> image = /boot/vmlinuz-2.6.<version from 13.37>
> root = /dev/sda2
> label = slack-13.37
> initrd = /boot/initrd-2.6.<version>.gz
> read-only
When you're using the distribution kernels, 13.1 came with
2.6.33.4 and 13.37 with 2.6.37.6 (and corresponding initrd's).
--
******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-27 82525 **
******************************************************************
tapp
> Not quite: the two kernels and initrd's must be in the _same_ /boot
> directory (probably the one from 13.1), so have different names.
Which brings us back to Aragorn's original, simpler idea: install the new
system normally incl. LILO to a new hdd, and add a chainload command in
the LILO of the hdd which continues to be your first boot device.
Joost Kremers
> Not quite: the two kernels and initrd's must be in the _same_ /boot
> directory (probably the one from 13.1), so have different names.
it's been a while since i did any dual booting, but i'm pretty sure that this is
not true. crucial is that /sbin/lilo (the program that reads lilo.conf and then
installs the bootloader LILO) has access to both kernels. so you can keep the
kernels in different /boot directories on different partitions, as long as both
partitions are mounted and lilo.conf points to the kernels correctly when
/sbin/lilo is run.
the point is that when you run /sbin/lilo, you're doing it from a running
system. that means that the path to the kernel of the other system (the one
you're not running at that moment) is *different* from the path to that same
kernel when you *are* running that second system. that may lead to some
confusion, but it actually makes sense when you think about it a little.
another option that i've used for a while was to have a separate partition with
the all kernels and System.map files and mount it under /boot in both installs.
--
Joost Kremers joostk...@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
Eef Hartman
> it's been a while since i did any dual booting, but i'm pretty sure that this is
> not true. crucial is that /sbin/lilo (the program that reads lilo.conf and then
True, but he was referring to "/boot/vmlinuz" and "/boot/initrd.gz"
for both entries, 13.1 and 13.37.
The second kernel then should have i.e. in /boot13.37/vmlinuz.
But the chainloader solution also works, or the one I mostly use:
having /boot in a separate partition and mounting it from both
releases (and then the kernels will have to be referred by their
respective versions).
> another option that i've used for a while was to have a separate partition with
> all kernels and System.map files and mount it under /boot in both installs.
As I said, that is my preferred solution for multi-booting different
Linux versions too.
Joost Kremers
> Joost Kremers <joostk...@yahoo.com> wrote:
>> it's been a while since i did any dual booting, but i'm pretty sure that this is
>> not true. crucial is that /sbin/lilo (the program that reads lilo.conf and then
>
> True, but he was referring to "/boot/vmlinuz" and "/boot/initrd.gz"
> for both entries, 13.1 and 13.37.
>
> The second kernel then should have i.e. in /boot13.37/vmlinuz.
or in /mnt/boot/vmlinuz. that's a method i've used in the past as well.
jo...@wexfordpress.com
> >> it's been a while since i did any dual booting, but i'm pretty sure that this is
> >> not true. crucial is that /sbin/lilo (the program that reads lilo.conf and then
>
> > True, but he was referring to "/boot/vmlinuz" and "/boot/initrd.gz"
> > for both entries, 13.1 and 13.37.
>
> > The second kernel then should have i.e. in /boot13.37/vmlinuz.
>
> or in /mnt/boot/vmlinuz. that's a method i've used in the past as well.
>
> --
> Selbst in die Unterwelt dringt durch Spalten Licht
> EN:SiS(9)
Let's make things simple.
I do indeed use the MBR of disk one for the various versions. Right
now I run 12.2, 13.0, 13.37 and the Salix version of 13.37. Sometimes
I also address a Win XP partition. I have two hard disks.
The trick is to address each partition in lilo for the full linux
vmlinuz image for that partition.
Each partition including the current one must be mounted before lilo
is run. . I use directories with the same name thus:
mkdir /sda8
mount /dev/sda8 /sda8
etc. for each partition to be addressed.
In my lilo.conf I have
...
# Linux bootable partition config begins
image =/sda3/boot/vmlinuz
root = /dev/sda3
label = Salix
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image =/sda8/boot/vmlinuz
root = /dev/sda8
label = Slack13.37
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image =/sda5/boot/vmlinuz
root = /dev/sda5
label = Slack13.0sda5
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /sdb2/boot/vmlinuz
root = /dev/sdb2
label = Slack12.2
read-only
# Linux bootable partition config ends
... etc.
I always have the right vmlinuz for the partition to be booted.
Been using this technique for a long time with no problems. The only
problem is when I mix in a knoppix or other Debian partition. They
require a different kind of Lilo block.
John Culleton
geep
Meself, I'd abandon lilo and use grub-0.97.
It's what I've used for ages and it's just so simple to add additional
Slackwares and M$ too. All that needs to be done when installing a
new Slackware is to edit one file - menu.lst. Installing M$ requires a
bit of thought, and maybe a smidgen of BIOS priority tweaking.
Cheers,
Peter
Lubiraz Alerano
I've installed slack as duel boot on several M$ boxes Jes point me
in a direction and I'll do the legwork.
OK, lets try. The said MS-Glassware was installed by some UFO and it
contained its booting app. on partition.
So your lilo call was a simple "other = /dev/whatever; label = Win(3;
3.1; 3.11; 95; 98; ME; 2000; XP; Vista; 7){choose one}" and the
computerised hardware responded. In some instances you had to instruct
lilo with the strange call "boot-as 0x80" so "C" behaves as primary.
In the same way treat ANY distribution of Slackware - the "setup" app
takes you through all steps and installs in designated partition and
one of finishing steps IS installation of lilo. Tell it to install
itself 'on root'.
Reboot to your "native" install call lilo.conf to editor and add a
call pointing to this "guest" partition.
Years works on my installs.
Have fun.
j...@pear.hopto.org
[snip]
> Meself, I'd abandon lilo and use grub-0.97.
> It's what I've used for ages and it's just so simple to add additional
> Slackwares and M$ too. All that needs to be done when installing a
> new Slackware is to edit one file - menu.lst. Installing M$ requires a
> bit of thought, and maybe a smidgen of BIOS priority tweaking.
> Cheers,
> Peter
Or you could use a boot CD. The CD would contain Legacy Grub's
menu.lst and stage2_eltorito. It would also have the Linux kernel,
needed modules, and initrd.gz. Easy to use: just put the CD in the
drive and boot--your new installation of Linux will boot. Take out the
CD and boot and you're back to normal.
Making one for Slackware 13.37 will require a little work. All I have
to offer is a boot CD for Slackware 13.1. You can learn more at
Chick Tower
> Meself, I'd abandon lilo and use grub-0.97.
> It's what I've used for ages and it's just so simple to add additional
> Slackwares and M$ too. All that needs to be done when installing a
> new Slackware is to edit one file - menu.lst.
Perhaps that's all it would take. Since Slackware 13.0, the installer
formats disks in a way that the GRUB that comes with Slackware cannot
handle. It can still chain-load to a boot loader on the "new-format"
partition, so you might need to install LILO in the new root. I believe
the details are in the Slackware 13.0 changelog.
I don't know if GRUB2 can handle the new format, but I know it can read
ext4 disks.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
Rob
> Perhaps that's all it would take. Since Slackware 13.0, the installer
> formats disks in a way that the GRUB that comes with Slackware cannot
> handle. It can still chain-load to a boot loader on the "new-format"
> partition, so you might need to install LILO in the new root. I believe
> the details are in the Slackware 13.0 changelog.
>
> I don't know if GRUB2 can handle the new format, but I know it can read
> ext4 disks.
The easiest way (that I find anyway), is to create a relatively small (say 256
MB) separate /boot partition using EXT2 or EXT3. Then I just copy the kernels
there as I install OSes or recompile the kernels (I usually don't even bother to
add it to fstab - I'll just mount it when updating).
That way I get two benefits: I can use GRUB legacy while still being able to
use EXT4 or other root filesystems as long as the kernel/initrd has support.
Adding a new OS or kernel then is a simple matter of editing menu.lst without
messing with boot loaders at all.
--
Rob