http://people.freebsd.org/~alfred/pxe/ But I get tired of dicking around with mfsroot vnode devices and such. The first thing I tried was taking the contents of the boot floppies and just sticking them in /usr/tftpboot. No dice, because then you end up with a read-only NFS root, which upsets sysinstall. How to get around that? The thing that bit me, I'm guessing, was removing the "load -T mfs_root /mfsroot" from loader.rc. I think load mfs_root creates an md filesystem. Now my thought is that if I can boot a minimal "diskless" install over the network, I can then fetch an appropriate install.cfg for the client and run sysinstall with it. So, I blew out /usr/tftpboot, and installed the bin distribution in there, copied the tfpboot back, set 'vfs.nfs.diskless_valid="1"' in boot/loader.conf, did a basic rc.conf and tried re-booting the client system. No such luck. It can't load init!!! NFS ROOT 172.16.0.1:/usr/tftpboot nfs_getpages: 13 exec /sbin/init: error 5 It then complains that init is not found in the path ... I can put sysinstall in /stand, but since the magic "setting up an mfsroot" never happened in /etc/rc.diskless1 there's no rw filesystem for sysinstall to work with. :( 4.1.1-RELEASE, btw. Any ideas? Thanks, -danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
