Jaakko Niemi a écrit :
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. atftpddefaults 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...
In my experience, /var/whathever/tftpwhathever works pretty well too. (I've been using /var/local/tftpboot for some time now).I do think it belongs under /var 'cause its a pretty growable rw directory (think about providing netboot-d-i image for all the arch, <> TX booting, routers, switches, printers conf etc....).
Standard according to what? Not FHS at least, and we don't have binaries in /etc either anymore. Could we get rid of the assumption that tftp is used only for booting other systems? There is no 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.
Seconded, but two suggestions :- keep "tftpboot" as the last part of the directory name ... Will be more in sync with general documentation.
- Having a chat on FHS/LSB lists to see what consensus you can get. @+, Fab