All configuration files Introduction 11.. PPuurrppoossee _L_i_n_u_x_c_o_n_f uses, manages, probes and generates various files. The current list shows them all. The list present the path of the file and a set of flags. Here are the different values possible: ((AA bbllaannkk)) This file is only read by _L_i_n_u_x_c_o_n_f. This means two things. Either it is a reference file used by _L_i_n_u_x_c_o_n_f or _L_i_n_u_x_c_o_n_f does not know yet how to manage this file, but use its content. Management of the file is left as a exercise :-) EE This file is erased at boot time by linuxconf. GG This file is generated by _L_i_n_u_x_c_o_n_f. It never read it back. _L_i_n_u_x_c_o_n_f use other files (probably /etc/conf.linuxconf) to store the configuration related to this service. /etc/sendmail.cf is an example of this. MM The file is fully managed by _L_i_n_u_x_c_o_n_f. This means that _L_i_n_u_x_c_o_n_f knows how to parse it and write it back properly. This means also that you are allowed to edit the file by hand (using a text editor) without breaking the ability of _L_i_n_u_x_c_o_n_f to manage it. OO This file is optional on a _L_i_n_u_x system. Not having it is not bad. This does not mean erasing it is a good idea :-) PP _L_i_n_u_x_c_o_n_f knows little about this file. It only probes for its presence and modification time. Based on this, _L_i_n_u_x_c_o_n_f will decide if a service is needed or a daemon must be restarted, or signaled. VV _L_i_n_u_x_c_o_n_f uses special virtual files. They generally represent limited views of some real config file. This is especially used to achieve fine grain system profile versionning and cluster management. ** This flag indicates that the path of the configuration file has been changed from the original/official value known by linuxconf.