From owner-freebsd-questions@freebsd.org Thu May 10 14:57:00 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25503FCC3FC for ; Thu, 10 May 2018 14:57:00 +0000 (UTC) (envelope-from ailee.email@icloud.com) Received: from mr29p60im-ztfb07091501.me.com (mr29p60im-ztfb07091501.me.com [17.120.80.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD60D69513 for ; Thu, 10 May 2018 14:56:59 +0000 (UTC) (envelope-from ailee.email@icloud.com) Received: from process-dkim-sign-daemon.mr29p60im-ztfb07091501.me.com by mr29p60im-ztfb07091501.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P8I00J00P7OY800@mr29p60im-ztfb07091501.me.com> for freebsd-questions@freebsd.org; Thu, 10 May 2018 14:56:43 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1525964203; bh=qKix8nkX3bvJ+ECUnZygokPH/sWEicDF/b/1IAhJfCM=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=LhK5jiOekflQVwJt66jCFxaJU7NRWqL2dmSAWDyrxsIc68KWY4wyY49goWJLS2JAe bGASofe/eL90UL0LwsmObxvRY0py/AKm/pW5AY7BEoYcAVxaogsRzFFMHFEx8HfIUx +cd3QPFJTzvXLkdg+euB23UTfzhL/KrhlIOJSgPY7LlmOoUA4vb3Q4gT264D5cOKvM TXKRCKq0r2TSvZGZMhc49wa1FuyMhwEiFdef0OpENRS31W9HUDPnQZHVVB6o0iYLsc mMJFctiuOl51oEeBwA1b27ap5MhKcVf/F+RC/gH1I1nWaULi0tmZiCPEYnDxVvlVYq QO0oX+RoR6uhg== Received: from icloud.com ([127.0.0.1]) by mr29p60im-ztfb07091501.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P8I00O20PIEAB00@mr29p60im-ztfb07091501.me.com>; Thu, 10 May 2018 14:56:43 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-05-10_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1805100142 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (1.0) Subject: Re: How to hide boot console message. From: =?utf-8?B?5p2O5ZGo5Y2O?= X-Mailer: iPhone Mail (15E302) In-reply-to: <5AF43A6D.90607@gmail.com> Date: Thu, 10 May 2018 22:56:36 +0800 Cc: freebsd Content-transfer-encoding: quoted-printable Message-id: <4473FFD1-612B-4E82-92EA-C78BDB065164@icloud.com> References: <061BEC75-786F-4C26-8ABE-0BE2431DA313@icloud.com> <5AF43A6D.90607@gmail.com> To: Ernie Luzar X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 14:57:00 -0000 I find in console show a error when boot. ..... Changing splash image . expr:division by zero /etc/rc:ERROR:choice failed=20 ...... > On May 10, 2018, at 8:26 PM, Ernie Luzar wrote: >=20 > =E6=9D=8E=E5=91=A8=E5=8D=8E wrote: >> Is it possible that the boot message is not displayed when boot ? Only sh= ow when some error happen. >> Most of time there is no boot error occurred, we no need to care the boot= message. >> I try create a file /boot.config with content "-mq" >> add below lines >> verbose_loading=3D"NO" >> boot_mute=3D"YES" >> to file /boot/loader.conf >> but some network connection message still show , is there a way to hide t= hat ? thanks >=20 > With the above config if you are still getting boot time network connectio= n messages, then this is a bug. You should file a bug report about this show= ing the output your getting. >=20 >=20 > Can help you with "stopping the boot time messages from showing". But ther= e is no control over showing only errors. The only error at boot time is the= system freezing up. You will notice this when it happens. Any other error s= uch as missed spelled options in /etc/rc.conf is not an boot error. They are= just ignored and the boot process continues by design. >=20 > If you use a boot time splash screen those "boot time messages" will not s= how rolling across your master console. A few boot loader messages, includin= g the boot options menu and the timed wait > countdown prompt, are still displayed at boot time, even with the boot spl= ash screen enabled. >=20 > See handbook for info on how to configure. https://www.freebsd.org/doc/han= dbook/boot-splash.html >=20 >=20