I take it back.

I reduced the client name to 'c' and the path to /export/c/root and it 
works.


Regards,
Sean Hafeez

"An armed society is a polite society. Manners matter when a man may 
have to back-up his actions with his life." -Robert Heinlein
On Sep 2, 2004, at 3:17 AM, Bernd Sieker wrote:

On 02.09.04, 01:10:04, Sean Hafeez wrote:
> I have read all the docs more then once.
>
> I have an SS20 that I am trying to netboot to install the last build of
> -current (ie. 2.0). My netboot server is an i386 running OpenBSD3.5.
>
> The SS20 is setup to be 192.168.64.45 and the OBSD box is 192.168.64.9.
> The system boots past the TFTP to the NFS part and..
>
> The error on the SS20 is...
>
> root addr=192.168.64.9 path=
                               ^^^^^^

it seems there is a length limit to the path. I was having the same
problem (NetBSD server) and using a shorter root path worked.  (In
my case the difference between "/export/sparc64/aurora/root" and
"/export/sparc/aurora/root" made all the difference. If the path
is too long, the client somehow recieves an empty string, not a
truncated version. I don't know if the limitation is in the dhcpd
or in the client bootloader.

> Can't open NFS network connection on '.....bla bla bla correct sun OF
> path to nic'
> Cannot load netbsd: error=13
>
> So..(on the OBSD box):
>
> [/]:cat /etc/exports
> /data
> /export/client/root -maproot=root client.beastproject.org

Does it literally say "client" here, or some other (longer) string?
The rootpath given here should be short enough, unless OpenBSD's
dhcpd has an even shorter limit (seems unlikely).

>
> [/]:cat /etc/hosts
>
> ::1 localhost.beastproject.org localhost
> 127.0.0.1 localhost.beastproject.org localhost
> 192.168.64.45 client.beastproject.org client
> 192.168.64.9 merlot.beastproject.org merlot
>
> [/]:cat /etc/dhcpd.conf
> allow bootp;
> authoritative;
> always-reply-rfc1048 true; 	#tried with and without
>
> shared-network LOCAL-NET {
>         option  domain-name "beastproject.org";
>         option  domain-name-servers 192.168.64.9;
>
>         subnet 192.168.64.0 netmask 255.255.255.0 {
>                 option routers 192.168.64.1;
>
>                 range 192.168.64.32 192.168.64.64;
>         }
>
> host client.beastproject.org {
>         hardware ethernet       08:00:20:75:f1:a3;
>         fixed-address           192.168.64.45;
>         option host-name        "client";
>         option root-path        "/export/client/root";
>         next-server             192.168.64.9;	#tried with and without

Is the "next-server" the same as the dhcpd server? If not, try
putting "next-server" before "root-path".

Are there, by any chance, more than one dhcpd running in the net?

>         }
> }
>
> [/export/client/root]:ls -la netbsd
> -rwxrwxrwx  1 root  wheel  3622206 Sep  1 17:49 netbsd*
>
> [/export/client/root]:ps -aux | grep nfs
> root        95  0.0  0.1   136   128 ??  Is     3:47PM    0:00.00 nfsd:
> master (nfsd)
> root     10920  0.0  0.1   128    96 ??  IL     3:47PM    0:15.94 nfsd:
> server (nfsd)
> root      4630  0.0  0.1   128    96 ??  IL     3:47PM    0:00.00 nfsd:
> server (nfsd)
> root     14277  0.0  0.1   128    96 ??  IL     3:47PM    0:00.00 nfsd:
> server (nfsd)
> root      1746  0.0  0.1   128    96 ??  IL     3:47PM    0:00.00 nfsd:
> server (nfsd)
>
> [/export/client/root]:ps -ax | grep port
> 23175 ??  Is      0:00.01 portmap
>
> [/]:ps -ax | grep mount
> 17944 ??  Is      0:00.02 mountd
>
>
> and I can see the NFS share from another box so I know that it is
> exported. I also tried with /export/client/root exported to the world.
>
> What am I missing?
>
> Help please!
>
>
> Thanks!
>

-- 
Bernd Sieker

NetBSD - your basement or mine?
		-- Julian Assange