[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: File structure
Hmm.. Generally fine by me, a few comments.
>The MiNT distribution kit sets up the following directory structure:
>
> /etc machine-biased files/programs
> /bin 'important' binaries
How's about /bin -> /usr/bin
> /dev devices (set up by MiNT)
> /pipe named pipes (set up by MiNT)
> /proc processes (set up by MiNT)
> /shm shared-memory sections (set up by MiNT)
> /tmp temporary files - cleared at boot-time
> /var maintenance directories
> /adm admin files
> /log log files
> /spool spool files (eg: cron/mail)
Add /tmp
(see below)
> /usr user-level directories
> /bin user-orientated binaries
> /etc daemons and their control programs
> /doc docs that aren't man pages. 1 file/dir each
> /include general include directory
> /g++ inc. files for G++
> /gem++ inc. files for Gem++
> /mgr inc. files for mgr
> /sys system-type include files
> /info TeXinfo style documentation
This like to be under /usr/local in the standard FSF distributions.
> /lib system libraries. Subdirs for programs
> /local local-to-system directories
> /man }
> /bin } currently contains groff and tclsh
> /lib }
> /man manual directories and the whatis database
> /man? ?=1->8 manual sections
> /cat? ?=1->8 pre-formatted sections
> /mnt mounting filesystems onto (note: can't use /mnt)
/sbin For system binaries, ie getty and init etc.
> /spool link to /var/spool
> /src contains directories of system'y source code
> /fs minixFS source code
> /kernel MiNT 1.09 source code
> /lib patchLevel 42 MiNTlib source code
Is this part REALLY necessary?
> /tmp temporary files *not* cleaned at boot-time
Should be a link to /var/tmp.
> /ucb ucb-type bins (currently just vi)
Should be vi, more, finger, cc, compress, vi+siblings, lpr, lpq, etc (once I
get them ported), yes, tset etc etc etc. ie. those binaries derived from BSD
which didn't appear in the mainstream until very late.
> /users root directory for users home dirs
Or /home if you like.
> /var link to /var
Pardon? isn't this a little bit recursive? :-)
>This isn't perhaps the most coherent way of setting it out (maybe a tree
>diagram would be better), but it shows how I set up the fs structure, and
>what I put into which directories.
>
>[note: The only reason vi is in /usr/ucb is that some programs hardcode
>/usr/ucb into themselves- otherwise it'd be in /usr/bin and like it!]
That's a bit facist isn't it? :-)
>[note2: This is set up as it is on my HD at home under MDK 3.0 - Some things
>are missing (notably the src directory) in MDK 2.0, and some programs are
>not in their 'correct' places.]
>
>[note3: I've only ever got one version of a program. This version has to be
>all things to all men. For example, more is in /usr/bin, not /bin.]
See above... /usr/bin can be /bin too.
>Any objections to me putting this forward as a first attempt to ratify
>the filesystem should be posted :-)
>
>BTW: I vote for MiNX as the name for the more-unix-alike system (if we
>need one. I've found that undeffing anything to do with the ST is the easiest
>way to get things to compile <grin>)
Hmm... sounds like a derisive name to me.. as in "What an awkward little
MiNX!" grin.
>Simon.
>_______________________________________________________________________
>\ Simon Gornall - Kings College London. Email: sjg@phlem.ph.kcl.ac.uk /
>/ - finger sjg@137.73.4.24 for info on the MiNT distrib kit - \
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve
--
---------------------------------------------------------------------------
Computer Systems Administrator, Dept. of Earth Sciences, Oxford University.
E-Mail: steve@uk.ac.ox.earth (JANET) steve@earth.ox.ac.uk (Internet).
Tel:- Oxford (0865) 282110 (UK) or +44 865 282110 (International).