Date: Wed, 12 Jan 2011 21:20:58 +1100 From: Peter Jeremy <peterjeremy@acm.org> To: freebsd-stable@freebsd.org Subject: Re: classes and kernel_cookie was Re: Specifying root mount options on diskless boot. Message-ID: <20110112102058.GA46319@server.vk2pj.dyndns.org> In-Reply-To: <E1PcDUQ-00016i-NB@kabab.cs.huji.ac.il> References: <Pine.GSO.4.64.1101091015070.27086@nber6> <E1PcDUQ-00016i-NB@kabab.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
--opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Jan-09 10:32:48 -0500, Daniel Feenberg <feenberg@nber.org> wrote: >Daniel Braniss writes... >> I have it pxebooting nicely and running with an NFS root >> but it then reports locking problems: devd, syslogd, moused (and maybe Actually, that was me, not Daniel. >Are you mounting /var via nfs? Yes. I'm using "diskless" in the traditional Sun workstation style - the system itself is running with a normal filesystem which is all NFS mounted from another (FreeBSD) server. I'm aware of the MFS-based read-only approach but didn't want to use that approach. >I note that the response to your message from "danny" offers the ability= =20 >to pass arguments to the nfs mount command, Actually, my original mail indicates that that I'm aware you can pass options to the NFS mount command (passing nolockd will solve my problem). My issue is that there are several incompatible approaches and none of them work by default. > but also seems to offer a fix=20 >for the fact that "classes" are not supported under PXE: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/90368 I wasn't previously aware of that PR but it is consistent with my findings. On 2011-Jan-10 10:52:34 +0200, Daniel Braniss <danny@cs.huji.ac.il> wrote: >I'm willing to try and add the missing pieces, but I need some better expl= anantion as to what they are, for example, I have no clue what the >kernel_cookie is used for, nor what the ${class} is all about. I'm also happy to patch the code but feel that both PXE and BOOTP should be consistent and I'm not sure which is the correct approach. >BTW, it would be kind if the line in the pxeboot(8): > As PXE is still in its infancy ... >can be changed :-) Well, there are still some issues with PXE booting FreeBSD - eg as discussed here. But, I agree, that comment can probably go. --=20 Peter Jeremy --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAk0tgIoACgkQ/opHv/APuIfiMwCfag5EU5tt7CcOoBGOF24bzJ0b 2wQAn2EZUYNdi+vn72+YugTaZTu1hlli =bHLv -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110112102058.GA46319>