Date: Tue, 25 Nov 2003 13:00:18 +0100 From: Siegbert Baude <Siegbert.Baude@gmx.de> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD, FHS, and /mnt/cdrom Message-ID: <3FC34452.2050004@gmx.de> In-Reply-To: <200311211923.11750.murphyf%2Bfhs@f-m.fm> References: <200311211736.hALHaLn20188@clunix.cl.msu.edu> <200311211923.11750.murphyf%2Bfhs@f-m.fm>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> 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. > Just because /var is a symlink to /lump/var shouldn't affect that. But if it's no symlink but a mount you run into trouble, if you want to remount /var (e.g. because out of disk space). So generally I would say this new directory you're looking for, should not be a subdirectory at all, especially if the parent directory is a frequently mounted one by itself. This would rule out /usr, /tmp, /var, /home at least. So better go for the /new_directory variant, IMHO. Ciao Siegbert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FC34452.2050004>