From owner-freebsd-questions@FreeBSD.ORG Mon Jan 7 21:16:58 2008 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED20116A41B for ; Mon, 7 Jan 2008 21:16:58 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id BAB1D13C458 for ; Mon, 7 Jan 2008 21:16:58 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 6646 invoked from network); 7 Jan 2008 21:16:57 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 7 Jan 2008 21:16:57 -0000 Message-ID: <478295E5.8030509@chuckr.org> Date: Mon, 07 Jan 2008 16:13:09 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Tilman Linneweh References: <75a268720801040620o7367a1fdt85c33516c252d8b3@mail.gmail.com> <0F185B64-1122-4AF1-95D0-82D3419CFFDE@FreeBSD.org> In-Reply-To: <0F185B64-1122-4AF1-95D0-82D3419CFFDE@FreeBSD.org> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Omer Faruk Sen , FreeBSD List Mailing Subject: Re: disabling boot output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2008 21:16:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tilman Linneweh wrote: > > > * Omer Faruk Sen [ Jan 4, 2008 (15:20 )]: >> How can I disable boot messages so user can't see any boot message. >> I think there is 4 part for that and each of them requires a different >> configuration file to be edited. >> >> 1) boot >> 2) loader >> 3) kernel message >> 4) init scripts >> >> Can anyone send me an URL that depicts those changes? Or at least >> where to >> look for them. I think 2,3,4 can be done with configuration files but >> 1 step >> requires some code change right? > > You can send the output to a serial port by putting > > console=comconsole > > into /boot/loader.conf. f you don't have a serial console, there's another way to do it, one I stepped into accidentally, and it took me a long while to recover from. There's a different line you could have put into the /boot/loader.conf file, one that says "boot_mute=YES". That's going to silence all of the probing messages completely. The way it bit me (and you probably ought to be aware of it) is that it works exactly the same, if you had entered "boot_mute=NO" or even "boot_mute=Cincinnati", in all cases, the boot messages are a goner, it's only reading that the word "boot_mute" is being set, and what it's being set to really doesn't get into the act. Took me a really long time to learn that one. I won't soon forget it. > > See > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html > > for details. > > çok selamlar > arved > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgpXlz62J6PPcoOkRAmLGAJ0UhN3WqY5Zo/2bGX7SkHhPw/a2nQCfcOGG mMKSLlBqsdLU0mAMAler/EM= =bCwD -----END PGP SIGNATURE-----