[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ITH: tftpd-hpa and tftpd servers default rootdirs



On Fri, Jan 02, 2004 at 01:48:25AM +0200, Jaakko Niemi wrote:
> On Thu, 01 Jan 2004, Daniel Jacobowitz wrote:
> 
> > On Thu, Jan 01, 2004 at 11:07:47PM +0200, Jaakko Niemi wrote:
> > >  I hereby announce my intentions to hijack tftp-hpa source
> > >  package. I mailed the currently listed maintainer recently,
> > >  but haven't heard back yet. 
> > > 
> > >  While preparing new version, I looked at the defaults and
> > >  noticed that our various tftpd packages use most horrible
> > >  defaults for the directory that tftpd serves out. atftpd
> > >  defaults to /tftpboot, netkit-tftpd defaults to /boot 
> > >  and current version of tftpd-hpa goes for /var/ftpd. 
> > > 
> > >  After thinking this a bit, I could only come up
> > >  with /var/lib/tftp or /var/lib/tftproot. Comments?
> > 
> > In my experience, /tftpboot is pretty standard for this sort of thing. 
> > I certainly don't think it belongs under /var/lib...
> 
>  Standard according to what? Not FHS at least, and we don't have

As I said, "my experience".  That's where people use it, document it,
et cetera.  For instance, a lot of embedded development products
include documentation on installing a TFTP server on your host and
configuring it; they tend to reference /tftpboot.

>  binaries in /etc either anymore. Could we get rid of the assumption
>  that tftp is used only for booting other systems? There is no

What else would you use it for?  No, seriously, I'm curious.  It's such
a half-assed excuse for a file transfer protocol.

>  practical reason on this age anymore to keep it in / as we have
>  enough disk space so that we don't need to symlink the kernel
>  and base system images to another directory in root filesystem.
> 
>  Out of all over fourty tftpd installations that I've seen, only 
>  two used /tftpboot and the operating systems were over decade
>  old. As for other distributions, at least Mandrake and RH seem
>  to ship with default being in /var/lib.

Most of my currently-in-use targets require me to type the boot path at
least a couple of times a day.  So I dislike anything that makes it
deeper :)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer



Reply to: