From ppl@bloodaxis.dyndns.org  Tue Dec  3 18:10:56 2002
Return-Path: <ppl@bloodaxis.dyndns.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3201F37B401
	for <FreeBSD-gnats-submit@freebsd.org>; Tue,  3 Dec 2002 18:10:56 -0800 (PST)
Received: from bloodaxis.dyndns.org (ip142166204111.nbtel.net [142.166.204.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9FC1743EAF
	for <FreeBSD-gnats-submit@freebsd.org>; Tue,  3 Dec 2002 18:10:55 -0800 (PST)
	(envelope-from ppl@bloodaxis.dyndns.org)
Received: by bloodaxis.dyndns.org (Postfix, from userid 1001)
	id 93EF5EA5; Tue,  3 Dec 2002 22:10:57 -0400 (AST)
Message-Id: <20021204021057.93EF5EA5@bloodaxis.dyndns.org>
Date: Tue,  3 Dec 2002 22:10:57 -0400 (AST)
From: Pierre-Paul Lavoie <ppl@nbnet.nb.ca>
Reply-To: Pierre-Paul Lavoie <ppl@nbnet.nb.ca>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Printer setup documentation: Running dmesg weeks after boot up
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         45981
>Category:       docs
>Synopsis:       Printer setup documentation: Running dmesg weeks after boot up
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    ceri
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 03 18:20:01 PST 2002
>Closed-Date:    Mon Jan 20 05:20:29 PST 2003
>Last-Modified:  Mon Jan 20 05:20:29 PST 2003
>Originator:     Pierre-Paul Lavoie
>Release:        FreeBSD 4.7-RELEASE-p1 i386
>Organization:
>Environment:
System: FreeBSD bloodaxis 4.7-RELEASE-p1 FreeBSD 4.7-RELEASE-p1 #0: Fri Nov 8 20:48:41 AST 2002 root@bloodaxis:/usr/obj/usr/src/sys/BLOODAXIS i386


>Description:

Taken from FreeBSD handbook printing section 11.3.1.2.1
(Kernel Configuration):

<snip>
To find out if the kernel you are currently using supports a serial
interface, type:

    # dmesg | grep sioN
</snip>

If it have been a while that the operating system is boot up,
original messages might have been silently discarded. As a result,
the user will not get any output from the above command.

Maybe `cat /var/run/dmesg.boot' should be use instead of dmesg(1)?
It is uglier, but have the advantage of beeing guaranteed to work
(I think). Or perhaps add a new -b(oot) option to dmesg(1) that
simply echo back `dmesg.boot'.

I believe that it would be a good thing to warn about this potential
pitfall.

>How-To-Repeat:

Go to
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-intro-setup.html#PRINTING-SIMPLE
section 11.3.1.2.1 Kernel Configuration

>Fix:

Mention `cat /var/run/dmesg.boot` instead of dmesg if it
have been a while that you have boot up.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: ceri 
State-Changed-When: Wed Dec 4 10:21:46 PST 2002 
State-Changed-Why:  
Good idea. 


Responsible-Changed-From-To: freebsd-doc->ceri 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Wed Dec 4 10:21:46 PST 2002 
Responsible-Changed-Why:  
I'll take care of this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=45981 
State-Changed-From-To: analyzed->closed 
State-Changed-By: ceri 
State-Changed-When: Mon Jan 20 05:19:44 PST 2003 
State-Changed-Why:  
I committed the change in this specific section, and also in various 
other places around the handbook - thanks for your submission. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=45981 
>Unformatted:
