This is probably one of the last release in 1.13. 1.14 will target enhancement to the user interface as well as a push in the module technology, notably the availability of stand-alone modules.
The module API had to be extended so each module can report its own set of command lines. See LINUXCONF_MODULE::usage().
See LINUXCONF_MODULE::setmenu() and LINUXCONF_MODULE::domenu(). There are now two versions of those functions.
Because of this change, the binary compatibility of the modules API could not be preserved. This means that all modules must be recompiled. They do not have to be modified though. Install the new linuxconf-devel package before recompiling :-) If you fail to recompile the modules, Linuxconf will prompt you about the incompatibility.
This ability makes the user account dialog more complete in this area. Co-administrator won't need to fiddle with the general email aliases facility (which requires root privileges under Linuxconf) to complete their task.
Another button was added and this should please a lot of people. It is called "Act/changes". It triggers the "Activate changes" of the "control panel" menu, which is the same process you get when you quit. Using that button, it will be much nicer to do various changes and trigger the activation without leaving from Linuxconf, or without digging to locate the control panel menu.
linuxconf --modulemain dhcpd --updatedns
To use this command line, one has to fill the "Update DNS domain" field because DHCP host entry only provide a name, not a name + domain. Once this is done, you can put in a cron job something like this:
#!/bin/sh if linuxconf --modulemain dhcpd --updatedns then /usr/sbin/named.reload fiIn 1.13r12, we are going a bit further. There is now a checkbox in the dialog, right below the "Update DNS domain" field. It is called "Update DNS from cron". You select this checkbox and a special command "/usr/lib/linuxconf/lib/dhcp2dns.sh" is added to root cron. You UN-check it and it is removed. It can't be easier :-)
The side effect of the fix is that the next time you will generate a sendmail.cf, it will complain that the current one was not generated by Linuxconf, which is probably wrong.
This bug explains why Linuxconf did not catch the various changes people were making in the /etc/mail/mailconf rules.
All construct like this one were modified so translators will be able to complete their job on this side. They will have to review a couple of message like this one:
Select [Add] to add ...