Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED], Doug Ambrisko writes: | 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. The diskless setup we use here is based on a compiled-in MFS root rather than an NFS root, so we couldn't use the bootp code to enable NFS swap. Our solution was a modification to swapon() to enable direct swapping to NFS regular files. This results in the same swaponvp() call that the bootp code would use (at the time we implemented this, swapping over NFS via vnconfig was extremely unreliable; I think things are much better now). Thanks for the patch. I was able to make a swapfile with vnconfig on -stable, but on -current I just get a device not configured error. Your patch work just fine on -current. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED], Doug Ambrisko writes:
| 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.
The diskless setup we use here is based on a compiled-in MFS root
rather than an NFS root, so we couldn't use the bootp code to enable
NFS swap. Our solution was a modification to swapon() to enable
direct swapping to NFS regular files.
This results in the same swaponvp() call that the bootp code would
use (at the time we implemented this, swapping over NFS via vnconfig
was extremely unreliable; I think things are much better now).
The patch we use is below.
Ian
Index: vm_swap.c
===
RCS file: /FreeBSD/FreeBSD-CVS/src/sys/vm/vm_swap.c,v
retrieving revision 1.96
diff -u -r1.96 vm_swap.c
--- vm_swap.c 2000/01/25 17:49:12 1.96
+++ vm_swap.c 2000/11/05 11:04:34
@@ -202,10 +202,14 @@
NDFREE(nd, NDF_ONLY_PNBUF);
vp = nd.ni_vp;
- vn_isdisk(vp, error);
-
- if (!error)
+ if (vn_isdisk(vp, error))
error = swaponvp(p, vp, vp-v_rdev, 0);
+ else if (vp-v_type == VREG vp-v_tag == VT_NFS) {
+ struct vattr attr;
+ error = VOP_GETATTR(vp, attr, p-p_ucred, p);
+ if (!error)
+ error = swaponvp(p, vp, NODEV, attr.va_size/DEV_BSIZE);
+ }
if (error)
vrele(vp);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
the dhcp.xxx stuff is easy, the problem is that the DHCP options are not enough, so im trying to look into defining a FBSDclass ala PXEClient, and supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. You don't need those; you can get them out of /etc/fstab. In particular, the whole idea of passing the NFS swap details in at this stage is just *totally* bogus. How do you specify nfs swap in the fstab file? I have been trying the way diskless(8) says and a few permutations thereof, but so far without luck. I get the feeling that swapon don't know how to handle nfs swap. What I have tried was: 10.1.2.3:/export/myclient/swap none swap sw,nfsmntpt=/swap 10.1.2.3:/export/myclient/swap none swap sw 10.1.2.3:/export/myclient/swap none nfs sw But each time I get this message: swapon: 10.1.2.3:/export/myclient/swap: No such file or directory John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
John Hay writes: | the dhcp.xxx stuff is easy, the problem is that the DHCP options are not | enough, so im trying to look into defining a FBSDclass ala PXEClient, and | supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. | | You don't need those; you can get them out of /etc/fstab. In particular, | the whole idea of passing the NFS swap details in at this stage is just | *totally* bogus. | | How do you specify nfs swap in the fstab file? I have been trying the 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. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
John Hay writes: | the dhcp.xxx stuff is easy, the problem is that the DHCP options are not | enough, so im trying to look into defining a FBSDclass ala PXEClient, and | supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. | | You don't need those; you can get them out of /etc/fstab. In particular, | the whole idea of passing the NFS swap details in at this stage is just | *totally* bogus. | | How do you specify nfs swap in the fstab file? I have been trying the 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. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
On Nov 04, John Hay wrote: John Hay writes: | the dhcp.xxx stuff is easy, the problem is that the DHCP options are not | enough, so im trying to look into defining a FBSDclass ala PXEClient, and | supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. | | You don't need those; you can get them out of /etc/fstab. In particular, | the whole idea of passing the NFS swap details in at this stage is just | *totally* bogus. | | How do you specify nfs swap in the fstab file? I have been trying the 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. Try shortening the paths, ie root-path "/e/d". This might get you a little more room. --Mat John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- Mathew Kanner [EMAIL PROTECTED] SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED]you write: } [...] }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=FF }as the root filesystem. Removing the option-128 line at least get me to }boot albeit without swap. } the way I see it, there at least 2 'calls' to dhcpd. 1- by the PXE/UNDI stuff in the romboot. which needs the PXEClient stuff, and gets very confused with root/swap server. specialy if the dhcpd/tftpd/root/swap servers are not the same hosts. 2- by the freebsd-bootp, which IMHO does not need the PXEClient and could use something like FreeBSDc, to get the 'correct' values. i know this sounds confusing, (even to me :-), but I think I can come up with some working examples soon. btw, the secret is in libstand/bootp.c and src/sys/nfs/bootp_subr.c danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
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 Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
| 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. :-) John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
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. :-) This is correct; basically I don't think the bootstrap has any business setting up swap. swapon needs to learn how to configure NFS swap (or you should use a swapfile). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
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
Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED]you write: } In message [EMAIL PROTECTED]you write: } } }Mostly I guess I'd really like it to simply save *all* of the DHCP } }response in the environment. Just "dhcp.xxx" where xxx is the parameter } }value would probably do it, or we can argue about names for everything if } }there aren't established names already. } } } what's in a name ;-) } the dhcp.xxx stuff is easy, the problem is that the DHCP options are not } enough, so im trying to look into defining a FBSDclass ala PXEClient, and } supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. } ok, so now i can setenv(dhc.xxx, val). I would very much like to make them available as sysctl dhcp.xxx, the only problem, is that the sysctl interface is prety much static, so has anybody lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them into the mid ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
Danny Braniss ([EMAIL PROTECTED]) wrote: ok, so now i can setenv(dhc.xxx, val). I would very much like to make them available as sysctl dhcp.xxx, the only problem, is that the sysctl interface is prety much static, so has anybody lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them into the mid ... It is dynamic in -current. -- Paul Saab Technical Yahoo [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED]you write:
}Danny Braniss ([EMAIL PROTECTED]) wrote:
} ok, so now i can setenv(dhc.xxx, val).
}
} I would very much like to make them available as sysctl dhcp.xxx, the only
} problem, is that the sysctl interface is prety much static, so has anybody
} lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them
} into the mid ...
}
}It is dynamic in -current.
}
so now i have to get current to compile :-)
btw, i asked this before, and got answers that were not to the point.
i would very much like to be able and compile to /usr/obj, and install
not on /, but say ${dest}/ ...
danny
}--
}Paul Saab
}Technical Yahoo
}[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
}Do You .. uhh .. Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
Danny Braniss ([EMAIL PROTECTED]) wrote:
In message [EMAIL PROTECTED]you write:
}Danny Braniss ([EMAIL PROTECTED]) wrote:
} ok, so now i can setenv(dhc.xxx, val).
}
} I would very much like to make them available as sysctl dhcp.xxx, the only
} problem, is that the sysctl interface is prety much static, so has anybody
} lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them
} into the mid ...
}
}It is dynamic in -current.
}
btw, i asked this before, and got answers that were not to the point.
i would very much like to be able and compile to /usr/obj, and install
not on /, but say ${dest}/ ...
make DESTDIR=/path installworld
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
} what's in a name ;-) } the dhcp.xxx stuff is easy, the problem is that the DHCP options are not } enough, so im trying to look into defining a FBSDclass ala PXEClient, and } supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. } ok, so now i can setenv(dhc.xxx, val). I would very much like to make them available as sysctl dhcp.xxx, the only problem, is that the sysctl interface is prety much static, so has anybody lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them into the mid ... If you are setting stuff in the loader environment, you can get it back after the system has booted with 'kenv'. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED]you write: }Mostly I guess I'd really like it to simply save *all* of the DHCP }response in the environment. Just "dhcp.xxx" where xxx is the parameter }value would probably do it, or we can argue about names for everything if }there aren't established names already. } what's in a name ;-) the dhcp.xxx stuff is easy, the problem is that the DHCP options are not enough, so im trying to look into defining a FBSDclass ala PXEClient, and supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. }There should be no real problems with the lease, as most leases are more }than long enough to boot the system anyway, so I wouldn't bother with }that. } and this is not a MS system that needs allot of magic before it boots up ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED]you write: }Mostly I guess I'd really like it to simply save *all* of the DHCP }response in the environment. Just "dhcp.xxx" where xxx is the parameter }value would probably do it, or we can argue about names for everything if }there aren't established names already. } what's in a name ;-) the dhcp.xxx stuff is easy, the problem is that the DHCP options are not enough, so im trying to look into defining a FBSDclass ala PXEClient, and supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. You don't need those; you can get them out of /etc/fstab. In particular, the whole idea of passing the NFS swap details in at this stage is just *totally* bogus. }There should be no real problems with the lease, as most leases are more }than long enough to boot the system anyway, so I wouldn't bother with }that. } and this is not a MS system that needs allot of magic before it boots up ;-) Correct. Another thing that needs fixing is dhclient in the diskless case; if you run dhclient it kills the NFS mount for /, so that when it pages some more of itself in (or goes to run /bin/sh to run the dhclient-script) you're screwed... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message [EMAIL PROTECTED]you write: } In message [EMAIL PROTECTED]you write: } } }Mostly I guess I'd really like it to simply save *all* of the DHCP } }response in the environment. Just "dhcp.xxx" where xxx is the parameter } }value would probably do it, or we can argue about names for everything if } }there aren't established names already. } } } what's in a name ;-) } the dhcp.xxx stuff is easy, the problem is that the DHCP options are not } enough, so im trying to look into defining a FBSDclass ala PXEClient, and } supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. } }You don't need those; you can get them out of /etc/fstab. In particular, }the whole idea of passing the NFS swap details in at this stage is just }*totally* bogus. } the problem with /etc/fstab it doesn't scale nicely - i have a few hundred hosts that are currently running nfsroot linux, and it's not easy to manage. so having the basic stuff in one file dhcp.conf - even if it has a lousy syntax - seems to me better than having many little fstabs around, specialy if things change. hum, what about the info to mount root? v2/v3, blocksize, timeouts etc? } }Another thing that needs fixing is dhclient in the diskless case; if you }run dhclient it kills the NFS mount for /, so that when it pages some }more of itself in (or goes to run /bin/sh to run the dhclient-script) }you're screwed... well, dhclient is some hack, and probably will be useless, albait the leasing stuff, but i only looked/used it briefly - (i got it to work with my laptop running bsdi/os) im looking at the dhcp. options, and they are many, what do you think would be the best way to store them? sysctl come to mind, but it's not dynamic, ie, only available if it was set by dhcp. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
: In message [EMAIL PROTECTED]you write: : : }Mostly I guess I'd really like it to simply save *all* of the DHCP : }response in the environment. Just "dhcp.xxx" where xxx is the parameter : }value would probably do it, or we can argue about names for everything if : }there aren't established names already. : } : what's in a name ;-) : the dhcp.xxx stuff is easy, the problem is that the DHCP options are not : enough, so im trying to look into defining a FBSDclass ala PXEClient, and : supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. : :You don't need those; you can get them out of /etc/fstab. In particular, :the whole idea of passing the NFS swap details in at this stage is just :*totally* bogus. You can specify swap paritions with dhcpd just fine, just use the the numerical IP: option root-path "999.999.99.99:/"; option option-128 "999.999.99.99:/images/swap"; -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
:You can specify swap paritions with dhcpd just fine, just use :the the numerical IP: : :option root-path "999.999.99.99:/"; :option option-128 "999.999.99.99:/images/swap"; : : -Matt You know, my written english is getting *really* bad! I meant, just use the numerical dhcp (really the bootp protocol) option '128' to specify the swap. You can specify any option you want numerically, whether dhcp has named it or not. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
