1 config files in etc need updating

by  |  29-Nov-2019 17:19

1) /etc/udev/rules.d/50-udev.rules /etc/udev/rules.d/._cfg0000_50-udev.rules 2) /etc/init.d/bootmisc /etc/init.d/._cfg0000_bootmisc 3) /etc/init.d/checkfs /etc/init.d/._cfg0000_checkfs 4) /etc/init.d/checkroot /etc/init.d/._cfg0000_checkroot 6) /etc/init.d/clock /etc/init.d/._cfg0000_clock Please select a file to edit by entering the corresponding number.

Welcome to Linux Questions.org, a friendly and active Linux Community. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.

1 config files in etc need updating-32

1 config files in etc need updating

We are using the Subversion RCS, but the same concepts apply whether you are using other systems (such as CVS or Arch).

The RCS will want to act on a single directory tree, but in most cases our configuration files are spread out over the file system. (The portage “world” file, a record of everything installed on your system, for instance, is in /var/lib/portage.) What we do is create a directory called /server-rcs that will be managed by the RCS, and in that directory is copies or links to all of the configuration files on the system.

The first step is to put the system configuration files into a revision control system (RCS).

An RCS allows us to track the history of files by storing information about changes such as the date/time a change was made, what the change was, who made it, and a free-text field explaining why the change was made.

Besides, that oral history tradition is difficult to maintain and harder to sustain as the number of machines grows.

Community Discussion