From: Russell King <rmk@arm.linux.org.uk>
To: bcrl@redhat.com (Ben LaHaise)
Cc: trini@kernel.crashing.org (Tom Rini),
linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: [PATCH] make nfsroot accept server addresses from BOOTP root
Date: Tue, 20 Feb 2001 23:02:10 +0000 (GMT) [thread overview]
Message-ID: <200102202302.f1KN2B423460@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.30.0102201248290.1614-100000@today.toronto.redhat.com> from "Ben LaHaise" at Feb 20, 2001 01:12:28 PM
Ben LaHaise writes:
> Yeah, that's the problem I was trying to work around, mostly because the
> 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.
This is the dhcp entry for a host that I use to tftp a kernel from a
different machine to that running dhcpd:
host tasslehoff
{
hardware ethernet 00:10:57:00:03:EC;
fixed-address tasslehoff;
next-server raistlin;
filename "/usr/src/k/tasslehoff";
}
The booting host is called "tasslehoff". The tftp server host is called
"raistlin", and the dhcp server is called "flint".
According to Tom, this should also cause Linux to nfs mount from the
"next-server" address, and it is fair that this is not documented by
the dhcp man pages since it appears to be a Linux Kernel quirk.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-02-20 23:05 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
2001-02-20 23:02 ` Russell King [this message]
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=200102202302.f1KN2B423460@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@redhat.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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