From: Tom Rini <trini@kernel.crashing.org>
To: Ben LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: [PATCH] make nfsroot accept server addresses from BOOTP root
Date: Tue, 20 Feb 2001 11:20:42 -0700 [thread overview]
Message-ID: <20010220112042.A5639@opus.bloom.county> (raw)
In-Reply-To: <20010220104415.D3150@opus.bloom.county> <Pine.LNX.4.30.0102201248290.1614-100000@today.toronto.redhat.com>
In-Reply-To: <Pine.LNX.4.30.0102201248290.1614-100000@today.toronto.redhat.com>; from bcrl@redhat.com on Tue, Feb 20, 2001 at 01:12:28PM -0500
On Tue, Feb 20, 2001 at 01:12:28PM -0500, Ben LaHaise wrote:
> On Tue, 20 Feb 2001, Tom Rini wrote:
>
> > Er, say that again? Right now, for bootp if you specify "sa=xxx.xxx.xxx.xxx"
> > Linux uses that as the host for the NFS server (which does have the side
> > effect of if TFTP server != NFS server, you don't boot). Are you saying
> > your patch takes "rp=xxx.xxx.xxx.xxx:/foo/root" ? Just curious, since I
> > don't know, whats the RFC say about this?
>
> Yeah, that's the problem I was trying to work around, mostly because the
Er, the problem of having to use sa (which is TFTP server) to specify the
NFS server?
> docs on dhcpd are sufficiently vague and obscure. Personally, I don't
> actually need tftp support, so I've just configured the system to now
> point at the NFS server. For anyone who cares, the last patch was wrong,
> this one is right.
If the RFC doesn't say anything about the format rp= has to be in, this
is probably right. Assuming it works. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2001-02-20 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 23:12 [PATCH] make nfsroot accept server addresses from BOOTP root Ben LaHaise
2001-02-20 17:44 ` Tom Rini
2001-02-20 18:12 ` Ben LaHaise
2001-02-20 18:20 ` Tom Rini [this message]
2001-02-20 23:02 ` Russell King
2001-02-20 23:25 ` Tom Rini
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=20010220112042.A5639@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=alan@redhat.com \
--cc=bcrl@redhat.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