Date: Wed, 09 Aug 2000 19:27:56 +0300 From: Nimrod Mesika <nimrodm@bezeqint.net> To: questions@FreeBSD.ORG Subject: Re: unix filesystem structure Message-ID: <20000809192756.A60561@localhost.bsd.net.il> In-Reply-To: <20000808202239.A21332@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Tue, Aug 08, 2000 at 08:22:39PM %2B0100 References: <20000808202239.A21332@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 08, 2000 at 08:22:39PM +0100, j mckitrick wrote: > is there any advantage to the unix filesystem structure, keeping all > binaries together, all docs together, all config files together, etc, rather > than the modern method of keeping all the parts of a given application > together? > One reason is to let you keep read-only files (i.e., binaries) and read-write files (configuration files, data, etc.) in separate filesystems. For example, Unix systems are usually designed so that you could mount /usr read-only or place /tmp /var on a fast r/w disk. -- Nimrod. http://www.geocities.com/rodd_27 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000809192756.A60561>