From owner-freebsd-current Thu Aug 12 14: 4:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 046F215040; Thu, 12 Aug 1999 14:04:30 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA86638; Thu, 12 Aug 1999 17:04:04 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199908122104.RAA86638@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ben Rosengart Cc: multimedia@FreeBSD.ORG, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: it's time... References: In-reply-to: Your message of "Thu, 12 Aug 1999 14:44:54 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Aug 1999 17:04:04 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 11 Aug 1999, Brian F. Feldman wrote: > > > What in the world would be the point of doing this? What would be so great > > about not seeing the system boot up? > > One might want minimal or no boot messages, just to look nice, while > still wanting the dmesg stuff around in case something goes wrong or > they need to configure a kernel. It's certainly chrome, but I'd like > it. Spash screen. That being said, the capability to have what comes out during a verbose boot go somewhere else for later review, while only the "normal" messages are seen on the console would be sorta cool. I think you could do this by converting the printf()'s in the kernel to something like syslog() with explicity verbosity/priority specifications. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message