[: Re: [Infrastructures] how to build an internal (local) file structure?]

[dsr-infra@tao.merseine.nu]

On Thu, Mar 24, 2005 at 12:26:26PM -0600, Mike wrote:
> 
> /COMPANY
>   /bin
>   /lib
>   /etc
> 
> Like a typical unix box. My question is for things like data,
> mapping, resource, or configuration files... where should they
> go? If there is a file 'mapping.pl' that needs the file
> 'mapping.cfg', certainly the 'mapping.pl' goes in
> /COMPANY/bin. Does the 'mapping.cfg' go into /COMPANY/lib,
> /COMPANY/etc, or somewhere else?

If that's the way you want it --

bin is for executable code
etc is for config files
lib is for code libraries
var is for data
tmp is for temporary files 

Typically, though you have a multiple-machine scenario, in which
there are classes of machines which are effectively identical,
but different classes must be treated differently.

So, you might want:

/COMPANY/MACHINECLASS/bin|etc|lib|var

And you might, potentially, want a particular MACHINECLASS to be
"standard" or "common", put it on every machine, and keep things
there that every machine will need.


-dsr-

-- 
Nothing to sig here, move along.