Date: Fri, 10 Mar 2006 01:35:22 -0500 From: Kris Kennaway <kris@obsecurity.org> To: freebsd-stable@freebsd.org Subject: Re: 6.1-PRERELEASE nfs root troubles Message-ID: <20060310063521.GA5197@xor.obsecurity.org> In-Reply-To: <20060310063058.GE69429@ugai.uvd-omsk.su> References: <20060306084222.GE57165@ugai.uvd-omsk.su> <20060306092743.GA18697@xor.obsecurity.org> <20060306105507.GF57165@ugai.uvd-omsk.su> <20060306210034.GA50522@xor.obsecurity.org> <20060310063058.GE69429@ugai.uvd-omsk.su>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Mar 10, 2006 at 12:30:58PM +0600, sergey akifiev wrote: > On Mon, Mar 06, 2006 at 04:00:34PM -0500, Kris Kennaway wrote: > > Thanks :) I netboot many machines on 6.1 and don't see this, so perhaps it it due to your use of the BOOTP* options: > > > > options BOOTP # Use BOOTP to obtain IP address/hostname > > # Requires NFSCLIENT and NFS_ROOT > > options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info > > options BOOTP_NFSV3 # Use NFS v3 to NFS mount root > > options BOOTP_COMPAT # Workaround for broken bootp daemons. > > seems, that this issue isn't connected with BOOT* options at all. > my test host, holding diskless root is an i686 machine and diskless client is > an old i586 box. it seems, that some i686-optimized binary sneaked into > diskless client's root. > i've found this by booting that kernel on dual-xeon server lieng around here > ;-) > but is still cannot understand, how this can be connected with this trap... Is the kernel also compiled for i686? Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEER4pWry0BWjoQKURAkTcAJ42UQ5K5MnTht2O5dxS9ecYg484AgCdFXUz hoNl8QtWiQc+bCvGfKXiaKc= =XulJ -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060310063521.GA5197>