Subject: Re: tftp on 1.3
To: None <mason@primenet.com.au>
From: Andrew Gillham <gillhaa@ghost.whirlpool.com>
List: current-users
Date: 02/27/1998 09:23:50
Geoff Wing <gcw@pobox.com> wrote:
 
> There was a significant change that nobody was told about - that I know of.
> I was going to send in a patch (after writing it) but I've put it off for
> a while.
> 
> Put a ``/'' in front of all filenames.
> 
> My concern is that this is not really necessary in some cases, viz. when you
> have used the ``-s'' option.  From the manual page:
>    -s  tftpd will chroot(2) on startup; therefore the remote host is not
>        expected to pass the directory as part of the file name to transfer.

Grrr, now I know why my NetBSD 1.3 machines are no longer usable as a tftp
server for my cisco equipment!  Is there a good reason this was changed? 
Particularly when '-s /tftpboot' is used? 
If anyone already has a working patch, please mail it to me, otherwise I'll
have to come up with one today at work.

I don't want to sound like I'm whining (which I am), but I use a NetBSD
machine for a tftp server, and for rsh/rcp services with our cisco router
network.  With 1.3, these were *all* broken for me.  The rsh/rcp problem
is related to NIS, which I can disable to make it work ok. (though I have
a patch that makes it work with NIS)

-Andrew
-- 
-----------------------------------------------------------------
Andrew Gillham                            | This space left blank
gillham@whirlpool.com                     | inadvertently.
I speak for myself, not for my employer.  | Contact the publisher.