remadmin --exec guispy /tmp/in.log /tmp/out.log linuxconf \ --guiproto
This features might be handy to give a different look to the various servers you are managing, avoiding doing configuration changes ... on the wrong server.
The first one compares the current configuration file with the last version archived. The second one shows all the revision of all the configuration file of the given sub-systems. All configuration file are presented if no sub-system are supplied on the command line.
These options are limited and could be enhanced. Comments and requests are welcome.
The *.paths are new. There is one Linuxconf.paths per distribution and each module may supply one. The CONFIG_FILE object has been enhanced. The path provided to this object has now two functions: It is both a default path for this configuration file and a key in the *.paths. Those *.paths are simple lookup allowing one to redefine the standard path for a configuration file in one distribution.
A document will be written to explain the various strategies used in Linuxconf to expand modules compatibility.
Various strategies are studied to decide how a given service must be delivered (as a module or built-in). Comments and ideas are welcome.
Linuxconf has now some ability to detect if a new sendmail.cf file is required after a configuration change (whatever it is). Before replacing it, it checks that the one in place was generated by itself. Linuxconf records the MD5 checksum of the sendmail.cf it generates so it knows if the one in place was generated by itself.
Before replacing a modified (manually I guess) sendmail.cf. Linuxconf requires confirmation of the operator and produces a backup.
Various changes were done to move to this new strategy which was debugged over various test release. It is believed to be reliable (and very useful, from the comment received). It is also documented in the various help screens.
To enable this feature, just add the netadm module to your configuration using the "Control file and systems" menu and then the "Linuxconf's module" menu. A new top level menu will appear named "Cluster administration".
Here is the help screen for this module which you give you a nice introduction to the concepts. Just click here.
One nice feature of the bootp support is the ability to check with the bootp server each time linuxconf does its sanity check. This means that if you are doing some adjustment to your bootp configuration on the bootp server, just by doing a "linuxconf --update" on the workstation using bootp is enough to make those changes effective (no reboot).
Linuxconf will fix the /etc/resolv.conf with this information. Currently, the bootp support is done, except for a buglet to fix. dhcp support is not done. The button is there in the "basic host information" dialog though.
Some more work will be done to enhance the way Linuxconf reformat the line it edits. It will make it nicer for those who still edit this file by hand!