#283 closed defect (fixed)
man.conf location
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description
currently man.conf ends up in /usr/share/man/man.conf
In my reading of the FHS it should be in /etc/man.conf really. IMO we should add an FHS compliance note on how to do that here (as we do for various other packages)
Change History (7)
comment:1 by , 23 years ago
comment:3 by , 23 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
The easiest way to do this is adding "mv /usr/share/misc/man.conf /etc". The man program will look for man.conf in a number of directories, including the /etc directory.
comment:4 by , 23 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 by , 23 years ago
I know this has been closed but I just wanted to check this with you all. (Note, I wrote this in between Gerard assigning the bug and closing it ;-))
just for the record; this is the relevant code I believe:
from src/man-config.c
char *default_config_files[] = {
CONFIG_FILE, /* compiled-in default */ "/etc/man.conf", "/etc/man.config", "/usr/lib/man.conf", "/usr/lib/man.config", "/usr/share/misc/man.conf", "/usr/share/misc/man.config"
};
CONFIG_FILE gets defined in paths.h (from paths.h.in) as: #ifndef CONFIG_FILE #define CONFIG_FILE "/usr/share/misc/man.conf" #endif
so we can either just make sure we move the file away or alternatively couldn't we just pass a -D option in or sed paths.h to make it more correct?
comment:6 by , 23 years ago
True, that's possible but since it's not really necessary, a mv is a lot easier to type out.
Changed previous last paragraph, plus added a new one:
If you don't know what to answer to all the questions asked during the <userinput>make</userinput> phase, then just accept the default. It'll be just in fine in the majority of the cases. What you are asked here are a bunch of questions relating to the kind of network protocols that you have enabled in your kernel.
The default answers will enable the most common protocols that will allow you to perform TCP/IP networking, connect to the Internet and some other protocols. You still need to actually enable these protocols in the kernel. What you do here is merely telling the programs to be able to use those protocols but it's up to the kernel to make it available to the system.