I've gone back to various man pages to make sure I'm not trying to do
anything too strange but I haven't looked at the ltsp_nbd script.  From
the in-tftpd man page, using "-s <path>" is recommended for security so
I'd like to be able to carry on using it.

Also, I have now spotted that I'm pointing to /opt/ltsp/i386/boot for
in.tftpd and was expecting lts.conf to be read from
/var/lib/tftpboot/ltsp/i386.  I diff'ed the 2 directories and they are
identical except that lts.conf was only in one.  This isn't a big
surprise as I put it there :)  I can't remember what documentation
pointed me to those paths but trying to find it now, everything I read
is using different paths.

I suspect, from Oliver's comment just before this one, that adding "/"
to my filename line in dhcpd.conf might workaround the problem.  However
this will only work as long as all tftp'd files are in the same
directory (obviously).  Please can someone point me to something which
tells me (or just tell me) why I have two directories with the same
contents and which I should consider to be the "master".  Then I'll use
that directory consistently and try out the extra "/".

-- 
/var/lib/tftpboot/ltsp/i386/lts.conf not accessed
https://bugs.launchpad.net/bugs/377916
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to