Groups | Search | Server Info | Login | Register
Groups > comp.os.os2.beta > #144
| From | Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> |
|---|---|
| Newsgroups | comp.os.os2.utilities, comp.os.os2.misc, comp.os.os2.beta, comp.os.os2.setup.storage |
| Subject | LVM partition table extensions |
| Message-ID | <IU.D20110429.T212935.P1476.Q0@J.de.Boyne.Pollard.localhost> (permalink) |
| Organization | virginmedia.com |
| Date | 2011-04-29 22:29 +0100 |
Cross-posted to 4 groups.
My Boot Manager was already capable of taking partition names (for the MBR partitioning scheme) from the IBM Boot Manager MBR partition table extensions. Thanks to information provided by Alex Taylor, I've now updated it so that it uses the IBM LVM metadata, falling back to the IBM Boot Manager partition table extensions if the IBM LVM metadata aren't there. I've also updated DASDPART so that it does the same thing. My test systems here don't have IBM's LVM. The EFI partitioning scheme is the way of the future, and my test systems have EFI partition tables and MBR partition tables with no more than the original IBM Boot Manager extensions. But Dave Yeo, whom I believe has OS/2 systems with IBM's LVM, was going to have a go with my Boot Manager. I'm still waiting to hear back from him. (You'll of course now need the new Boot Manager that I've just made, M. Yeo.) I've added in the IBM LVM partition table support blind, and, in the absence of documentation as to the exact algorithm for locating the IBM LVM metadata (a point that we've discussed before, with reference to how something in Ubuntu tidies up container partitions in MBR partition tables to eliminate otherwise unusuable "holes" that waste space) this might require some tweaking to cover all possibilities, which of course I cannot do here without something to test against. If you want to beat M. Yeo to the finishing post, drop me a line. (-: I say that the EFI partitioning scheme is the way of the future. In fact, it's the way of the present, if one takes off the OS/2-tinted glasses. The rest of the world is already going EFI, and has been for some several years now. (My Boot Manager and DASDPART tool already understand EFI partition tables.) So don't expect wonders in the way of OS/2 LVM partition table support. I'm going to work a little more on incorporating the IBM LVM drive letter information into things like my Boot Manager. But if you want an OS/2 LVM tool that will do all of the volume and partition management, M. Taylor is still the person to bribe, not me. (-:
Back to comp.os.os2.beta | Previous | Next — Next in thread | Find similar
LVM partition table extensions Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2011-04-29 22:29 +0100
Re: LVM partition table extensions Roderick Klein <rwklein@xs4all.nl> - 2011-04-30 21:22 +0200
Re: LVM partition table extensions Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2011-05-02 02:53 +0100
Re: The meaning of "my". Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2011-05-02 02:53 +0100
Re: LVM partition table extensions madodel <madodel@ptd.net> - 2011-05-01 20:21 -0500
Re: LVM partition table extensions Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2011-05-02 23:17 +0100
csiph-web