<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Joakim Schicht wrote:</tt>
<blockquote type="cite" cite="mid:SNT102-W317FFDD0EA4960388A9576B2960@phx.gbl">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style><tt>You
can read about how to boot a full XP from...</tt></blockquote>
<tt><br>
Thanks.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:SNT102-W317FFDD0EA4960388A9576B2960@phx.gbl"><tt>I have not yet dived into iSCSI booting, but will soon
do. Btw, is that possible to boot over WAN? Is your setup documented
anywhere?<br>
</tt></blockquote>
<tt><br>
AoE is a SAN protocol which doesn't use IP, and is restricted to an
Ethernet broadcast domain. iSCSI uses IP and is thus routable.
Assuming all routers and firewall rules allow port 3260 (or some other
port of your choosing), you can certainly iSCSI-boot across the
Internet.<br>
<br>
My setup is quite simple. I use IETD to serve the SAN (iSCSI target)
on some Knoppix 3.4 box. All workstations PXE-boot to a PXELINUX
menu. One of the menu.c32 config-file options is:<br>
<br>
LABEL ramxp<br>
PXE ramxp.0<br>
<br>
where ramxp.0 is actually 'make EMBEDDED_IMAGE=ramxp.gpxe
bin/undionly.kkpxe' and ramxp.gpxe is:<br>
<br>
#!gpxe<br>
ifopen net0<br>
sleep 5<br>
dhcp net0<br>
sanboot iscsi:ctrl.mydomain.com::::ctrl:ramxp<br>
<br>
where the SAN is a simple 300 MB HDD image with one FAT32 partition
with SYSLINUX installed. The contents are:<br>
<br>
/ldlinux.sys<br>
/syslinux.cfg<br>
/memdisk<br>
/RamXP.HDD<br>
<br>
where syslinux.cfg is simply:<br>
<br>
DEFAULT ramxp<br>
LABEL ramxp<br>
KERNEL memdisk<br>
APPEND raw<br>
INITRD RamXP.HDD<br>
<br>
It loads quite reasonably quickly. HTTPDisk is a another, different
option and is an experimental SAN protocol not in gPXE proper, but
performance seems pretty poor; caching might improve this someday.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:SNT102-W317FFDD0EA4960388A9576B2960@phx.gbl"><tt>Btw, I am the same Joakim that tested your winvblock
driver a few months ago.<br>
</tt></blockquote>
<tt><br>
I thought you might be. Cool. :) We can thank V. for the majority of
the work in WinVBlock, which derives from V.'s WinAoE.<br>
<br>
- Shao Miller</tt>
</body>
</html>