From owner-cvs-all Fri Feb 25 12:23:45 2000 Delivered-To: cvs-all@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 51A9D37BB62; Fri, 25 Feb 2000 12:23:38 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00475; Fri, 25 Feb 2000 12:22:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002252022.MAA00475@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jordan K. Hubbard" Cc: Robert Watson , "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern init_main.c In-reply-to: Your message of "Fri, 25 Feb 2000 11:22:20 PST." <95896.951506540@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Feb 2000 12:22:24 -0800 From: Mike Smith Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > When using excessively verbose boots, the scroll-back buffer often doesn't > > reach back far enough. Is there any way, as with dmesg.boot in a normal > > install, we could provide sysinstall-based access to the boot messages > > without using the scroll-back? I.e., a new menu option, ``Review Hardware > > Probe Messages'' which provided a scrollable window pointing at the > > contents of dmesg? > > I can do this, but it will only really help you post-boot time. > The /var/run/dmesg.boot file doesn't exist on the MFS filesystem. Increase the kernel message buffer, and use the machdep.msgbuf sysctl to retrieve it inside sysinstall. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message