John Hay writes:
| > | > You don't, it is done via the bootp or dhcp record option 128 for example
| > | > option option-128 "192.168.2.254:/usr/work/netboot";
| > | > You then have to make the swap file in that directory of format
| > | > swap.<IP of client>
| > | > Use dd to create the file by copying /dev/zero for the size you want.
| > | >
| > | > Note during boot up the kernel will tell you what it is using for
| > | > swap via this request.
| > |
| > | The option-128 confuse the pxeboot program. If I put
| > |
| > | option root-path "/export/diskless";
| > | option option-128 "10.1.2.3:/export/shark";
| > |
| > | in the dhcpd.conf file, pxeboot tries to mount /export/sharkM-^[^B-i?
| > | as the root filesystem. Removing the option-128 line at least get me to
| > | boot albeit without swap.
| >
| > Root path should have the IP address of the server such as:
| > option root-path "192.168.2.254:/usr/home/ambrisko/netboot";
| >
| > Then in boot messages you should see:
| > rootfs is 192.168.2.254:/usr/home/ambrisko/netboot
| > swapfs is 192.168.2.254:/usr/work/netboot
| >
|
| Yes, you are right. Putting the ip number in the root-path cures the
| pxeboot failure. But is still only configure the NFS ROOT according
| to the kernel's output. I had a look at the pxe code in
| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
| /sys/i386/i386/autoconf.c which is the kernel side and it looks like
| they don't do anything about swap. There is a /* XXX set up swap? */
| placeholder though. :-)
Yep looks like you're right, I just tried it on 4.2-BETA it worked in
4.1.1. Swap is now broken ... sigh this is going to be a problem. I
guess the only thing you might be able to do in the interim is to do a
vnconfig of a file and then mount that as swap. I think the vnconfig
man pages describes this. Hopefully it works over NFS.
Doug A.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
