time to reminisce. On 02/17/16 22:11, Tim wrote: > Tim: >>> Once you sort this out, you want to plan how you do multiboots in the >>> future. Way back when I tried it, and even two is a pain, one good >>> solution was to make your own custom boot partition, and all it did was >>> let you select which partition to boot, it chainloaded the next one. > > Mike Wright >> That sounds like the ideal approach for what I do. Do you have an >> example of that you'd be willing to share? I've never used chain >> loading and have only seen it referenced on this list. > > Back in the old GRUB 1 days, that was easy enough. And I suppose you > could install a version 1 bootloader onto a single /your/ boot > partition. It'd be left alone by your installs. > > This is from a very old system, which had an entry to chainload from a > floppy disk. By using a hd0 instead of fd0 entry, or whatever drive and > partition number pertained to the partition that you wanted to boot, you > could chainload to another hard drive: > > title Fedora Core (2.6.17-1.2142_FC4) > root (hd0,0) > kernel /vmlinuz-2.6.17-1.2142_FC4 ro root=LABEL=/ acpi=force > initrd /initrd-2.6.17-1.2142_FC4.img > > title Boot from floppy disk drive > lock > rootnoverify (fd0) > chainloader +1 > > 'twas as simple as that. I'm far from impressed by the incomprehensible > mess that GRUB 2 is. > > >> I use a very similar approach. Since a lot of my installs are intended >> to be run in a custom Xen environment they can't even single boot but I >> still need the kernels and initrds to copy elsewhere. The problems >> arise when the installer does what it thinks is best for me and starts >> screwing with my LVM setup or goes scarfing through all my disks >> creating boot stanzas for installations that are incapable of standalone >> boots. Gets really big and really ugly really fast. I have had much >> better luck with Ubuntu installers. > > I think there were options to not probe for other systems. But I > haven't done an install for ages. > > Of course, if you're going to dedicate an entire hard drive to an > installation, the simple solution is to unplug the others while > installing. Or, disable their port in the BIOS, temporarily, so they're > not found. > > Personally, I favoured dedicating whole drives to an install, rather > than partition. There's a few advantages: More space for it to use. > Very easy to unplug to disable, archive, or transfer. Since I don't > install bi-annually, I used to get a new drive for a new install, and > try it out independent from prior installs, with it as the sole drive. > If it hoses anything, it only does itself. The old drive gets > connected, later, data copied over, and the old drive left as an > archive. > > I never seemed to get a collection of un-used drives, though. It's > never long before one gets put into a completely new box, or replaces > another drive that's knackered. > . gone are the 'good old days' of boxes 4 and 5 5" drive bays where one could install install 3" drives in removable drive carriers and swap drives. -- peace out. If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.7 tc,hago. g . -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
