[opensuse] Installing multiple operating systems on same HDD
I don't want to use VirtualBox or VMWare. I have a 1TB HDD which is crammed full of empty and unused space. I want to put this space to some use by playing around with more than one systems and distros. I have created (for now) following partitions on this HDD (sda): sda1 Windows XP ntfs [INSTALLED EARLIER TODAY] sda2 Extended partition sda5 openSUSE 12.2 [INSTALLED EARLIER TODAY] sda6 swap sda7 (For oS 12.1) sda8 (For os 12.1 - just for the heck of it) Now, XP of course has its boot sitting in MBR and GRUB in openSUSE 12.2 is using Extended Partition to boot. Before I go and install oS 12.1 in sda7 I would like to know where do I tell GRUB to boot from - extended partition, just like oS 12.2, or do I use the 12.1 "/" entry for Grub's configuration? If I use the Extended Partition will it overwrite whatever is there for the 12.2 installation? I am asking because I don't want to spend hours recovering my 12.2 system if I mess the setup in Grub for 12.1. I've looked around but cannot find an unambiguous description of what to use for the 12.1 Grub except that one should not use the MBR (and not only because XP is installed). All help would be greatly appreciated, thank you. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday, August 11, 2012 09:41 AM Basil Chupin wrote:
I don't want to use VirtualBox or VMWare. I have a 1TB HDD which is crammed full of empty and unused space. I want to put this space to some use by playing around with more than one systems and distros.
I have created (for now) following partitions on this HDD (sda):
sda1 Windows XP ntfs [INSTALLED EARLIER TODAY] sda2 Extended partition sda5 openSUSE 12.2 [INSTALLED EARLIER TODAY] sda6 swap sda7 (For oS 12.1) sda8 (For os 12.1 - just for the heck of it)
Now, XP of course has its boot sitting in MBR and GRUB in openSUSE 12.2 is using Extended Partition to boot.
Before I go and install oS 12.1 in sda7 I would like to know where do I tell GRUB to boot from - extended partition, just like oS 12.2, or do I use the 12.1 "/" entry for Grub's configuration? If I use the Extended Partition will it overwrite whatever is there for the 12.2 installation?
I am asking because I don't want to spend hours recovering my 12.2 system if I mess the setup in Grub for 12.1. I've looked around but cannot find an unambiguous description of what to use for the 12.1 Grub except that one should not use the MBR (and not only because XP is installed).
All help would be greatly appreciated, thank you.
BC
With the Windows code in the MBR you must boot from one of the four primary partitions, whichever is marked active. You don't say how you are controlling whether the MBR calls sda1 vs sda2. In any event, the simplest solution for the 12.1 sda7 instance is to install grub in that partition's boot sector. You can then add a stanza to menu.lst in sda5's 12.2 that chainloads to sda7. Or you can add bypass installing grub with 12.1 and add a fully qualified stanza to sda5's menu.lst that will boot that instance directly. That is, chainloading will have 12.2 grub handing off to the 12.1 grub in the sda7 PBR, while a fully qualified stanza will have 12.2 grub directly calling the 12.1 kernel and root from sda7. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-08-11 15:41, Basil Chupin wrote:
I don't want to use VirtualBox or VMWare. I have a 1TB HDD which is crammed full of empty and unused space. I want to put this space to some use by playing around with more than one systems and distros.
I have created (for now) following partitions on this HDD (sda):
sda1 Windows XP ntfs [INSTALLED EARLIER TODAY] sda2 Extended partition sda5 openSUSE 12.2 [INSTALLED EARLIER TODAY] sda6 swap sda7 (For oS 12.1) sda8 (For os 12.1 - just for the heck of it)
Now, XP of course has its boot sitting in MBR and GRUB in openSUSE 12.2 is using Extended Partition to boot.
Before I go and install oS 12.1 in sda7 I would like to know where do I tell GRUB to boot from - extended partition, just like oS 12.2, or do I use the 12.1 "/" entry for Grub's configuration? If I use the Extended Partition will it overwrite whatever is there for the 12.2 installation?
Yes. You tell it to install grub in sda7, its own root partition, not to boot from mbr, not to write generic code to mbr. This way you first boot your first installed grub, and you add an entry to boot the second grub: title second grub (/dev/sda7) rootnoverify (hd0,6) chainloader +1 This way you can add as many as you like. You could install a small oS at the first position instead which task is to hold grub and act as rescue system if needed. - -- Cheers / Saludos, Carlos E. R. (from 12.1 "Asparagus" GM (bombadillo)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAmhC0ACgkQU92UU+smfQUoXgCePB3tVG4w6PCnS0uu2xh0Kv8P ILUAnRyEF1mupUeihdN+n3YtimqHm2SL =b0hp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2012. augusztus 11. 15:41 napon Basil Chupin
I don't want to use VirtualBox or VMWare. I have a 1TB HDD which is crammed full of empty and unused space. I want to put this space to some use by playing around with more than one systems and distros.
I have created (for now) following partitions on this HDD (sda):
sda1 Windows XP ntfs [INSTALLED EARLIER TODAY] sda2 Extended partition sda5 openSUSE 12.2 [INSTALLED EARLIER TODAY] sda6 swap sda7 (For oS 12.1) sda8 (For os 12.1 - just for the heck of it)
Now, XP of course has its boot sitting in MBR and GRUB in openSUSE 12.2 is using Extended Partition to boot.
Before I go and install oS 12.1 in sda7 I would like to know where do I tell GRUB to boot from - extended partition, just like oS 12.2, or do I use the 12.1 "/" entry for Grub's configuration? If I use the Extended Partition will it overwrite whatever is there for the 12.2 installation?
I am asking because I don't want to spend hours recovering my 12.2 system if I mess the setup in Grub for 12.1. I've looked around but cannot find an unambiguous description of what to use for the 12.1 Grub except that one should not use the MBR (and not only because XP is installed).
Hello: I always chainload all my different operation systems. In practice this looks like when you turn on the machine it offers a grub or lilo (or other) boot loader menu where you can choose which system to boot. If the chosen one is linux then it directs to another boot loader where you can select from kernel versions or failsafe mode etc. In case of Windows it is booted directly (at leas in my case). Have a look at this message / thread: http://lists.opensuse.org/opensuse/2012-01/msg00985.html Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/12 07:37, Istvan Gabor wrote:
2012. augusztus 11. 15:41 napon Basil Chupin
írta: [.....]
Before I go and install oS 12.1 in sda7 I would like to know where do I tell GRUB to boot from - extended partition, just like oS 12.2, or do I use the 12.1 "/" entry for Grub's configuration? If I use the Extended Partition will it overwrite whatever is there for the 12.2 installation? [...........]
Hello:
I always chainload all my different operation systems. In practice this looks like when you turn on the machine it offers a grub or lilo (or other) boot loader menu where you can choose which system to boot. If the chosen one is linux then it directs to another boot loader where you can select from kernel versions or failsafe mode etc. In case of Windows it is booted directly (at leas in my case).
Have a look at this message / thread:
http://lists.opensuse.org/opensuse/2012-01/msg00985.html
Istvan
Many thanks to you, Dennis and Carlos for your help. I now "get the idea". The bit I was really missing was that the additional system has to be manually added to menu.lst. What was throwing me was that I naturally assumed that when I installed 12.2 after XP and grub automatically recognised that there was another operating system installed and made an entry for it in the menu.lst that it would the same when I install more systems - ie, create the correct entry/ies for it/them. But not so - one has to manually edit (the very first) menu.lst to add the additional systems. Thanks again for your help. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-08-12 03:56, Basil Chupin wrote:
What was throwing me was that I naturally assumed that when I installed 12.2 after XP and grub automatically recognised that there was another operating system installed and made an entry for it in the menu.lst that it would the same when I install more systems - ie, create the correct entry/ies for it/them. But not so - one has to manually edit (the very first) menu.lst to add the additional systems.
Yast assumes the system you are installing is the main one, the boss. That one would have entries for the rest. Thus you have to tell yast not to do that, and then add the entries on the first system. Yast of the first system might add entries for the rest, though. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlAnEAUACgkQja8UbcUWM1zgKwD9FaUqQkPyqmwnw8W0GKSPQ3yB HntZ+ozDUP6V5eAZ3tsBAIkeeXQBEhzcubpnb6W14Au8wHfRK3pzOu33XjZ/82vf =HK1+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/12 12:08, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-08-12 03:56, Basil Chupin wrote:
What was throwing me was that I naturally assumed that when I installed 12.2 after XP and grub automatically recognised that there was another operating system installed and made an entry for it in the menu.lst that it would the same when I install more systems - ie, create the correct entry/ies for it/them. But not so - one has to manually edit (the very first) menu.lst to add the additional systems. Yast assumes the system you are installing is the main one, the boss. That one would have entries for the rest. Thus you have to tell yast not to do that, and then add the entries on the first system.
Yast of the first system might add entries for the rest, though.
Hi Carlos, Let me get this right. Are you saying that if I were to install now openSUSE 12.1 into sda7 (with XP already in sda1 and oS 12.2 already in sda5) then the new install 12.1 will recognise and make the correct entries for these already-existing systems? And if this is the case, then when I boot the computer I will see the grub menu for 12.1 which will have 12.1 as the first entry on this menu with XP and 12.2 further down the menu? And if this is correct then all one need to do is to edit the menu.lst for 12.1 and rearrange the order of the systems shown so that instead of seeing 12.1 as the first entry it shows, say, 12.2 (or even XP)? BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-08-12 04:24, Basil Chupin wrote: What _HE_ thinks are the correct entries. There is a difference. :-) Perhaps... Sometimes... HTH ;-) - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlAnG4gACgkQja8UbcUWM1zoMwD5AV4whd5MSas2goRXKjJUFkpo 4DNw3Awlc6N1jkvHr+EA+wRlpvjWESE1HBik3SiRXZx/ELs73IfKWtOMcBTuSF2F =vhjx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-08-12 04:24, Basil Chupin wrote:
On 12/08/12 12:08, Carlos E. R. wrote:
Hi Carlos,
Let me get this right.
Are you saying that if I were to install now openSUSE 12.1 into sda7 (with XP already in sda1 and oS 12.2 already in sda5) then the new install 12.1 will recognise and make the correct entries for these already-existing systems?
What _HE_ thinks are the correct entries. There is a difference. :-)
And if this is the case, then when I boot the computer I will see the grub menu for 12.1 which will have 12.1 as the first entry on this menu with XP and 12.2 further down the menu?
Perhaps...
And if this is correct then all one need to do is to edit the menu.lst for 12.1 and rearrange the order of the systems shown so that instead of seeing 12.1 as the first entry it shows, say, 12.2 (or even XP)?
Sometimes... HTH ;-) - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlAnG4sACgkQja8UbcUWM1y4zwEAiUimF/66df0UwIfMG24Vd8zQ 26gtdncWl8BZXUYj/tIA/3giVIPvpli0ewtu76q1lcKxkL90qL9GXUcNfcBcpR8K =HfNR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/12 12:57, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-08-12 04:24, Basil Chupin wrote:
On 12/08/12 12:08, Carlos E. R. wrote: Hi Carlos,
Let me get this right.
Are you saying that if I were to install now openSUSE 12.1 into sda7 (with XP already in sda1 and oS 12.2 already in sda5) then the new install 12.1 will recognise and make the correct entries for these already-existing systems? What _HE_ thinks are the correct entries. There is a difference. :-)
And if this is the case, then when I boot the computer I will see the grub menu for 12.1 which will have 12.1 as the first entry on this menu with XP and 12.2 further down the menu? Perhaps...
And if this is correct then all one need to do is to edit the menu.lst for 12.1 and rearrange the order of the systems shown so that instead of seeing 12.1 as the first entry it shows, say, 12.2 (or even XP)? Sometimes...
HTH ;-)
So what you are saying is, "Ya buys yar ticket and ya takes yar chances", right? :-) (Sounds very strange for such a sophisticated system like openSUSE to operate. I could expect this from some other distros but from openSUSE........ :-) .) BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/12 12:57, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-08-12 04:24, Basil Chupin wrote:
On 12/08/12 12:08, Carlos E. R. wrote: Hi Carlos,
Let me get this right.
Are you saying that if I were to install now openSUSE 12.1 into sda7 (with XP already in sda1 and oS 12.2 already in sda5) then the new install 12.1 will recognise and make the correct entries for these already-existing systems? What _HE_ thinks are the correct entries. There is a difference. :-)
And if this is the case, then when I boot the computer I will see the grub menu for 12.1 which will have 12.1 as the first entry on this menu with XP and 12.2 further down the menu? Perhaps...
And if this is correct then all one need to do is to edit the menu.lst for 12.1 and rearrange the order of the systems shown so that instead of seeing 12.1 as the first entry it shows, say, 12.2 (or even XP)? Sometimes...
HTH ;-)
You should have more faith in openSUSE. I just installed 12.1 the above way and it works flawlessly :-) . grub for 12.1 picked up XP and 12.2 correctly and I can boot into all 3 without any hassles :-) . All I need to do now is to rearrange the order re what appears in whcih order in the grub boot menu. I think that there should be a qualification to this just for the record: the above is working the way described above with GRUB LEGACY and not grub2. (I wonder if it will work in the same way with grub2? I'll find out sometime in the future no doubt when grub2 becomes operational in oS.) BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/08/11 23:41 (GMT+1000) Basil Chupin composed:
I don't want to use VirtualBox or VMWare. I have a 1TB HDD which is crammed full of empty and unused space. I want to put this space to some use by playing around with more than one systems and distros.
I have created (for now) following partitions on this HDD (sda):
sda1 Windows XP ntfs [INSTALLED EARLIER TODAY] sda2 Extended partition sda5 openSUSE 12.2 [INSTALLED EARLIER TODAY] sda6 swap sda7 (For oS 12.1) sda8 (For os 12.1 - just for the heck of it)
Not an ideal multiboot arrangement if you plan on having more Linux installations. You don't want new installations stomping on existing installations' bootability by overwriting a pre-existing Grub. And, you don't want the inevitable reinstallation of Windows to stomp out all else's bootability, even if it takes an experienced user only a minute or two at most to fix it afterward. The most reliable way to set up multiboot is to create a smallish primary to be the real or master boot partition. Windows won't mess with it, yet it works with generic Windows-compatible MBR code. Once Grub is installed to it, it doesn't get mounted to /boot, and only you touch it, which means it can't get mangled unless you mangle it yourself. All Windows will do is move the boot flag to its own partition, which you move back after the Windows reinstall is complete. Or you can even keep Windows as the primary bootloader by creating an entry for NTLDR to use to chainload to your primary Grub. http://fm.no-ip.com/PC/install-doz-after.html explains. http://fm.no-ip.com/Tmp/Dfsee/gx620L01.txt is a single HD layout designed for 4 distros plus both Windows and DOS and a huge partition for A/V files. http://fm.no-ip.com/Tmp/Dfsee/gx280L02.txt is a single HD layout designed for Windows and Dos and 9 Linux distros on a much smaller HD. http://fm.no-ip.com/Tmp/Dfsee/gx260L0f.txt is a single HD layout designed for Windows and Dos and 19 Linux distros on a much smaller HD, with freespace remaining to add several more. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/12 16:53, Felix Miata wrote:
On 2012/08/11 23:41 (GMT+1000) Basil Chupin composed:
I don't want to use VirtualBox or VMWare. I have a 1TB HDD which is crammed full of empty and unused space. I want to put this space to some use by playing around with more than one systems and distros.
I have created (for now) following partitions on this HDD (sda):
sda1 Windows XP ntfs [INSTALLED EARLIER TODAY] sda2 Extended partition sda5 openSUSE 12.2 [INSTALLED EARLIER TODAY] sda6 swap sda7 (For oS 12.1) sda8 (For os 12.1 - just for the heck of it)
Not an ideal multiboot arrangement if you plan on having more Linux installations. You don't want new installations stomping on existing installations' bootability by overwriting a pre-existing Grub. And, you don't want the inevitable reinstallation of Windows to stomp out all else's bootability, even if it takes an experienced user only a minute or two at most to fix it afterward.
The most reliable way to set up multiboot is to create a smallish primary to be the real or master boot partition. Windows won't mess with it, yet it works with generic Windows-compatible MBR code. Once Grub is installed to it, it doesn't get mounted to /boot, and only you touch it, which means it can't get mangled unless you mangle it yourself. All Windows will do is move the boot flag to its own partition, which you move back after the Windows reinstall is complete. Or you can even keep Windows as the primary bootloader by creating an entry for NTLDR to use to chainload to your primary Grub. http://fm.no-ip.com/PC/install-doz-after.html explains.
http://fm.no-ip.com/Tmp/Dfsee/gx620L01.txt is a single HD layout designed for 4 distros plus both Windows and DOS and a huge partition for A/V files.
http://fm.no-ip.com/Tmp/Dfsee/gx280L02.txt is a single HD layout designed for Windows and Dos and 9 Linux distros on a much smaller HD.
http://fm.no-ip.com/Tmp/Dfsee/gx260L0f.txt is a single HD layout designed for Windows and Dos and 19 Linux distros on a much smaller HD, with freespace remaining to add several more.
Many thanks for this, Felix. I like it. The first option will do me quite nicely as I cannot see myself installing more than 2 copies of openSUSE and then 2 other distros just to keep in touch with other attempts at getting Linux to the world :-) . What I want to set up then is this on one HDD: XP openSUSE 12.2 openSUSE 12.1 (which will be replaced by 12.3 when it is starts to take shape) Distro-1 Distro-2 But I am trying to come to grips with what is shown in the first URL you provided. I think it is pretty clear to me that sdc7 to and including sdc10 contain the 4 Linux distros, and sdc16 contains the A/V files. I am also assuming that sdc11, 12 and 13 are partitions for the Windows installation. I am also assuming that sdc2 is the active partition for Windows where the NTLDR will go, and that sdc3 is the common /boot partition for the 4 Linux distros. But what are sdc14 and especially sdc15 which is only 1GB big? From the above (first URL example) I am concluding that what I should be doing is: a. create a 500MB Primary partition with 32FAT to act as C:/ for Windows and which I will make ACTIVE; b. create a 200MB Primary partition called /boot formatted ext3 for use by Linux distros; c. create an Extended partition from the remaining space, and then create within this logical drives for- 1. swap (common to all distros) of 4GB; 2. partition for oS12.2; 3. partition for oS 12.1; 4. partition for Distro-1; 5. partition for Distro-2. Now, installing XP is not a hassle, and installing oS 12.2 is OK as well - I assume I install grub legacy to the common /boot; and I then also install the subsequent distros to /boot as well - is this correct? In your URL example above, this common /boot would be (your) sdc3, correct? BC PS BTW, I don't intend to re-install XP ever as it will be there only to remind me of what crap looks like :-) . -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/08/12 19:20 (GMT+1000) Basil Chupin composed:
On 12/08/12 16:53, Felix Miata wrote:
http://fm.no-ip.com/Tmp/Dfsee/gx620L01.txt is a single HD layout designed for 4 distros plus both Windows and DOS and a huge partition for A/V files.
That URL is what was a prelimininary layout for that system. http://fm.no-ip.com/Tmp/Dfsee/vizioL05.txt is the current more self-explanatory one for the same system.
http://fm.no-ip.com/Tmp/Dfsee/gx280L02.txt is a single HD layout designed for Windows and Dos and 9 Linux distros on a much smaller HD.
http://fm.no-ip.com/Tmp/Dfsee/gx260L0f.txt is a single HD layout designed for Windows and Dos and 19 Linux distros on a much smaller HD, with freespace remaining to add several more.
Many thanks for this, Felix. I like it. The first option will do me quite nicely as I cannot see myself installing more than 2 copies of openSUSE and then 2 other distros just to keep in touch with other attempts at getting Linux to the world :-) . What I want to set up then is this on one HDD:
XP
openSUSE 12.2
openSUSE 12.1 (which will be replaced by 12.3 when it is starts to take shape)
Distro-1
Distro-2
But I am trying to come to grips with what is shown in the first URL you provided.
I think it is pretty clear to me that sdc7 to and including sdc10 contain the 4 Linux distros, and sdc16 contains the A/V files. I am also assuming that sdc11, 12 and 13 are partitions for the Windows installation.
I am also assuming that sdc2 is the active partition for Windows where the NTLDR will go, and that sdc3 is the common /boot partition for the 4 Linux distros.
It's a single HD system. There is no sdc. 1 is C: for Windows. 2 is FreeDOS's C:. 3 is realboot for Grub Legacy, and active, as indicated by the ">" in the first chart column.
But what are sdc14 and especially sdc15 which is only 1GB big?
/home and /usr/local. The latter is where I unpack mozilla.org's Firefox and SeaMonkey devel and legacy builds, and DFSee.
From the above (first URL example) I am concluding that what I should be doing is:
a. create a 500MB Primary partition with 32FAT to act as C:/ for Windows and which I will make ACTIVE;
You probably only want it active while installing Windows, unless you plan to chainload from NTLDR to your master Grub or other Grubs on every boot. If it's not active when you begin Windows installation, it will be when it's over, until you switch it back. 500M is on the tiny side for XP's operating files, probably too small. Around 40M is enough for its boot files and temporary installation files. 3GB or more is what XP needs for the OS, paging and basic software, but with 4G of real RAM it will always be virtually void of freespace due to XP's brain dead calculation of needed paging space. You'll want to disable its paging, or set it to a minimal size, if you're not going to give it a much bigger operating partition.
b. create a 200MB Primary partition called /boot formatted ext3 for use by Linux distros;
Not an entirely good plan: 1-This should be your master Grub. 2-Journalizing /boot is all but pointless. The only times it gets written are Grub updates, kernel updates, and initrd updates. The rest of the time it amounts to a readonly filesystem, and then even reads are infrequent. 3-For the initial Linux installation mounting on /boot would be fine, but once you're ready to install others, you want the first distro's /boot files on the / partition. On this your master Grub you will be the menu.lst maintainer. You don't want multiple distros' kernel updates rearranging it on their own. So you will be mounting it elsewhere. Try /bootmaster, /disks/realboot, /mnt/mastergrub or whatever suits your thinking. Then copy its grub directory content and message file to /boot on that first distro's /, and move the rest there, so that it can continue to be properly maintained by the distro. At that time /etc/grub.conf will need to be updated to the new location, then Grub (re)installed accordingly. 4-The size it needs to be depends on how many kernels and initrds you plan to keep there. 200M is good for a large bunch of installation kernels and initrds, but if you only plan on 4 distros at most, you won't be using very much of 200M. You could instead mount it to /usr/local and make it do dual duty as realboot and home software from outside the package management system that you use in more than one of the distros, if you do any of the latter. If so you'd probably want it to be more than 200M. What I do on a new disk is extract a tarball of message and boot/grub to the new master boot partition, "installing" Grub there via a live Knoppix boot and the Grub shell. Then the installation of the first Linux goes directly and exclusively to the target logical partition without ever needing a separate /boot partition to later need to reconfigure.
c. create an Extended partition from the remaining space, and then create within this logical drives for-
1. swap (common to all distros) of 4GB;
2. partition for oS12.2;
3. partition for oS 12.1;
4. partition for Distro-1;
Seems more like distro 3. :-p
5. partition for Distro-2.
Now, installing XP is not a hassle, and installing oS 12.2 is OK as well - I assume I install grub legacy to the common /boot; and I then also install the subsequent distros to /boot as well - is this correct? In your URL example above, this common /boot would be (your) sdc3, correct?
sda3: master/real/global boot, home to master Grub, chainloader of Windows and other Grubs. Not common /boot. Independent real boot not mounted to /boot. It would become a tangled unusable mess if it was shared by multiple distros. Its use is to chainload to the Grub on each installed distro, and to XP. You can also copy individual stanzas from those menu.lsts or create them from grub.cfgs into its menu.lst to bypass actually using other Grubs, saving a bit of boot time at the expense of adding each new one and manually keeping up to date those for any distros that don't maintain symlinks from their latest kernels to vmlinuz. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/08/12 00:31, Felix Miata wrote:
On 2012/08/12 19:20 (GMT+1000) Basil Chupin composed: [...........]
I am also assuming that sdc2 is the active partition for Windows where
the NTLDR will go, and that sdc3 is the common /boot partition for the 4 Linux distros.
It's a single HD system. There is no sdc.
Many thanks for the clairifications you give below. But, re above, from the first URL: # fdisk -l /dev/sdc Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xdf5ee107 Device Boot Start End Blocks Id System /dev/sdc1 * 1 51 409626 b W95 FAT32 /dev/sdc2 52 116 522112+ 1b Hidden W95 FAT32 /dev/sdc3 117 142 208845 83 Linux /dev/sdc4 143 182401 1463995417+ 5 Extended /dev/sdc5 143 665 4200966 82 Linux swap / Solaris /dev/sdc6 666 926 2096451 1b Hidden W95 FAT32 [..............]
be doing is: From the above (first URL example) I am concluding that what I should
a. create a 500MB Primary partition with 32FAT to act as C:/ for Windows and which I will make ACTIVE;
You probably only want it active while installing Windows, unless you plan to chainload from NTLDR to your master Grub or other Grubs on every boot. If it's not active when you begin Windows installation, it will be when it's over, until you switch it back.
500M is on the tiny side for XP's operating files, probably too small. Around 40M is enough for its boot files and temporary installation files. 3GB or more is what XP needs for the OS, paging and basic software, but with 4G of real RAM it will always be virtually void of freespace due to XP's brain dead calculation of needed paging space. You'll want to disable its paging, or set it to a minimal size, if you're not going to give it a much bigger operating partition.
Eh, I got myself all tied up at this point from this point :-( . I never[***] install XP into C:/ but always into D:/ which is why I create C:/ as 500MB and make it active and use whatever space (>20GB) for XP itself. Whenever I have done this, XP has always put the NTLDR into C:/. [***] EXCEPT in this particular instance where over the past couple of days to save some time I actually installed XP into one big C:/ partition (Primary); then created an extended partition from the remaining space and which I then broke up into logical partitions (a) swap, (b) linux-1, (c) linux-2, (d), linux-3, (e) linux-4 with openSUSE 12.2 sitting in (b) and openSUSE 12.1 now sitting in (c).
by Linux distros; b. create a 200MB Primary partition called /boot formatted ext3 for use
Not an entirely good plan:
1-This should be your master Grub.
From this point onwards you lost me I am sorry to say :-( . But don't worry, I'll reread what you wrote until I "get it" :-) . What is throwing me off is that I have installed XP and also installed openSUSE 12.2. I then installed openSUSE 12.1 and it picked up XP and 12.2 so that when I boot my computer I get a grub menu which allows me to boot into any one of these 3 systems. I realise that when I boot I get openSUSE 12.1 (the last installed system) appearing as the first/default item which will be booted but I have already altered the menu.lst in oS 12.1 to boot not from "0" but "2) which openSUSE 12.2. Therefore what you are saying about a Master Grub and copying things all over the place is causing me brain damage :-D . But as I said, it will eventually sink in :-) . Some light is already starting to break thru but there is still some way to go :-) . [........] BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.5.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/08/13 17:02 (GMT+1000) Basil Chupin composed:
Felix Miata wrote:
But, re above, from the first URL:
# fdisk -l /dev/sdc
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes ... Device Boot Start End Blocks Id System /dev/sdc1 * 1 51 409626 b W95 FAT32 /dev/sdc2 52 116 522112+ 1b Hidden W95 FAT32 /dev/sdc3 117 142 208845 83 Linux /dev/sdc4 143 182401 1463995417+ 5 Extended /dev/sdc5 143 665 4200966 82 Linux swap / Solaris /dev/sdc6 666 926 2096451 1b Hidden W95 FAT32
That's from the 2nd URL in my OP. I later went on to say: That URL is what was a prelimininary layout for that system. http://fm.no-ip.com/Tmp/Dfsee/vizioL05.txt is the current more self-explanatory one for the same system. That preliminary layout wasn't done in the target machine. One machine (big31) was used to connect a HD from an older machine (gx270 aka vizio) that the target was to replace (gx620 aka new vizio), so when that 'fdisk -l' was run, the first machine's HD was sda, the old machine's HD was sdb, and the target HD to go into the new machine was sdc. Big31 was used to do a limited amount of cloning and file copying in order to shortcut the new vizio's installation time. During my response to you I hadn't remembered, or noticed, and wouldn't have selected that example if I had, as the thread was about "same HDD", presumably sda.
Therefore what you are saying about a Master Grub and copying things all over the place is causing me brain damage :-D . But as I said, it will eventually sink in :-) . Some light is already starting to break thru but there is still some way to go :-) .
A short form version of Master Grub menu stanzas might be thought of this way: 1-chainload Windows 2-chainload 12.2's Grub 3-chainload 12.1's Grub 4-chainload Linux #3's Grub 5-chainload Linux #4's Grub and optionally: 6-copy of 12.2's Grub stanza to boot it without any chainloading step 7-copy of 12.1's Grub stanza to boot it without any chainloading step ... Maybe you could think of "Master Grub" as a special purpose OS installation dedicated to boot loader functionality, which must be configured entirely manually by you as sysadmin. The "copying all over the place" would be part of the initial installation only. Had you not already installed anything, you would only be copying one small group of files to one location (boot/grub) from some source (e.g. a tarball or a live Linux) to your Master Grub (primary) partition, after which you would configure a menu.lst, and install Grub using the Grub shell. Once all is done initially, you wouldn't need to modify the Master Grub's menu.lst unless and until adding a new distro that you hadn't already included an appropriate menu.lst stanza for. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Basil Chupin
-
Carlos E. R.
-
Dennis Gallien
-
Felix Miata
-
Istvan Gabor