From owner-freebsd-current Wed Nov 11 03:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05481 for freebsd-current-outgoing; Wed, 11 Nov 1998 03:43:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA05473 for ; Wed, 11 Nov 1998 03:43:06 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 7865 invoked by uid 1001); 11 Nov 1998 11:42:42 -0000 Date: 11 Nov 1998 11:42:42 -0000 Message-ID: <19981111114242.7862.qmail@ns.oeno.com> From: Ville-Pertti Keinonen To: sthaug@nethelp.no CC: jkh@zippy.cdrom.com, current@FreeBSD.ORG In-reply-to: <10401.910775245@verdi.nethelp.no> (sthaug@nethelp.no) Subject: Re: Is it soup yet? :-) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 3. /usr/mdec is a silly-assed name. Who thought of it? What does it even > > The mdec name certainly isn't FreeBSD-specific, changing it would add > > to the difficulty of finding things based on a "general knowledge" of > > Unix-like systems. > Has it: FreeBSD, NetBSD, possibly OpenBSD. > Doesn't have it: Solaris 2, HP-UX, Digital Unix, BSD/OS, RedHat 5.2 Digital UNIX has /mdec. I doubt I'm the only person who associates the name mdec with a directory that contains binary boot code images for various disk/filesystem types and methods of boot. I don't object to changing it, but simply wanted to point out that changing it can add confusion. I don't like the idea of putting boot block images in /boot, though. (Unless they are magically mapped to where they are actually read from on boot) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message