From owner-freebsd-current Sat Dec 19 04:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05604 for freebsd-current-outgoing; Sat, 19 Dec 1998 04:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05580 for ; Sat, 19 Dec 1998 04:20:02 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id NAA36646; Sat, 19 Dec 1998 13:18:16 +0100 (CET) To: Bruce Evans cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 23:10:08 +1100." <199812191210.XAA06347@godzilla.zeta.org.au> Date: Sat, 19 Dec 1998 13:18:16 +0100 Message-ID: <36644.914069896@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812191210.XAA06347@godzilla.zeta.org.au>, Bruce Evans writes: >>> mount_foo should almost never be used directly. It should be in /libexec >> >>Then why have mount_foo at all? > >So that mount(8) is easy to extend. So that you don't get a spagetti program (like for instance ifconfig) which needs to know about all sorts of weird filesystems ideosyncracies. In difference from Bruce I think that mount_XXX is the primary interface, (and as such agree with jordan that mount_ufs should be there). Mount is just a backwards compatibility gadget now. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message