From owner-freebsd-current@FreeBSD.ORG Sun Oct 4 13:58:19 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F8C11065670 for ; Sun, 4 Oct 2009 13:58:19 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id B7E488FC08 for ; Sun, 4 Oct 2009 13:58:18 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1MuRbN-000ERC-EZ for freebsd-current@freebsd.org; Sun, 04 Oct 2009 15:58:17 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Oct 2009 15:58:17 +0200 From: Daniel Braniss Message-ID: Subject: 8.0RC1 and BOOTP_NFSV3 regression? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Oct 2009 13:58:19 -0000 I'm not sure when this happened, but a kernel compiled with BOOTP_NFSV3 fails when the server is not FreeBSD (ie NetAPP). before, with the option set, only when kernel_options="nfsv3" was set it would fail/panic, this way, I could control which diskless, shearing the same kernel, would boot with nfsv3 and which not, dependig on the server. there is hope! before it would panic when receiving a v3 file handle, now it fails, but panics later when no init is found :-) is anyone with enough nfs v2/v3 knowledge willing to fix this? cheers, danny