Hi Shao, On Tue, Jun 01, 2010 at 10:57:26PM +0800, Miller, Shao wrote: > Good day Fengguang, > > Well thanks to you, developers have more than one option to consider. > Merits of both submissions can be discussed, so perhaps yet another, > better submission can result.
Yeah, cannot agree any more. > In regards to your "kernel URL root=... initrd URL" preference, the > reason I chose a "cmd=..." approach is because I wished to avoid tying > the gPXE .lkrn prefix to any particular desired boot target type > (bzImage, in this instance). Lots of people boot to SAN, for instance, > or multiboot images like Xen or VMware. Good viewpoint. Sorry I was too Linux oriented ;) > You are quite right in that a gPXE script as initrd could provide more > than a passed command-line could. Keeping booting choice parameters all > in one file (syslinux.cfg, grub.conf, etc.) makes for > "one-stop-shopping," though. Right, some users may favor the command line. Thanks, Fengguang _______________________________________________ gPXE-devel mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe-devel
