From: adrian15 <adrian15sgd@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Chainloadig from grub2 to isolinux
Date: Thu, 07 Aug 2014 19:59:04 +0200 [thread overview]
Message-ID: <53E3BE68.1080703@gmail.com> (raw)
In-Reply-To: <20140807175225.4ecdfcbd@rsbsd.rsb>
El 07/08/14 16:52, Beeblebrox escribió:
>>> If you use loopback.cfg as intended it will all work.
> loopback.cfg contains the linux/initrd entries relevant to each distro's iso (or at least that's what the wiki page shows). That's exactly the problem - each iso has different settings for linux/initrd entries, and if you get them wrong, it really does not matter what file the entry was placed in.
>
> Also as confirmed by ben, it's apparently not going to work on a number of Debian-based iso's. Usually the solution is to include casper in the CD to make this happen AFAIK.
As part of us releasing Rescatux as an isolinux based distro (before
it was a super grub2 disk (or grub2) based distro) I am supposed to work
with Debian Live people so that any Debian live cd has a default working
loopback.cfg file.
Not sure if I'm going to do it in the next Rescatux stable release
but definitively is in my TODO list.
Probably the most intelligent workaround for this problem is doing an
isolinux.cfg, pxelinux.cfg or syslinux.cfg parser for grub2 in a similar
way to the menu.lst parser.
As pxelinux.cfg has now some submenues I'm not sure that would work
too good. I, personally, don't think it's worth the effort to implement
such a parser but if you want it so much please implement it.
I, personally, going to advocate for the loopback.cfg method.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
next prev parent reply other threads:[~2014-08-07 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:46 Chainloadig from grub2 to isolinux Beeblebrox
2014-07-02 9:48 ` Vladimir 'phcoder' Serbinenko
2014-07-02 13:37 ` Beeblebrox
2014-07-02 13:46 ` Vladimir 'phcoder' Serbinenko
2014-07-02 14:52 ` Beeblebrox
2014-07-02 15:00 ` Vladimir 'phcoder' Serbinenko
2014-07-08 13:39 ` Raif S. Berent
2014-07-08 15:47 ` Andrey Borzenkov
2014-07-08 22:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 19:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 21:37 ` Ben Hildred
2014-07-21 21:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 21:55 ` Raif S. Berent
2014-07-21 22:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-22 4:24 ` Ben Hildred
2014-07-22 10:37 ` tuxracer
2014-07-22 11:04 ` Vladimir 'phcoder' Serbinenko
2014-07-22 12:44 ` tuxracer
2014-08-07 14:52 ` Beeblebrox
2014-08-07 17:59 ` adrian15 [this message]
2014-09-21 17:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E3BE68.1080703@gmail.com \
--to=adrian15sgd@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.