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

[devick@lanier.com]

Some software vendors (such as Oracle) put config files in /etc.
We prefer to add a /data directory, which is managed under our change
control system.  This is where we put various config files, Oracle
parameter files (init.ora), etc.

Each application on our systems also has a dedicated data directory,
in addition to the database(s).

On Thu, Mar 24, 2005 at 12:26:26PM -0600, Mike wrote:
> I don't like how previous administrators have set the internal,
> home-grown scripts. Currently everything is just thrown into
> /commands. What I want is to change the structure so that it
> looks more like:
> 
> /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?
> 
> What makes sense?
> 
> Mike
> _______________________________________________
> Infrastructures mailing list
> Infrastructures@mailman.terraluna.org
> http://mailman.terraluna.org/mailman/listinfo/infrastructures