🚀 go-pugleaf

Is there a plan for the GNU system's file system structure ?  Unix
nowadays is very confusing as all vendors nowadays have reached
different solutions for the problems of workstations having perhaps
different CPUs sharing the same disks.  There are also goals to keep
changing files in one part of the tree (like /var).

Administration of such systems in general - things like creation of
new users, booting of the system, configuring the system to function
differently than others who mount the same file system based on the
hardware connected, backups, perhaps handling account expiration /
removal gracefully, setting up anon. ftp subsystem, configuring the
kernel, setting up mailing lists etc. etc. - is also nowadays done
differently on every vendor's Unix systems.

Has anyone done any work on things like this ?  A general policy about
the file system would be needed, as well as some simple tools to do
the various administrative tasks in a simple uniform way.  If we can
plan a good way to get GNU to be easily administrated in a multi-cpu
network right from the beginning, we won't need the lousy ad-hoc
different-for-every-site administrative scripts & procedures we're
using now for Unix.

//Jyrki