From owner-freebsd-current Sat Dec 8 16:20: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 46B7F37B405 for ; Sat, 8 Dec 2001 16:19:56 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id BAA19682 for freebsd-current@freebsd.org; Sun, 9 Dec 2001 01:19:55 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id fB8NuII32772; Sun, 9 Dec 2001 00:56:18 +0100 (MET) (envelope-from j) Date: Sun, 9 Dec 2001 00:56:18 +0100 (MET) Message-Id: <200112082356.fB8NuII32772@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200111210831.fAL8Vjn01579@freefall.freebsd.org> <20011208022416.B818@cicely8.cicely.de> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: cvs commit: src/sys/kern subr_diskmbr.c X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernd Walter wrote: > 32 times for each disk on booting with most of 30 disks. > Possibly it's triggered by vinums drive scanning. Yep, same here (and it is triggered by vinum). > What can I do about these messages? Remove it. It should not have been there in the first place, at least not without an "if (bootverbose) ..." in front of it. It isn't telling any news anyway, because you certainly already knew that your disks are using DD mode, and the last word is telling "(ignored)" which is the intented and expected action to happen anyway. I do understand Peters gripe about broken BIOSes that try to interpret fdisk tables (where the fdisk table is actually in the domain of the boot block itself). The comments tell a bit more about it. But adding pointless messages that flush the boot log and possibly hide important boot messages can't be goo. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message