From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: chained grub2 derivative bootauto system
Date: Sat, 01 Sep 2012 09:11:40 +0200 [thread overview]
Message-ID: <5041B52C.1000808@gmail.com> (raw)
In-Reply-To: <CAELHeEdggA_kx2ESuKXpFTF1aZpB03gM8LeUPQ8tbBSSoOnTxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
On 01.09.2012 08:06, Brendan Trotter wrote:
> Hi,
>
> On Fri, Aug 31, 2012 at 11:59 PM, Lennart Sorensen
> <lsorense@csclub.uwaterloo.ca> wrote:
>> On Fri, Aug 31, 2012 at 09:19:43AM +1000, Philip Rhoades wrote:
>>> Ivo,
>>>
>>> Interesting idea - I particularly like the idea of booting from
>>> arbitrary isos.
>>
>> Too bad that accessing an iso on a usb key is nothing like an actual cd
>> or dvd and the sytem you boot must have support for the fact you put the
>> iso on the usb key rather than as a real disc. Nothing the boot loader
>> can do to change that.
>>
>> If it was really that simple, someone would already have made such a
>> boot loader for use on usb keys. The reason it doesn't exist yet is
>> that it can't exist.
>
> For "PC BIOS", having a USB with multiple ISO images would actually be
> relatively easy.
>
> The USB's boot code would need to hook Int 0x15 to steal some memory,
> then install code that emulates a CD (and El Torito) into the stolen memory.
> Obviously you'd also hook "Int 0x13" so that the BIOS disk services are
> redirected to your CD emulation code.
>
> I'd expect that similar would be possible for UEFI (e.g. create a special
> UEFI driver that emulates CD/s).
>
> The main problem is after the OS on the ISO tries to take control of hardware
> and fails to find its (emulated) CD. For some OSs this may not be a problem -
> e.g. MS-DOS and FreeDOS (which continue to use the BIOS services
> and don't take control of hardware), Linux (as long as the root
> partition isn't on
> the emulated CD), etc. For other OS's (Windows) it can't work.
>
> However, someone that wants to create a USB like this might not care about
> those "unsupportable" OSs anyway.
>
> Finally; I'm not sure how a scheme like this would involve GRUB - you'd want
> relatively specialised USB boot code (not GRUB). GRUB could (potentially)
> be installed inside one or more of the ISOs, but this would be a normal
> "El Torito" (or UEFI) boot as far as GRUB would know.
>
This is something that can be included in GRUB. Just the amount of
needed work isn't comparable with the number of additional scenarios
supported (namely mostly only *DOS on ISO).
>
> Cheers,
>
> Brendan
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2012-09-01 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 21:20 chained grub2 derivative bootauto system ivo welch
2012-08-30 23:19 ` Philip Rhoades
2012-08-31 14:29 ` Lennart Sorensen
2012-09-01 6:06 ` Brendan Trotter
2012-09-01 7:11 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-08-31 5:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-08-31 14:43 ` Lennart Sorensen
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=5041B52C.1000808@gmail.com \
--to=phcoder@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.