Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 May 2020 23:11:41 +1000
From:      andrew clarke <>
Subject:   Re: redesignde the unix-like system directory
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2020-05-06 20:16:43, kindu smith ( wrote:

> Borrowing android and freebsd just to keep it simple:
> /app, application directory, various system-level applications
> /boot,  boot directory, set up ABI, API, EFI, kernel, modules and other
> directories to store complete microkernel boot source code, interface,
> EFI partition information, modules.
> /cloud, various cloud applications
> /data,  database, such as key, web page data
> /help,  operating system manual
> /net,  network information and server information, etc.
> /system , store the file system hierarchy (FHS) directory
> /user,  user directory, set user account and information

The developers of Apple OS X and Haiku/BeOS (to use as examples) have already
done this to a certain extent. Both OSes began life with their own directory
structure, though, and they stuck with it. The structure wasn't changed years

An existing established OS like FreeBSD is unlikely to move all its files
around just to make things slightly more convenient for new sysadmins. Among
other things, reorganising the root directory structure would make existing
documentation almost impossible to follow.

If you really want to go down that path (pun intended) I suspect you'll need
to create your own fork of FreeBSD.

The other option is to create a whole bunch of symlinks on an existing system.

However I feel that both involve a lot more unnecessary work instead of simply
learning where everything is on that system.

Want to link to this message? Use this URL: <>