From owner-freebsd-current Sun Jan 17 13:14:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00931 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:14:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00924; Sun, 17 Jan 1999 13:14:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id NAA32926; Sun, 17 Jan 1999 13:14:48 -0800 (PST) To: jack cc: current@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-reply-to: Your message of "Sun, 17 Jan 1999 12:10:34 EST." Date: Sun, 17 Jan 1999 13:14:47 -0800 Message-ID: <32922.916607687@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nowhere near as annoying as "tagged openings now xx". I don't like this error much either (especially since it generates tech support questions on USENET and other places from users going "Aieee! What does this mean?!") but I was overruled on the issue by arguments that it was still providing useful information about drives that didn't really handle multiple tags as well as their spec sheets claimed. The problem with this argument is that it's sort of like the syslogd spew argument. It used to be that syslogd would just hammer your console (or log files) with repetetive messages, should some utility be generating them, without attempting to collapse them to a more meaningful (readable) summary. People screamed loudly about this and subsequent generations of syslogd just print the original message and then a little one-liner some time later which says "And I just got 47 more messages just like that." That's a great optimization and I would suggest that the tag reduction messages be similarly collapsed. Each and every time I boot my system and then launch X (through xdm), for example, I get a spew like this on my console: (da0:ahc0:0:0:0): tagged openings now 64 (da0:ahc0:0:0:0): tagged openings now 63 (da0:ahc0:0:0:0): tagged openings now 62 (da0:ahc0:0:0:0): tagged openings now 61 (da0:ahc0:0:0:0): tagged openings now 60 (da0:ahc0:0:0:0): tagged openings now 59 (da0:ahc0:0:0:0): tagged openings now 58 (da0:ahc0:0:0:0): tagged openings now 57 (da0:ahc0:0:0:0): tagged openings now 56 (da0:ahc0:0:0:0): tagged openings now 55 (da0:ahc0:0:0:0): tagged openings now 54 (da0:ahc0:0:0:0): tagged openings now 53 (da0:ahc0:0:0:0): tagged openings now 52 (da0:ahc0:0:0:0): tagged openings now 51 (da0:ahc0:0:0:0): tagged openings now 50 (da0:ahc0:0:0:0): tagged openings now 49 It all comes in one burst and isn't helping me any by giving me 16 messages where one would do just as nicely. > Also, I suspect having acd in the kernel and wcd in MAKEDEV may > lead to confusion for some people. I was under the impression that Soren was going to rename acd to wcd before the branch. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message