From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: netboot broken ?
Date: Sun, 12 Feb 2006 11:03:44 -0800 (PST) [thread overview]
Message-ID: <dso0qg$25j$1@terminus.zytor.com> (raw)
In-Reply-To: 1138378138.4801.9.camel@obsidian
Followup to: <1138378138.4801.9.camel@obsidian>
By author: "Bryan O'Sullivan" <bos@serpentine.com>
In newsgroup: linux.dev.kernel
>
> On Fri, 2006-01-27 at 08:16 +0100, Knut Petersen wrote:
>
> > Any ideas? Can anybody please
> > - confirm that network booting does still work
> > - confirm that it is broken.
>
> Network booting has been in limbo for years, and hasn't had a lick of
> maintenance in approximately forever. The way forward is supposed to be
> via initramfs, but nobody is testing the nfsroot code in there, so it
> has a fair probability of not working.
>
Feel free to pull the unified git repository and help test:
git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-klibc.git
I really would appreciate both positive and negative bug reports.
-hpa
prev parent reply other threads:[~2006-02-12 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 7:16 netboot broken ? Knut Petersen
2006-01-27 8:15 ` Magnus Damm
2006-01-27 16:08 ` Bryan O'Sullivan
2006-02-12 19:03 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dso0qg$25j$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox