Re: Configurable files and functions
On Fri, Mar 02, 2007 at 12:33:11PM -0600, Dave Walker wrote:
> I am looking for an explanatory list of configuration files used in
> sarge 3.1. The information I am looking for would give the location
> (path), function (what the system uses it for), and whether the file
> can be successfully changed by editing.
A configuration file, by its very nature, means that it can be edited,
although you would need to be root to edit "system wide" configuration
files.
> Does such a list exist?
I don't know. I'm guessing no because, unfortunately, documentation is
usually one of the last things to be done in a volunteer project and
normally done to "scratch an itch" or to conform with policy.
*Almost* every app has a .rc (runtime configuration) file which may have
numerous options and so providing a list like you suggest seems like a
waste of time considering it would need to be updated etc. Think "Would
*I* keep the list updated once I knew what they were?"
> I have in mind such files as .bashrc and .bash_profile and I am sure
> there are many others that I will encounter.
Yep, heaps.
e.g.
---------------------------------------
File | purpose
---------------------------------------
.inputrc | Customises readline
I have in my personal .inputrc:
set bell-style none
Which turns off the beeping when tab completing on the command line. :-)
man readline for further info. Note that a .inputrc is not created in
your home directory when you install readline-common. You have to create
it yourself.
> Is it time for me to buy a reference book containing this info? If so,
> which one? I do plan to upgrade to Etch as soon as it is the stable
> release, so if a book is available for sarge, would it be useful for
> etch?
Umm no, because it will soon become outdated. Its easier to
* archive interesting posts
* take note of interesting urls (I have just created a database
in postgreSQL because my list of urls was becoming long and
unweildly.
* search on google for relevant material as needed.
For starters I'd recommend "rute book" and "Debian Survival
Guide" as search terms.
--
Chris.
======
Don't forget to check that your /etc/apt/sources.lst entries point to
etch and not testing, otherwise you may end up with a broken system once
etch goes stable.
Reply to: