SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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.
# 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
-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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.