Linuxconf 1.7R23 (Test release)
Linuxconf 1.7r23 will probably Linuxconf 1.8 or very
close. There has been too much time between the two releases and 1.7 offers
quite a few improvement over 1.6. Any comments welcome. There are many
improvement coming for 1.8 (1.9 indeed). I think this is the time before
jumping on too many new features.
Anyway, here is the change log
- There is now an uninstall script which get your system exactly as before
you install linuxconf.
- Some spell checking here and there. There is still room for improvement in
- When linuxconf try to execute a command and the command is missing, it
pops a dialog and let you configure the command right on the spot. You can
change the path, the arguments and you can also tell Linuxconf not to manage
this anymore. This dialog is not new in linuxconf. What is new is the fact
that linuxconf trigger it whenever something is missing.
- There is now support for installation on a Debian system. Debian system
use many SysV init scripts and Linuxconf is not using them. Nevertheless,
Linuxconf works quite well on a Debian system. The installation script have
been tuned to support debian. Basically
expected Debian has
While you can do those change interactivly with linuxconf, the install script
does it for you.
Beware that the basic nslookup supplied with debian is incompatible with
Linuxconf. If you have problem with Linuxconf claiming that your DNS is not
operating correctly, make sure you install the bind package of Debian: It
supply the "real" nslookup and make linuxconf happy. I am currently
talking with Debian people about the validity of having two nslookup.
- Linuxconf was not using the PID files for some daemons even if they were
available. Few daemon are forking. Sendmail is one and in some special case,
Linuxconf was not killing the proper one when activating a new configuration.
It now use /var/run/sendmail.pid is available.
- It has been tested on redhat 4.0 also. Some redhat have
/usr/sbin/rpc.portmap, some have /usr/sbin/portmap. When linuxconf will
complain, you'll be able to fix it interactvly. All these kind of linuxconf's
own configuration are independant of the distribution so linuxconf won't
bother you if you install a newer linuxconf.
The install script is tuned for official redhat 4.0 (but still support redhat
3.0.3 and 2.x).
- When probing the configuration of an absent network device, Linuxconf was
triggering the load of the driver for those using kerneld. Now it check in
/proc/net/dev before asking further questions to the kernel.
- When writing to the /var/log/netconf.log file, linuxconf more properly
identify the reason. The different log appears then as
PPP postconnect commands
- Linuxconf support the keyword xfernets and bogusns although it does
nothing with them. It only preserver what was there. Preliminary.
- Linuxconf really check that there is a DNS configured in /etc/named.boot
before starting named. On systems like Slackware, a /etc/named.boot is
supplied with comments and named was started for nothing.
- More gentle with the /proc entry in the fstab. Fix it when broken. Some
distributions put something like this
proc /proc proc ...
none /proc proc ...
- If there were some configuration errors, it was not reported and the
broken DNS was activated. Now it report errors. Could be improved though. The
errors are catche so low, it is difficult to tell from which rule they come.
If there is any error, the DNS is not activated.
- A check box have been added to the "linuxconf network access"
dialog in networking allowing you to collect logs of connexion in
/var/log/htmlaccess.log. Will be useful for the demo mode of linuxconf.
- It was possible to tell linuxconf that you don't use LILO. But the dialog
was dumb and required that you had a valid LILO config anyway. Further after
quitting from the dialog, linuxconf was trying to run LILO. Fixed!
- The linuxconf's logs is now better organised. When you view it you can see
the section related to booting and others related to configuration changes.
- Even if you told linuxconf not to user mailertable (for special domain
routing), it was attempting to initialise the file /var/lib/mailertable.
- The privilege associated for virtual domain administrator has been
changed. The key was too simple and could have clashed with other privileges
in the privileges database /etc/conf.linuxconf. The encoding was
PRIVI_foo.com.user value (where foo.com is an example).
It is now
Those who are using these privilege, just regrant them to your users or edit
by hand /etc/conf.linuxconf.
- In the ppp dialout configuration dialog, it is now possible to specify
routing information (beside the default route). You can enter pairs of
network/netmask. No need to fiddle in /etc/ppp/ip-up anymore.
Linuxconf will modify /etc/ppp/ip-up (ask you before doing it) and will put a
callback to it. With this feature, linuxconf is able to manage multiple PPP
dialout and kill (netconf --disconnect) the proper one.
An interactive mode in the control panel will be added, displaying all dialout
connexion and allowing you to kill them.
The same mechanism will be added to PPP account configuration making the
ppplogin scripts useless (but still supported). Should be done after the
release of 1.8. Perfect for ISPs.
- Linuxconf was checking /etc/XF86Config to tell if X was configured. It is
now checking also /etc/Xaccel.ini.