Date: Wed, 23 Oct 2002 17:43:40 -0400 From: Feng Li <fengli@kddia.com> To: "Christopher Meiklejohn" <cmeiklejohn@conversent.com> Cc: "Brian Jackson" <b.k.jackson@verizon.net>, "Kris Kennaway" <kris@obsecurity.org>, <freebsd-questions@FreeBSD.ORG> Subject: Re: Is there any info about this type tftp daemon ? Message-ID: <20021023172926.5E5F.FENGLI@kddia.com> In-Reply-To: <DKENILALFPBIMOOGMNBFGEKKKFAA.cmeiklejohn@conversent.com> References: <3DB70628.2040103@verizon.net> <DKENILALFPBIMOOGMNBFGEKKKFAA.cmeiklejohn@conversent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Friends About this issue, the reason I asked is because I once used a TFTP server when I was in my previous company. This was a Sun box with Solaris 2.6. On that server, if you send file to that server, you don't need to make an empty file on it before you send, it saved us a lot of time. I believe it is another edition of tftp daemon. The bad thing is that I didn't dig enough to get the info for where the specific tftp program came from. I just hope that different edition tftp application in the world somewhere and someone knows it, but it seems that I was wrong ... Thanks, Feng > Taken from the man page: > > "Files can be written only if they already exist and are > publicly writable. " > > --Chris > > <snip> > > > > I know that on some old Sun systems I had to manage, I had to "touch > > <filename>" and make sure it was writable before we could get files to > > it. In other words, make a 0 length file of the name of the file you > > are trying to tftp to the server first, and when you do the transfer it > > will overwrite it. Might be the same issue? > > > > Brian > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021023172926.5E5F.FENGLI>