Linuxconf uses, manages, probes and generates various files. The current list shows the filenames, the path to the files, and a set of flags. The following values are possible:
This file is only read by linuxconf, which means one of two things. Either it is a reference file used by Linuxconf or Linuxconf does not know yet how to manage this file, but may use its contents.
This file is erased at boot time by linuxconf.
This file is generated by Linuxconf. It never
reads it again. Linuxconf uses other files
(probably /etc/conf.linuxconf) to store
the configuration related to this service.
For example, the file /etc/sendmail.cf is used this way.
The file is fully managed by Linuxconf. Linuxconf knows how to parse it and write it back properly. This also means that you are allowed to edit the file by hand (using a text editor) without breaking Linuxconf's ability to manage the file.
This file is optional on a Linux system; its existence is not crucial. However, erasing it is not a good idea.
Linuxconf knows little about this file, but does probe for its presence and modification time. Based on these facts, Linuxconf will decide if a service is needed or if a daemon must be restarted or signaled.
Linuxconf uses special virtual files. They generally represent limited views of some real config file. These files are used especially to achieve fine-grain-system-profile- versioning and cluster management.
This flag indicates that the path to the configuration file has been changed from the original/official value known by Linuxconf.