<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
The Mad One wrote:
<blockquote type="cite" cite="mid:876947.73447.qm@web27907.mail.ukl.yahoo.com">
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top" style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;">
<div id="yiv163490987">
<div id="yiv163490987">Hello to everyone,<br>
<br>
I'm working on my ACS thesis & I'm stuck on how to classify gPXE's
network booting in the way it is used by a solution like DRBL (Diskless
Remote Boot in Linux).<br>
<br>
I know it's a sort of "OS streaming" solution, but can OS streaming be
classified as a VDI solution ? <br>
[because in some manner it is virtualizing the hard drive of the
desktop computer, but the OS is running on bare metal (on that desktop
computer) not in a VM]<br>
<br>
VDI= Virtual Desktop Infrastructure.<br>
<br>
Please, help me solve this dilemma.<br>
<br>
Thanks in advance,<br>
TheMadOne.<br>
</div>
</div>
</td>
</tr>
</tbody>
</table>
<br>
</blockquote>
<tt>Ugh. "Virtualization": <a href="http://en.wikipedia.org/wiki/Virtualization" class="moz-txt-link-freetext">http://en.wikipedia.org/wiki/Virtualization</a><br>
<br>
Is the term used enough in the industry, do you think? Its utterance
makes potential consumers' eyes light up with "Yeah, I've heard about
that stuff!" </tt><tt>Marketing. </tt><tt>Fluff. Ugh.<br>
<br>
With a BIOS INT 0x13 HDD I/O consumer like DOS, gPXE could very well be
the sole disk provider and you could consider that to be OS streaming.<br>
<br>
Where gPXE "hands off" and is no longer invoked to provide disk I/O,
then perhaps you could consider gPXE to be a critical component as part
of an OS streaming strategy.<br>
<br>
But gPXE can also provide UNDI and PXE, functioning as a network stack
for UNDI and PXE consumers, such as DOS or some pre-OS boot-loader or
some other product.<br>
<br>
But gPXE can also run scripts and Syslinux COMBOOT modules.<br>
<br>
Surely gPXE is a network boot-loader... But it's more. :) I guess
"gPXE is cool" isn't thesis material. :S<br>
<br>
Where gPXE provides the disk for DOS, the OS would still be running on
the client computer rather than on a server... But then again, perhaps
DOS is running solely to provide thin access as a terminal to server,
where a majority of the processing and user experience would be hosted.<br>
<br>
Perhaps you could classify it as "network boot-loader" and "network
stack" and "SAN stack" for your discussion?<br>
</tt>
</body>
</html>