<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Wu Fengguang wrote:</tt>
<blockquote type="cite" cite="mid:20100602130456.GB7764@localhost">
<title>Re: [gPXE-devel] [PATCH][lkrn] add cmdline and ramdisk support</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">Hmm, autoboot defaults to the TFTP download
protocol given the<br>
filename option. This drops a big strength of gPXE.. And you'll need<br>
another option for kernel parameters (and need to handle spaces in<br>
between).<br>
</font></tt></p>
</blockquote>
<tt><br>
' filename=<a href="http://webserver/foo" class="moz-txt-link-freetext">http://webserver/foo</a> ' would do the trick. If such
command-line processing simply sets the corresponding DHCP options,
gPXE already looks at the protocol in this DHCP option and uses it.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:20100602130456.GB7764@localhost">
<p><tt><font size="2">You mean the x_cmd:// URI? That's pretty clean
for implementation,<br>
however sounds ugly as a user interface.<br>
</font></tt></p>
</blockquote>
<tt><br>
Absolutely agreed. Just a possibility. It could even be compiled as
an optional feature and should not require any changes to current gPXE
files, as far as I can tell.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:20100602130456.GB7764@localhost">
<p><tt><font size="2"><br>
How about this cmdline syntax:<br>
<br>
APPEND #!gpxe; dhcp net0; kernel URL root=...; boot;<br>
<br>
- the '#!gpxe' declares the start of a gPXE script (this will exclude<br>
the BOOT_IMAGE=... added by GRUB)<br>
<br>
- the followed ';' declares that the semicolon will be treated as<br>
the DELIMITER (think about the '/' in :s/a/b/ for vim)<br>
<br>
- each gPXE must end with the DELIMITER, ie. the last ';' is not<br>
optional (this will exclude the BOOT_IMAGE=... appended by PXELinux)<br>
<br>
> I'd really enjoy reading what the gPXE core developer usual
suspects<br>
> have to offer. :)<br>
</font></tt></p>
</blockquote>
<tt><br>
The February 12th, 2009 incarnation[1] (not the original January
incarnation) used ';' as command delimiter, so I don't disagree with
you, there. Since the boot-loader-appended ' BOOT_IMAGE= ' should fall
after the last command (which should do some booting), it would
favourably be ignored... Unless the booting command should fail, of
course.<br>
<br>
To be honest, concerns around decisions regarding command syntax have
been blocks against my submissions for initrd+cmdline and gPXE
CLI/scripting enhancements, historically, as Stefan has just confirmed.<br>
<br>
Stefan Hajnoczi wrote:
</tt>
<blockquote type="cite" cite="mid:AANLkTimnkggKOpervEi9mOCd0lgL7mVd5EIJauoV2qHs@mail.gmail.com">
<title>Re: [gPXE-devel] [PATCH][lkrn] add cmdline and ramdisk support</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">How bad is it if only initrd is supported, no
lkrn commandline?<br>
<br>
Then we don't need to worry about new syntax and code for parsing
command lines.<br>
</font></tt> </p>
</blockquote>
<tt><br>
Wu Fengguang wrote:
</tt>
<blockquote type="cite" cite="mid:20100602131735.GA8895@localhost">
<title>Re: [gPXE-devel] [PATCH][lkrn] add cmdline and ramdisk support</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">At least I can do with initrd.<br>
<br>
I would appreciate if the initrd feature can merged ASAP.<br>
<br>
Please don't let the unresolved command line UI stand in the way :)</font></tt></p>
</blockquote>
<tt><br>
It seems reasonable to be able to split them apart.<br>
<br>
[1]
<a href="http://sourceforge.net/mailarchive/message.php?msg_name=F0E5F8699DE1364584CDB894E99713551187F589%40YRDSB5.YRDSB.YRDSB.NET" class="moz-txt-link-freetext">http://sourceforge.net/mailarchive/message.php?msg_name=F0E5F8699DE1364584CDB894E99713551187F589%40YRDSB5.YRDSB.YRDSB.NET</a></tt><tt><br>
</tt>
</body>
</html>