How can the answer be improved?
Active4 years, 1 month ago
I'm trying to make a multiboot usb with Ubuntu, Backtrack and Mantra-OS on it (all ubuntu as you can see). Those are the steps I've done:
After that I mounted and copied files in the respective ISOs to folders I've made:
After that I filled on the configuration file
syslinux.cfg in /media/diqus/syslinux with this:
(anon1.png: 640x480 8bit png in /media/disqus/syslinux/)
Now everything is going alright and I'm able to boot, I have the syslinux menu and even load vmlinuz and initrd! The os is actually loading (I have the splash screen) but then I have the error (something about Busybox):
I'm not quite sure what's the problem but I think it's about relative paths and the CDROM 'thing'. Ps2 bios download mediafire. I've tested many of them (even relative and absolute) but nothing works.
The answer must not be about MultiBootUSB, MultiSystem, Yummi or any other tool; it must not be also about grub or grub2 or any other bootloader. I want to make my approach work.
pr.nizar
pr.nizarpr.nizar
2 Answers
I actually solved this and it works!I found a cheat code called: live-media-path=path/to/casper/folder along with ignore_uuid.So the modified working code:
Many thanks!
P.S: For other distros you may look for syslinux configuration files in Yumi's repository at GitHub: https://github.com/bwnickle/YUMI/blob/master/src/menu/
pr.nizarpr.nizar
Ok, since you aren't interested in alternate solutions, then you are going need to take more time to understand how the book process works.
The bootloader loads the kernel and initrd into memory, and then passes execution to the kernel. After that point all execution is passed off to the init/upstart process in the initrd, and any scripts that first process calls. The scripts within the initrd, do not really know anything about the filesystem, or relative pathos of where it was loaded from. They cannot simply reference some big caspar filesystem in that directory.
The Initrd of livecds, contain scripts that permit them to locate the filesystem. For Ubuntu system it looks for a particular file in a particular folder within the root of every known filesystem on every drive that it can see. If it cannot find anything you get the error you mentioned.
You can pass the
ISO-SCAN option to as part of your append line. This argument will tell the script that instead of scanning filesystems, it will loopback mount an ISO, and read the files from within that.
![]()
Just dropping files in some random directory you define is probably not supported. I haven't looked at the livecd initrd scripts lately, but I am not aware of any options that permit you to specify some arbitrary directory for the extracted files.
If you want behavior that hasn't already been designed by the developers, then you are going to have to re-build your initrds with your own scripts and tools to load the root filesystem. Leaving the ISO on the filesystem, and then using the
iso-scan/filename=$isofile option is the method you can use without having to rebuild your initrd.
I Will Always Love You.mp3 4.14 MB 02. After We Make Love.mp3 7.01 MB 01. I Have Nothing.mp3 4.43 MB 03. Run to you.mp3 4.04 MB 05. Whitney houston discography torrent. I'm Every Woman.mp3 4.38 MB 04.
Community♦
ZoredacheZoredache
![]()
17.7k77 gold badges4444 silver badges6868 bronze badges
Isolinux Bootable UsbNot the answer you're looking for? Browse other questions tagged multi-bootliveusbsyslinux or ask your own question.Comments are closed.
|