Could you submit a problem report (either using send-pr), or via
	the www.netbsd.org webpages, indicating which areas of diskless
	chould be better worded (to ensure this doesnt fall through the
	cracks).

	Thanks
		David/absolute

                  -=-  Resentment is a renewable resource  -=-

On Tue, 9 Jun 1998, Claude Foley wrote:

> Hi,
> 
> It makes a lot of sense, I think that now I understand what chroot does.
> Thanks.
> 
> But I think that the diskless man page should be updated,
> following the instructions there lead to this problem and another
> one about the file /etc/exports because /export/myclient is not
> a mount point. Also instead of writing populate /_ it should be
> written populate /export/myclient/root/(etc, bin, sbin) it was not
> obvious to me. But it is not that important so when it will be the
> last thing on the TODO list it should be done.
> 
>  ----------
> From: Christoph Badura
> To: netbsd-help@NetBSD.ORG
> Subject: Re: boot over network
> Date: Tuesday, June 09, 1998 1:14PM
> 
> 
> Claude.Foley@cns.eds.com (Claude Foley) writes:
> 
> >For tftpd I just commented out the line in inetd.conf and
> > -s /tftpboot is there so it should work.
> 
> >What I did to figure out the problem is simple.
> >tftpd was running on the server( calisto ) and I did tftp calisto( on
> >calisto ).
> >the file /tftpboot/C0A80102 was created as a symbolic link.
> 
> >It is weird because the fact that the file was a link should be
> >transparent to tftpd
> >unless tftpd really want to do something special with links.
> 
> This isn't weird at all.  Because you used "-s /tftpboot", tftpd
> does a ``chroot("/tftpboot")'' before accessing any files, which makes
> /tftpboot the root directory of the file system.  And since the symlink
> points to outside that file system, you can't access the file behind the
> symlink.
> 
>  --
> Christoph Badura
> 
> Now available in print: Lion's Commentary on UNIX 6th Edition, with
> Source Code
> 			http://www.peer-to-peer.com/
>