LinuxQuestions.org - Will a common /boot work?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Will a common /boot work? (https://www.linuxquestions.org/questions/slackware-14/will-a-common-boot-work-333065/)

Will a common /boot work?

I wanna install as many as 10 distros, and I am worried whether GRUB supports that number.

Moreover, does it support Unix like Operating Systems? Like Darwin or Solaris or Free BSD?

I am thinking of making a common /boot partition, so as to avoid problems with non-detection of the OSs.

As far as I have heard, I think that Free BSD will install its own boot loader, so if it does that, will it detect the other "Linux" distros? And yes, the stupid Windows XP too.

Need more info? I will provide you.

Yeah. A common /boot is the recommended way to boot multiple distros, so that there's a common mountpoint for lilo.conf or grub if that's what you prefer.

FBSD, I'm not so sure. I do know, however, that NetBSD will detect Linux and Windows installations.

I am still learning the way to boot multiple Operating Systems.

I have read some online tutorials too for this purpose.

Now, is it like the NTLDR (Boot loader for Windows) will reside on the MBR (Windows has to be installed first to avoid any further problems.)

And LILO or GRUB on the /boot partition?

Tell me how big should be the /boot partition. I mean any personal recommendations?

I have read about the 1024 cylinder limit and stuff.

Install Windows first, yeah. But Win2k and XP are (semi-)civilized, in that they install to the superblock, not the MBR.

Install Win.
Set some other partition bootable (your /boot is a good idea)
Install Linux, with LILO in the root block, not the MBR.

It'll work. That's the procedure I've used on three computers, with Win2k and XP. With Win98, it'll still work, but you need to install LILO to the MBR.

Quote:

It'll work. That's the procedure I've used on three computers, with Win2k and XP. With Win98, it'll still work, but you need to install LILO to the MBR.

Didn't get that.

LILO is really simple.
Can you tell me how many operating systems it can support?

[quote]
But Win2k and XP are (semi-)civilized, in that they install to the superblock, not the MBR. [quote]

I thought it was the MBR.
But, in Windows XP Recovery Console, there is a command called

Code:

fixmbr

which places the NTLDR on the MBR.

But who cares.

I need more info on multiple booting with FreeBSD, Solaris and Darwin too. I would also need the order in which they should be installed.

Maybe I should have placed this topic in the *NIX forum as well. :confused:

lilo can boot freebsd.
on one machine ihave this in the /etc/lilo.conf for it :

Code:

# freebsd bootable partition config begins

other=/dev/hda4

table=/dev/hda

loader=/boot/chain.b

label=FreeBSD

# freebsd bootable partition config ends

here freebsd is installed on hda4 ( as you see )
the rest is standard.

also you could use the same kernel with different linux distro's
( the ones that use a standard kernel )

egag

oh.... and the install order:

-windos
-all linux ( install lilo to the mbr with the first...add the rest )
-freebsd etc... ( don't install a bootloader but add them to lilo.conf )

btw...i don't know solaris or darwin

egag

Quote:

also you could use the same kernel with different linux distro's
( the ones that use a standard kernel )

I would like to get more info on that. I have never heard of that! :)

I am quite new to LILO. I think I will go with LILO. I have configured GRUB quite a lot but it fails sometimes.

Can anybody paste the entire /etc/lilo.conf here.. (Better if it has windows too)

I would like to see how does it look exactly.

I know how GRUB should look like. Never configured LILO though.:(

I think I should take some LILO tutorials as well. :)

Quote:

-freebsd etc... ( don't install a bootloader but add them to lilo.conf )

But, If i install Free BSD Later, how do I access my /boot partition?

From within Free BSD or a live CD ? (I have not played with FreeBSD yet)

This is to add the lines corresponding to FBSD to LILO.

Quote:

all linux ( install lilo to the mbr with the first...add the rest )

MBR or the /boot partition?

Thats what my question is.

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot = /dev/hda

#compact        # faster, but won't work on all systems.

prompt

timeout = 300

# Normal VGA console

#vga=normal

# VESA framebuffer console @ 1024x768x64k

vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

#vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# ramdisk = 0    # paranoia setting

# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz-2.6.11.11

  root = /dev/hdb2

  label = Slackware

  append="pci=usepirqmask idebus=66"

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

# Linux bootable partition config ends

# Linux bootable partition config begins

image = /boot/vmlinuz-2.6.11.11

  root = /dev/hdb8

  label = mini

  append="pci=usepirqmask idebus=66"

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

# Linux bootable partition config ends

# Linux bootable partition config begins

image = /boot/vmlinuz-2.6.11.7

  root = /dev/hdb2

  label = Linux-2.6.11.7

  append="pci=usepirqmask idebus=66"

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

# Linux bootable partition config ends

# Windows bootable partition config begins

other = /dev/hda1

  label = windows

  table = /dev/hda

# Windows bootable partition config ends

# freebsd bootable partition config begins

other=/dev/hda4

table=/dev/hda

loader=/boot/chain.b

label=FreeBSD

# freebsd bootable partition config begins

here's a complete lilo.conf file.
it uses the same kernel for hdb2 ( Slackware ) and hdb8 (mini ), and i copied the module-tree
/lib/modules/2.6.11.11 from Slackware to mini.
also there's a choice to boot a different kernel for Slackware and has a windos and freebsd
option.

and i would keep the freebsd kernel in it's own /boot on it's own partition.
lilo has no troubles anymore to boot a kernel above 1024 cyl.
( in fact that's what you do with win. )

-install the first linux distro
-install lilo in the mbr.
-install next distro
-install all on it's own partition
-copy contents of newdistro/boot to main /boot
-reboot to the first distro
-add a new section in lilo.conf ( which points to the new kernel and partition )
-run "/sbin/lilo " to install ( that in fact is a diff. to grub; after a change in lilo.conf
you must rerun lilo )
---->goto install next distro

egag

Quote:

-run "/sbin/lilo " to install ( that in fact is a diff. to grub; after a change in lilo.conf
you must rerun lilo )

Yeah. I read that LILO requires more maintenance compared to GRUB.

Quote:

-install the first linux distro
-install lilo in the mbr.
-install next distro
-install all on it's own partition
-copy contents of newdistro/boot to main /boot
-reboot to the first distro

That was a little bit confusing.

Now, what about my idea of using the common /boot partition?

I understood that i have to keep the FreeBSD /boot on the same partition as on its /root. and later add the lines to lilo.conf (Is it the same way that I have to do with other Linux distros?)

But, now as per you have told, I need to install LILO on the MBR after installing the First Linux Distro.
Installing /boot too on it's own partition did not make sense for me.
Then what is the use of the common /boot partition that I have created?

Does your post supports the fact that LILO is no more under the 1024 cylinder limit?

yip , the 1024 cyl. limit is history.
and i didn't start about a common /boot partition, i thought
you would have reason to want it.
if it was only because of the 1024 cyl. limit , then it's not needed.

you can still use any kernel to boot, as long as the dir.where the kernel is,
is mounted when you run " lilo ", so it can find it.
also , the module-tree on the / partition has to fit the kernel

maybe it's not all to clear yet , but look at it this way :
-when you install lilo ( =run "lilo" ) , the kernel must be found by lilo,
so it has to be somewhere in the directory tree.
-when you boot the kernel, it does not have to be in the directory tree of the
distro you are booting.
the /boot dir. isn't used anymore.

errrm...it *is* confusing... :)
( but it works )

egag

Yeah..Thanks for the help so far guys.

Egag, you helped a lot.

I will take a LILO tutorial, and be back if I have any questions.

I need to understand how LILO works first.

Otherwise I will get badly confused and make this thread tooooooo long, which doesn't seem to be good.

You're serious when you say you will install Darwin ?

Also Solaris install will overwrite the MBR, there's no way
to avoid that, you will have to re-install lilo from Linux
bootable CD.

yeah, do some reading on lilo.
and if you run into troubles or have more Q.'s , just post here.
many people here like to help...

egag