GPT + LILO: limitations?
Hi,
My current build server is a multiboot machine with quite many different installations on it. Here's what the hard disk looks like: Code:
# fdisk -l /dev/sda Today I got a new build server, and I would like to copy that setup to my new machine. I'd also prefer to add four extra partitions. As far as I remember, I've reached fdisk's possible limit of logical partitions (correct me if I'm wrong). Normally, GPT partitioning allows me to go beyond this limitation (up until 64 partitions, IIRC). I just tried the gdisk (GPT) partitioning scheme + LILO combination, and it works on this machine. So now I'd like to know the eventual limitations of LILO with this kind of thing. Can I configure something like twenty partitions and then access them via LILO? Cheers, Niki |
If I remember from reading the various docs that come with Slackware, lilo doesn't always work with a GPT system, so it looks like you got lucky. I've read that elilo is a version of lilo that is intended to work better with GPT.
Note: I use MBR so anything I'm saying in the preceding paragraph is theoretical, not actually tried by myself. If you don't mind the (slight amount of) added work of making a initrd for each OS, you could stick with MBR and use LVM to get any number of partitions. I've got two Slackware installs running off the same LVM which is in turn in a LUKS partition, so I confirm that LVM works. :) Note: the boot partition can't be within an LVM, but with care, it is possible to have one boot partition that is used by multiple Linuxes: you make sure the kernel and initrd for each OS has a unique name and update lilo accordingly. edit: adding a second hard drive is another way to get more partitions. ;) |
Quote:
My doubts mainly concerned the number of different systems LILO can address. I guess such extreme multiboot setups are quite rare. Well, for the time being everything seems to work OK. Cheers, Niki |
Quote:
|
Niki,
I don't think on a GPT disk you need extended partitions, but maybe that is needed to be able to boot from a MBR with lilo. Did you do without that partition (/dev/sda4)? I am asking as, a while ago I changed my setup from MBR+LILO to GPT+elilo/refind (i.e. eufi). Before the 'bios' eventually went into eufi-mode I found that the old MBR was still used, at least the system was still booting, but this was done by lilo instead of elilo. For elilo you'll need a separate fat partition, so I wouldn't try GPT+elilo if you do not want to go to eufi-like booting. |
Quote:
|
And here's the end result. Partitioning:
Code:
[root@leanore:~] # gdisk -l /dev/sda Code:
[root@leanore:~] # lilo Niki |
Wait... Kiki, did you use an EF02 BIOS Boot Partition at all or direct boot from a /(root)?
|
Quote:
Cheers, Niki |
Quote:
|
Quote:
Unless, a team from slackware can maintain it. lilo just works. |
Quote:
|
Quote:
|
Quote:
Code:
gdisk /dev/sda |
Quote:
Since LILO is not going to need any work (and I won't just ticker with it for no good reason), I volunteer to take over. Consider it maintained. |
All times are GMT -5. The time now is 02:48 PM. |