From owner-freebsd-hackers Tue Aug 7 10:36:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4B5AA37B411 for ; Tue, 7 Aug 2001 10:36:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f77HaBQ34372; Tue, 7 Aug 2001 19:36:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: les@safety.net Cc: julian@elischer.org (Julian Elischer), K.J.Koster@kpn.com (Koster K.J.), freebsd-hackers@FreeBSD.ORG Subject: Re: dmesg behaviour In-Reply-To: Your message of "Tue, 07 Aug 2001 10:31:40 PDT." <200108071731.KAA91767@safety.net> Date: Tue, 07 Aug 2001 19:36:11 +0200 Message-ID: <34370.997205771@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200108071731.KAA91767@safety.net>, Les Biffle writes: >> this is a wonderful feature that has saved my butt many times >> (working in the kernel it's REALLY nice to have >> the last panic message in the dmesg buffer.) >> learn to love it.. :-) > >I can see the benefits. I will re-write the programs and scripts that >eat the dmesg output to look for the last boot, but I'm concerned that >the behavior is different on different platforms. I really hate mysterious >platform differences. The console-log code is machine-independent apart from the initial allocation of the space, so don't expect differences in this area. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message