Inclusion into custom bootdisk difficult after version 100
In the past I trivially added Finnix v100 to my multi-purpose grub-based USB stick like this:
# cat boot/images/
title Finnix v100 x86-64 Linux 2.6.32 (2010-10-28)
kernel /boot/images/
initrd /boot/images/
title Finnix v100 i386 Linux 2.6.32 (2010-10-28)
kernel /boot/images/
initrd /boot/images/
title Go Back
configfile /boot/grub/menu.lst
# ls -l boot/images/
total 125968
-rwxr-xr-x 1 root root 2676709 Oct 26 2010 initrd.gz
-rwxr-xr-x 1 root root 66 Jun 26 2013 md5sums
-rwxr-xr-x 1 root root 121585664 Oct 26 2010 root.img
-rwxr-xr-x 1 root root 2299296 Oct 25 2010 vmlinuz.x86
-rwxr-xr-x 1 root root 2413824 Oct 25 2010 vmlinuz.x86-64
where initrd.gz, root.img, and the 2 kernels were taken directly off the Finnix v100 iso. Everything worked and was happy
However when I tried to do the same with the current version 108 and any version back to 101 - I keep getting stuck with Finnix not being able to find itself on the USB once the boot starts. It's almost if finnixfile= is no longer respected at boot.
I suspect it is something exceedingly simple that I need to add to make the USB stick "recognizable". I would really like to avoid overengineering stuff with syslinux - grub1 boots on pretty much everything off a USB these days, and has a rather nice UI.
Is this easily fixable?
Thank you!
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Finnix Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Peter Rabbitson for more information if necessary.