Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Oct 2002 11:22:18 -0700
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        Bruce Evans <bde@zeta.org.au>
Cc:        freebsd-bugs@FreeBSD.ORG
Subject:   Re: bin/43434: New option to 'dmesg' which allow to display or not old boot messages
Message-ID:  <20021001112217.A19820@Odin.AC.HMC.Edu>
In-Reply-To: <200210011710.g91HA6AC022255@freefall.freebsd.org>; from bde@zeta.org.au on Tue, Oct 01, 2002 at 10:10:06AM -0700
References:  <200210011710.g91HA6AC022255@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--yrj/dFKFPuw6o+aM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 01, 2002 at 10:10:06AM -0700, Bruce Evans wrote:
>=20
>  What's wrong with ``grep [-C] <magic> /var/log/messages'' then? :-)
>  (except it doesn't handled rotated log files or races with newsyslog ...=
).
>  It handles rotation a bit better than dmesg -- my message buffer gets
>  rotated by debugging cruft and doesn't keep boot messages for long.
>  Some magic would be required to find the last message without tags.
>  Printing only the very last message doesn't seem very useful anyway.
>  Lastness depends on an arbitrary descision about where the boot ends.

99+% of the time when a user types dmesg what they really want to see is:

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights
reserved.
FreeBSD 5.0-CURRENT #2: Thu Sep 26 14:33:02 PDT 2002
    root@minya.sea.one-eyed-alien.net:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel "/boot/kernel/kernel" at 0xc06ca000.
Preloaded elf module "/boot/kernel/snd_maestro3.ko" at 0xc06ca0a8.
=2E..

For the _current_ boot.  They couldn't care less about previous boots
unless they are looking for a message to diagnose a crash.  Currently if
you don't have extra debugging stuff on and you don't generate a lot of
errors, you typicaly find boot messages repeated several times, especialy
in -stable.  Thus you have to carefully scroll though the whole list to
find the current boot.  This change makes dmesg do what the user wants,
but allows access to the previous messages in the unlikely event they
are needed.

-- Brooks

--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

--yrj/dFKFPuw6o+aM
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9mefZXY6L6fI4GtQRAj29AJ9ysTsMBmd33E3cCikuGRG5mKKETACfSYzy
Sd+II7gKfXiqTYGyVqcjVu4=
=OmZx
-----END PGP SIGNATURE-----

--yrj/dFKFPuw6o+aM--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021001112217.A19820>