From owner-freebsd-hackers Sun Mar 19 00:41:15 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA00210 for hackers-outgoing; Sat, 18 Mar 1995 21:50:21 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA00200 for ; Sat, 18 Mar 1995 21:50:16 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id VAA22272; Sat, 18 Mar 1995 21:49:31 -0800 From: Poul-Henning Kamp Message-Id: <199503190549.VAA22272@ref.tfs.com> Subject: Re: kern/248: scbus attach/probe printf inconsistency To: bde@zeta.org.au (Bruce Evans) Date: Sat, 18 Mar 1995 21:49:30 -0800 (PST) Cc: bde@zeta.org.au, dufault@hda.com, freebsd-hackers@freefall.cdrom.com, pst@Shockwave.COM In-Reply-To: <199503190524.PAA07244@godzilla.zeta.org.au> from "Bruce Evans" at Mar 19, 95 03:24:28 pm Content-Type: text Content-Length: 884 Sender: hackers-owner@FreeBSD.org Precedence: bulk > >This happens because we print bogus information. > > This happens because fdisk/disklabel are confused. They have problems > finding the correct information and don't do any consistency checking. > An error transcribing non-bogus information would cause much the same > problem as bogus information. Bruce, if I can expect you to sit in the receiving end of all emails relating to this, then the printf can stay, otherwise I will use my release-engineer hat, and say: it must die. I'm willing to accept "die" to mean: only be printed when bootverbose is set. But in a normal boot I don't want to see it. The <1% of our users who care, can certainly be bothered to do a "boot -v" to see it. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'