Good, I thought this volume name is passed to kernel and you had that in mind, that's why I gave the link to msfn topic. I guess I should know how to get the volume name
The volume label I am referring to is the name given to the CD-ROM while burning it. When creating an ISO using mkisofs it is referred to as the volid....
About the first- it worked without specific label from USB disk, using 2.2 version. Haven't tried for CD yet.
The comment is related to Parted Magic. It insists upon compliance with the following:
In addition, upon extracting the downloaded Parted Magic ISO it creates isolinux.cfg, syslinux.cfg, sample_pxelinux.cfg in the root of the multi-boot CD-ROM.
- The multiboot CD-ROM volume label is "Parted Magic"
- The downloaded Parted Magic ISO is extracted to the root of the multiboot CD-ROM. It cannot be located anywhere else.
Second- it might be possible, location of the files is passed as kernel parameters. May be a little play with that could lead to a solution.
Downloaded it and extracted to USB disk, transferred the kernel parameters to menu.lst. In QEMU it fails, but on real machine it loads just fine. There is a little delay where it sits on a black screen seemingly doing nothing, I guess it's loading filesystem.squashfs. After a minute or so everything is loaded. From a CD this could be slower. Haven't tested it on CD yet, but I'd like to prove you wrong
This was partly answered earlier in this post where you refer to "As for the second part-". In addition Clonezilla has proved difficult to load using this method. Calling the kernels directly also has the disadvantage of bypassing the isolinux inside the ISO and thereby potentially not starting as the developer intended. http://www.clonezill...ad/sourceforge/
Release: 20080511-hardy is the version I am testing as this about to be released as the next version.
Tynibit and Jaclaz mentioned about more "inteligent" distributions. I'll give you an example- Debian install from HD-like media.
On the disk you place only initrd and the kernel, wherever you like as you can change path to them in menu.lst. Since it's only these 2 files, they could be on a mapped ISO, IMG- doesn't matter. Next step is to place the actual netinstall.iso in root of disk, containing the packages and other stuff for the installer. When kernel is loaded, it seeks for the ISO, mounts it and uses it.
If more "live" distros are using the same approach, you can imagine how your goal would be easily accomplished.
When more and more people require this functionality, I guess developers would start implementing it. Shouldn't be a big deal to make their live distro work the same way, but for now that's what we got.