Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Mon, 28 Feb 2000 20:16:58 -0500 Message-Id: <200002290116.UAA22995@envy.delorie.com> From: DJ Delorie To: khan AT NanoTech DOT Wisc DOT EDU CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: (message from Mumit Khan on Mon, 28 Feb 2000 18:54:51 -0600 (CST)) Subject: Re: FS layout issues for v1.1 (eg., /bin and /usr/bin) References: In the Linux FSS, they talk about /,/usr,/usr/local like this: * / is for programs that are required to boot the system to its normal multi-user mode. Nominally, these would be statically-linked programs to remove a dependence on the shared library system being operational. * /usr is for other standard user-level programs installed with the OS (or official packages) and is normally built with shared libraries. * /usr/local is for programs that are installed only on that machine (i.e. not part of the "standard" package). I recall that there is a minimum set of "expected" commands in /bin (like ls, cp, sh, etc) but since cygwin isn't involved in booting most of its software belongs in /usr. /usr/local should never be touched (except maybe to set up an empty directory structure) by the standard installer.