From owner-freebsd-questions@FreeBSD.ORG Fri Nov 21 09:36:29 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D0ED16A532 for ; Fri, 21 Nov 2003 09:36:29 -0800 (PST) Received: from clunix.cl.msu.edu (clunix.cl.msu.edu [35.9.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C113D43FF3 for ; Fri, 21 Nov 2003 09:36:27 -0800 (PST) (envelope-from jerrymc@clunix.cl.msu.edu) Received: (from jerrymc@localhost) by clunix.cl.msu.edu (8.11.7p1+Sun/8.11.7) id hALHaLn20188; Fri, 21 Nov 2003 12:36:21 -0500 (EST) From: Jerry McAllister Message-Id: <200311211736.hALHaLn20188@clunix.cl.msu.edu> To: murphyf+fhs@f-m.fm (Frank Murphy) Date: Fri, 21 Nov 2003 12:36:21 -0500 (EST) In-Reply-To: <20031121155931.047C9750A6@server2.messagingengine.com> from "Frank Murphy" at Nov 21, 2003 04:59:30 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Jerry McAllister cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD, FHS, and /mnt/cdrom X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 17:36:29 -0000 > > > > > > It sounds like you think that a new root-level directory should be > > > created for this, and that /media would be OK, but there might be a (yet > > > undiscovered) better name. Is this accurate? > > > > That seems like a pretty good summary. > > > > ////jerry > > Cool. > Could you also explain to me why you think that /var would be such > a bad place for this? Well, I probably can't give a hard and fast absolute reason, but... We use /var as a place for directoreis/files that can grow somewhat unexpectedly and weakly controlled, such as spool and logs, etc. Because of that, our /var is most often put in some other large general filesystem with links and doesn't really live in either root (/) or isn't a root located filesystem, but just a directory in another filesystem such as /work (or in some recent ones /lump - I couldn't think of a better name). So, making it the home of mount points would be rather awkward. I suspect that some others do similar things with /var. I have heard it mentioned. I think something similar can be true of other root located file systems such as /usr, although for those it is more likely that it just be a directory living within /usr that gets moved and linked. Generally, I think mount point directories should be as close to root located as possible with as little intervening stuff that could possible get shuffled around. At first blush, it would sound like /mnt would be a likely place, but it has been out there too long and been used in too many locally unique ways that mounts on or in there could create much unnecessary confusion. As far as "any ol' where" goes, that doesn't bother me much, but it sounds like what is being asked for is a kind of common place that won't cause problems so vendors and third party writers can go ahead and make something that will work easily across platforms with the least pain - and ain't that what everyone whines so much about - the pain of adding devices, etc. This would be a harmless way to ease some of that pain. And, anyway, if a standard location is adopted and if some users want to do it differently on their machines nothing would stop them from doing whatever they want with their systems. It would be no worse than if there was no standard and probably easier. Just lets not break a bunch of stuff to do it. Gee, it's nice to be asked about something like this for a change. ////jerry > > Frank >