From owner-freebsd-questions@freebsd.org Wed Jan 25 05:17:05 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0263BCBA0DD for ; Wed, 25 Jan 2017 05:17:05 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.he.net", Issuer "GeoTrust SSL CA - G4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E80C812C0 for ; Wed, 25 Jan 2017 05:17:04 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from ::ffff:99.100.19.101 ([99.100.19.101]) by holgerdanske.com with ESMTPSA (AES128-SHA:SSLv3:Kx=RSA:Au=RSA:Enc=AES(128):Mac=SHA1) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Tue, 24 Jan 2017 21:17:03 -0800 Subject: Re: How to capture console messages during boot? To: freebsd-questions@freebsd.org References: <20170124234536.7b43ba1a@riseup.net> From: David Christensen Message-ID: <7c22e1d8-7f3f-49a4-d034-e9c4f2cfc26a@holgerdanske.com> Date: Tue, 24 Jan 2017 21:17:02 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170124234536.7b43ba1a@riseup.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 05:17:05 -0000 > On Tue, 24 Jan 2017 19:59:01 -0800 > David Christensen wrote: >> I am attempting to build a graphical workstation using: >> [snip] >> As I add software and adjust configuration settings, invariably I create >> or encounter issues. Some of these generate warnings/ errors on the >> console when the system boots. I'd like to capture console messages >> during boot, so that I can review them and fix things. On 01/24/17 20:45, Sergei Akhmatdinov wrote: > 2. Use `dmesg -a`, maybe piped into `less` if you prefer. > The -a switch should show you the boot process messages, which are normally > suppressed. Yes, that's what I was looking for. On 01/24/17 21:07, Michael Sierchio wrote: > cat /var/run/dmesg.boot That is incomplete -- I don't see all of the messages (just kernel, not init?). Thanks, everyone, for the help. :-) David