On Tue, Feb 20, 2001 at 11:02:10PM +, Russell King wrote:
> 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 sy
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
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
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
On Mon, Feb 19, 2001 at 06:12:12PM -0500, Ben LaHaise wrote:
> Here's a handy little patch that makes the kernel parse out the ip
> address of the nfs server from the bootp root path. Otherwise it's
> impossible to boot the kernel without command line options on diskless
> workstations (I hate R
Hello,
Here's a handy little patch that makes the kernel parse out the ip
address of the nfs server from the bootp root path. Otherwise it's
impossible to boot the kernel without command line options on diskless
workstations (I hate RPL).
-ben
diff -ur v2.4.1-ac18/fs/nfs/nfsroo
6 matches
Mail list logo