The only workaround I can think of is gPXE booting a stripped down Win/WinPE
that boots directly into your linux.iso through virtualization software. Then
Windows took care of the hooking and linux did not know it was actually running
in ram. It would of course add substantially to the boot time and required ram,
and may not be very easy to configure quickly. If it was for installing linux
locally, then it would be pointless. Very likely no one would bother with this,
at least I can't think of any good reason (except for the fun of testing and
verification).
At least it works with vmware.
Joakim Schicht
Date: Fri, 14 May 2010 15:24:27 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [gPXE] gPXE booting an .iso image
Oh ok, thanks a lot.
So there is no way to gPXE a Linux .iso image yet, right?
Thanks,
Luca
On Fri, May 14, 2010 at 3:21 PM, Miller, Shao <[email protected]>
wrote:
Good day Luca,
There is not yet a MEMDISK driver for Linux, so your .ISO file in RAM
will not be available when Linux is running. Linux doesn't use BIOS INT
13h for disk access, which is what MEMDISK hooks.
- Shao Miller
_________________________________________________________________
Windows Live™ Mail. Flere kontoer på ett sted.
http://download.live.com/wlmail_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
