From owner-freebsd-current@FreeBSD.ORG Sun Nov 9 12:43:19 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D876616A4CF for ; Sun, 9 Nov 2003 12:43:19 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C46D43F75 for ; Sun, 9 Nov 2003 12:43:19 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) hA9KhHZV081570 for ; Sun, 9 Nov 2003 15:43:17 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)hA9KhHx0081567 for ; Sun, 9 Nov 2003 15:43:17 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 9 Nov 2003 15:43:17 -0500 (EST) From: Andre Guibert de Bruet To: current@freebsd.org Message-ID: <20031109152718.B10120@alpha.siliconlandmark.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean Subject: nextboot.conf on sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 09 Nov 2003 20:43:20 -0000 Hi, It appears that nexboot.conf isn't cleared on boot on sparc64. I tested this with on: FreeBSD ultra.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Nov 7 23:59:19 GMT 2003 root@:/usr/src/sys/sparc64/compile/GENERIC sparc64 The nextboot command was invoked with: nextboot -o "-s" -k kernel I have reason to believe that the problem is due to / being read-only on single-user boot (which is a good thing for fsck purposes) so the file cannot be unlinked. When the system boots multi-user though, all appropriate filesystems are mounted rw, and nexboot.conf still doesn't get cleared. Then again, I could be wrong... :) Any ideas? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >