> Choi,
>
> I was able to successfully netboot this kernel. Here's what I did on my
> DEC3000 running NetBSD 1.5ZA:
>
> uncomment tftp and bootps in /etc/services
> uncomment tftp and bootps in /etc/inetd.conf
>
> ps aux | grep inetd | awk '{ print $2 }' | xargs kill -HUP
>
> mkdir -p /tftpboot/client/root
>
> Get the 1.5.2 netboot code from the NetBSD ftp server
>(ftp.netbsd.org/pub/NetBSD/NetBSD-1.5.2/alpha/installation/netboot/netboot)
and
> saved it as /tftpboot/boot.netbsd.alpha
>
> Added this entry to my /etc/bootptab:
>
> # /etc/bootptab
> #
> client.domain.com:\
>     :ht=ether:\
>     :ha=aabbccddeeff:\
>     :sm=255.255.255.0:\
>     :lg=www.xxx.yyy.zzz:\
>     :ip=www.xxx.yyy.zzz:\
>     :hn:\
>     :bf=boot.netbsd.alpha:\
>     :bs=auto:\
>     :rp=/tftpboot/client/root/:\
>     :vm=auto:
>
> Where aabbccddeeff is the MAC address of the network card and
> www.xxx.yyy.zzz is the IP address you want to assign to the 2100, and
> 255.255.255.0 is the correct netmask.
>
> Added this entry to my /etc/exports
> # /etc/exports
> #
> /tftpboot/client/root -maproot=root:wheel   -network www.xxx.yyy -mask
> 255.255.255.0
>
> same conventions for www.xxx.yyy and 255.255.255.0 as above.
>
> make sure rpcbind, mountd, nfsd are running. If they are already, kill
them
> and re-run them, this will make them reload the configs. If they aren't
> running, run them. they need to be running
>


Oh, and the kernel was /tftpboot/netbsd

Cheers

Collin