Dual OS live usb?
by business_kid from LinuxQuestions.org on (#57VKF)
This is at the 'thought experiment' stage, and I'm not running a serious experiment.
The genesis of this is that I want to have some data available on both a RazPi, and a linux box, and I wondered if it could be done with one live usb key.
The RazPi boots without grub, or sector 0, AFAICT. The 1st partition has to be FAT32. There's a string of gpu firmware, memory allocation, cpu firmware, memory reallocation, peripheral firmware loaded & dealt with; there's several programs on /boot, one f which is loaded that does stuff, and a config.txt that's the equivalent of the BIOS peripheral setup. That config.txt loads the kernel which has it's name mentioned in config.txt. There is a file 'cmdline.txt' which is passed/appended to the kernel providing it's boot parameters, including root=/dev/somewhere. A System.map has to exist for this kernel and is loaded. The entire package in /boot is about 40Megs, and you'd need a little headroom - say 50Megs total. This cannot have grub or lilo (which each think they are the only one about) asking them questions in X86 code.
Linux needs grub, lilo, or something. I'm no longer an expert on non-conformist booting. Alien's live usb, for instance, has a 1M boot partition that's teetotally blank :confused:. I've been sticking to old style techniques, and they have served me well.
There's very little room for maneuver in RazPi booting; I can specify a root=/dev/somewhere, but the rest has to be as I said.
So could I have the following setup?
The genesis of this is that I want to have some data available on both a RazPi, and a linux box, and I wondered if it could be done with one live usb key.
The RazPi boots without grub, or sector 0, AFAICT. The 1st partition has to be FAT32. There's a string of gpu firmware, memory allocation, cpu firmware, memory reallocation, peripheral firmware loaded & dealt with; there's several programs on /boot, one f which is loaded that does stuff, and a config.txt that's the equivalent of the BIOS peripheral setup. That config.txt loads the kernel which has it's name mentioned in config.txt. There is a file 'cmdline.txt' which is passed/appended to the kernel providing it's boot parameters, including root=/dev/somewhere. A System.map has to exist for this kernel and is loaded. The entire package in /boot is about 40Megs, and you'd need a little headroom - say 50Megs total. This cannot have grub or lilo (which each think they are the only one about) asking them questions in X86 code.
Linux needs grub, lilo, or something. I'm no longer an expert on non-conformist booting. Alien's live usb, for instance, has a 1M boot partition that's teetotally blank :confused:. I've been sticking to old style techniques, and they have served me well.
There's very little room for maneuver in RazPi booting; I can specify a root=/dev/somewhere, but the rest has to be as I said.
So could I have the following setup?
- RazPi boot
- x86_64 boot (perhaps with EFI). I have it disabled ATM.
- RazPi /
- X86_64 /
- DATA