[syslinux] isolinux.cfg location?
nazosan at gmail.com
Fri Dec 30 21:54:20 PST 2005
On 12/30/05, Andrey Vul <andrey.vul at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> what i did is:
> a) reassemble isolinux.asm and change isoliux_dir constant from isolinux
> to mod123. after compiling i opened isolinux.bin with a hexeditor and
> did an ascii search for mod123and replaced it with whatever
> b) ascii search in hexeditor for isolinux (press f3 or Ctrl+G or
> whatever until you get to ?/boot/isolinux? ? is unknown hex character)
> and replace with whatever
> so the result is this:
> /boot/whatever_1 <- item 1 menu
> /boot/whatever_2 <- item 2 menu
> /boot/whatever_N <- item 3 menu
> /boot/isolinux <- multi menu
> and the sweet part is that just add this line:
> label return
> kernel /boot/isolinux/isolinux.bin
> to return to main menu
> tried and true
> H. Peter Anvin wrote:
> | Nicolas Bigaouette wrote:
> |> Thanx for the feedback and the clarification.
> |> I tough of "merging" config files, but it's not quite the way I see the
> |> CD I'm creating. I'm booting that cd with CDShell, witch can load
> |> isolinux. I want to make a choice in CDShell of "Insert" or "Damn Small
> |> Linux". That choice would bring the same screen as if the computer was
> |> booted with the respective Live CD. Right now I'm calling CDShell's
> |> implementation of isolinux with the default parameters of those livecd.
> |> But I'd like to have the isolinux screen with the "boot:" prompt, the
> |> live cd's logo, the boot options, etc. I'm limited right now to just the
> |> default options.
> |> It seems possible to pass some options to isolinux as of
> |> http://cdshell.org/doc/cmdref.html#isolinux. Even if it says that the
> |> arguments would be interpreted by isolinux as if entered at the "boot:"
> |> prompt, it still seems possible for isolinux to "receive information"
> |> from CDShell or another boot loader booted before isolinux.
> |> If syslinux relies on a some variables being initialized at load time,
> |> it could relies also on some other variables to get the location of the
> |> configuration files. I don't really understand what you meant by "they
> |> would have to be reset before a new config file can be loaded"... I
> |> didn't meant "load a different config file from an already loaded
> |> isolinux" if this is what you tought I wanted...
> | The two problems are largely equivalent, though.
> | -hpa
> | _______________________________________________
> | SYSLINUX mailing list
> | Submissions to SYSLINUX at zytor.com
> | Unsubscribe or set options at:
> | http://www.zytor.com/mailman/listinfo/syslinux
> | Please do not send private replies to mailing list traffic.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Created with GnuPG
> -----END PGP SIGNATURE-----
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> Please do not send private replies to mailing list traffic.
Could you explain the final part of that a little more? I understand
the idea of replacing the directory name inside the compiled binary,
but, I can't see how changing it gives you this menu where you can
select the three different configuration files like this.
More information about the Syslinux