Re: Knoppix 7.4 and multiboot
On 9/22/14, s7r <s7r@sky-ip.org> wrote:
>
> I have a 32GB fast USB flashdrive. I have configured knoppix as follows:
>
> - From a virtual machine, Install knoppix to flash drive and selected a
> 10GB partition for filesystem and 19GB for overlay persistent
> partition. All good till now.
>
> What I want, in the 10GB of the first (boot) partition where knoppix
> system is installed to add more live ISO files (such as Tails, etc.)
> and be asked which one I want to boot (in a menu) every time at startup.
>
> Is this possible? Can I customize the boot config files in such a way?
I had a whole different email written up and realized I've stepped
outside my comfort zone here, that some of it might not apply
(especially file system related) because you're using flashdrive...
In my case where I'm booting from a hard drive, I've had fun with
this. I've made a number of different entries in /etc/grub.d/40_custom
BUT... I don't know how that would change for what you're trying to
do.. Flashdrive will be one of my own next self-education checkpoints
so biggest thing right now is I don't know how the file system looks..
For cognitive simplicity if nothing else, using multiple different
directories, one for each ISO, comes to mind if that's possible.
Again, that's where I'm iffy on what your file system looks like.
Those different directories would need to be created on the flashdrive
to make it self-contained.
An example menuentry item I've made for an HDD *HARD DRIVE*:
menuentry "give your entry a recognizable name here" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set=root (36 digit *serial* number from lshw)
linux /boot/vmlinuz root=UUID=(REPEAT SAME 36 digit *serial* number)
initrd /boot/initrd.img
}
BUT AGAIN, that IS going to change for what you're doing.
The "insmod ext2" applies to ext2, ext3, AND ext4.
"hd1" was a peripheral hard drive connected via USB.
"msdos3" was the third partition on ANY of my hard drives, regardless
of a given hard drive's UUID (unique identifier). In my case, that "3"
consistently corresponded to and booted from "sda3" and "sdb3",.
The UUID number is one of the most consistent ways to identify our
hardware. The CLI (command line interface) command I use to get that
is "lshw" (as root).. I'm sure there are other ways to get that ID
number, lshw just works fast and friendly for me.
Those /boot directory references there.. My multiple personalized
sub-directories went under that. Each was named for the ISO involved
and then contained all the necessary boot initiation files specific to
the single ISO. So in some of my menuentry items, you'd instead see
something like:
linux /boot/wheezy/vmlinuz root=UUID=(REPEAT SAME 36 digit *serial* number)
initrd /boot/wheezy/initrd.img
Your entire newly customized menuentry item goes in
/etc/grub.d/40_custom on the next line after it says:
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
LAST MUST-DO STEP is you save the /etc/grub/d/40_custom file and then
update. For GRUB2 as example, I use "update-grub". In my case, I can
then find the now updated custom menuentry items reflected in
/boot/grub/grub.cfg but I have no idea how that will turn out in your
case.. :)
I've got to move stuff outside where I work from.. I'll be around
later if you have questions, and no one else has written yet.. I'm
still real *green* at this but MIGHT be able to help you find
something by Internet searching based on personal experience.. :)
Cindy
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with duct tape *
Reply to: