On December 22, 2014, Nicholas Leippe wrote: > If your motherboard supports it, you could go full openbios--which
> flashes your kernel directly into the bios for very fast boot times. That's actually going in the opposite direction of the goal of the project, which was to minimize the number of places things had to be changed in the event of software updates. Openbios is nice, don't get me wrong. But I'd have to flash each machine, and then when a new kernel comes out, I'd have to re-flash each machine. Thanks but no thanks. --- Dan On Tue, Dec 23, 2014 at 4:56 PM, Chris <[email protected]> wrote: > On Mon, Dec 22, 2014 at 3:43 PM, Levi Pearson <[email protected]> > wrote: > > > The tftp protocol, which is the "standard" method of network booting > > Linux, is > > horrifically slow. > > > Here's one datapoint. > > Over gigabit ethernet, I typically see tftp downloads that run at a bit > over seven megabytes per second. > > Yes, it's a lot slower than local disk and a lot slower than the network > itself, but I wouldn't call it "horrific" if one is downloading only a few > tens of megabytes over tftp. Other parts of the system startup are likely > to have a greater impact on boot time than smallish tftp downloads over > gigE. (Subjectively, tftp over 100 megabit ethernet is a lot more painful, > though I haven't measured the actual corresponding download speed.) > > As the man said, YMMV, etc. > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
