From owner-freebsd-hackers Tue Aug 7 10:32: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from safety.net (ns3.safety.net [216.200.162.38]) by hub.freebsd.org (Postfix) with ESMTP id A4EE637B43E for ; Tue, 7 Aug 2001 10:31:53 -0700 (PDT) (envelope-from les@safety.net) Received: (from les@localhost) by safety.net (8.9.3/8.9.3) id KAA91767; Tue, 7 Aug 2001 10:31:40 -0700 (MST) (envelope-from les) From: Les Biffle Message-Id: <200108071731.KAA91767@safety.net> Subject: Re: dmesg behaviour In-Reply-To: from Julian Elischer at "Aug 7, 2001 12:33:31 pm" To: julian@elischer.org (Julian Elischer) Date: Tue, 7 Aug 2001 10:31:40 -0700 (MST) Cc: K.J.Koster@kpn.com (Koster K.J.), les@safety.net ('les@safety.net'), freebsd-hackers@FreeBSD.ORG Reply-To: les@safety.net X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > 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. Thanks, -Les -- Les Biffle Community Service... Just Say NO! (480) 585-4099 les@safety.net http://www.les.safety.net/ Network Safety Corp., 5831 E. Dynamite Blvd., Cave Creek, AZ 85331 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message