your mail
Quoted 9 lines · Michael Marxmeier
Quoted 6 lines
Quoted 3 lines · Heinz
/boot must be in a regular disk partition containing basic commands, device specials and LVM driver/commands.
About 20-30MB should be sufficient to set this up.
Quoted 8 lines
Quoted 3 lines
IMO this could even be less if initrd is used.
We may need about 1-2 MB per kernel image + 1-2 MB for the initial utilities (shell, vgchange, mount).How about a special boot area inside a boot-configured root volume group? That way, lilo could be modified to run the second stage boot loader which could then be as heavyweight as anyone needs it.
LILO is able to deal with sectors scattered over a boot disk limited by the 1024 cylinder BIOS rsstriction.
This implies no need for a special boot area _if_ we lay all sectors LILO needs into the LV parts on that one disk.
Or did you mean that with voot area?
If LILO would be able to deal with sectors scattered over many disks, why to have a special boot area anyway?
Quoted 3 lines
Isn't this sort of how hpux handles it?
HP-UX's 2nd stage bootstrap loader is only able to deal with a contiguous HFS formated filesystem.
That's the reason they mark the boot/root LV contiguous. Without tricks you are stuck with the initial created size. AFAIK this hasn't been changed including 11.X.
Heinz
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement C/S Deutsche Telekom AG
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt [email protected] Germany +49 6151 886-425 FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement C/S Deutsche Telekom AG
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt [email protected] Germany +49 6151 886-425 FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Quoted 8 lines
LILO is able to deal with sectors scattered over a boot disk limited by the 1024 cylinder BIOS rsstriction.
This implies no need for a special boot area _if_ we lay all sectors LILO needs into the LV parts on that one disk.
Or did you mean that with voot area?If LILO would be able to deal with sectors scattered over many disks, why to have a special boot area anyway?
Okay. Let me make sure I understand this. I think that what you're saying is that at this point, LILO should be able handle an LV like any other partition as far as booting is concerned? If so, then the real problem lies in getting the LVM turned on early enough that we can finish the boot process, correct? And if that were the case, we should be able to treat the LVM like any other necessary kernel driver and install it with an initrd. Sorry to repeat things, but I want to make sure that I have a firm understanding of what you're saying.
--Daniel
-Daniel ------------------------------------------ Daniel Whicker ([email protected])
Quoted 8 lines · Daniel Whicker
Okay. Let me make sure I understand this. I think that what you're saying is that at this point, LILO should be able handle an LV like any other partition as far as booting is concerned? If so, then the real problem lies in getting the LVM turned on early enough that we can finish the boot process, correct? And if that were the case, we should be able to treat the LVM like any other necessary kernel driver and install it with an initrd. Sorry to repeat things, but I want to make sure that I have a firm understanding of what you're saying.
I guess now that I think of it, I was kindof thinking of an area on the root VG that lilo could find, which would hold a kernel, and an initrd image so the extra partition isn't needed.
-Shawn
<=========== America Held Hostage ===========>
Day 2219 for the poor and the middle class.
Day 2238 for the rich and the dead.
703 days remaining in the Raw Deal.
<============================================>