From owner-cvs-all Mon Jan 29 1:55: 2 2001 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D750737B404; Mon, 29 Jan 2001 01:54:37 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0T9sXK19893; Mon, 29 Jan 2001 10:54:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Matt Dillon , John Baldwin , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Mikhail Teterin Subject: Re: workaround for broken mfs using vn. (was Re: cvs commit: src/sys/i386/conf GENERIC ) In-Reply-To: Your message of "Mon, 29 Jan 2001 01:51:04 PST." Date: Mon, 29 Jan 2001 10:54:33 +0100 Message-ID: <19891.980762073@critter> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> You previous email didn't show "mdconfig panics" it showed the kernel >> panic'ing. >> >> Sometimes precision is a good thing :-) > >Hmm!! Well, you've stunned me with clever rhetoric. It's not rethoric damnit! If you got the panic when you run mdconfig then yes, you can say "mdconfig panics" despite the fact that only the kernel (and users) panics in FreeBSD. But saying "mdconfig panics" when the panic happens when you run a different program isn't exactly makeing it any easier to figure out what you're talking about... -- 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 cvs-all" in the body of the message