Linuxconf 1.9r5 (Test release)
- Linuxconf now operates on Sparc-linux (RedHat 4.0). SILO is
not supported yet though. ftp.solucorp.qc.ca and www.solucorp.qc.ca are
managed by a Sparc ELC btw, runing Linux!
Another tester (running an ISP with virtual domains) is running Sparc Linux
- The default configuration for the boot mode is "Text &
network" with a timeout of 20 seconds. Far too many people were not
reading the message at the end of the install and were quite surprise to find
out that their mission critical server did not reboot all by itself. This
should cause much less surprise.
- When booting, if a command was taking to long to complete, the default
behavior (let it run in the background) did not work. The dialog was looping.
You really had to kill the process (using the dialog). This also means that
when the system was booting unattended, linuxconf could have looped forever if
some configuration problems were detected.
- Minor changes to the way the loopback network device is configured to
please linux 2.1. Compatible with any kernel though.2
- It was not possiible to delete a dropin. The DEL button was available when
doing "local" configuration. In that case it is meaningless. Local
configuraiton allows one to override the content of a dropin without actiually
changing the file in /etc/linuxconf/control. Deleting a dropin there is
useless. Better go to the control panel and deactivate it.
- When adding new login shells (PPP account or shell account), linuxconf was
not validating properly the existence of the shell. Now it will tell you if
the shell is missing or if it is there but you forgot to make it executable
(Common error for PPP login scripts).
- Linuxconf now make sure that names enter in a DNS are limited to alpha,
digits and -. Other character will be signal.
- Linuxconf was a bit too smart about absolute names. It was forcing a dot
at the end of every name (because it is a much to common error to forget it).
Now it will put a dot only if there is one dot in the name. So a name without
dot is taken as a local name.
- The "basic configuration" dialog was reworked. Some field title
were renamed this way
- mail host -> mail server
- smart host -> mail gateway
- smart host mailer -> mail gateway protocol
- A new field has been added. It does not add functionality at all but
should make it clearer. Most people configuring a mail server (for a domain)
forget to go at the end of this dialog and write the name of the domain (alias
for your system, when receiving). For example, if you configured sendmail on
the machine mail.foo.com and this is the main mail server of foo.com, you
should tell sendmail to accept mail for foo.com also. Too many people forget
that and get an error in their log telling that sendmail try to forward email
for foo.com but find out that the MX for foo.com is mail.foo.com. To make this
much visible, the new field is a check box and the title is computed for the
current domain. It simply goes like this
[ ] Accept email for foo.com
It is the second field of the dialog. I guess, people won't miss it. If you
check that checkbox, then Linuxconf will simply generate a line "Cw
foo.com" in sendmail.cf. Those who already have their configuration right
won't be affected by this change. I mean, the "alias for your
system" section is still functional. I have fixed the help file about
- The virtual domain mail utilities vpop3d and vdeliver are now talking to
syslog. This should help track configuration problems.
- First attempt at supporting the DHCP daemon configuration. This is
the dhcp server from the Internet Software Consortium, available from ftp://ftp.fugue.com/pub.
This looks like this will replace whatever dhcp/bootp server package out
there. For now, Linuxconf knows how to read/write the file (The syntax is
quite readable, and provide a nice dialog to configure few subnets. bootp
hosts entry are not functional. I would be happy to get comment on this. For
those who don't know much about dhcp, here is a recipe to configure TCP/IP on
W95 when a dhcp server is available.
"Tell it you want TCP/IP and reboot"
I am planning to support the dhcp client also right in Linuxconf (A checkbox
in basic host information). Unlike, W95, you won't have to reboot :-)
Anyway, I would like to get comments on the following topics:
- General usability of the configuration dialogs
- Any thoughts about the principle allowing some linkage between the dhcpd
server and the DNS configuration. Is there a need for that. I know that NT
does this, but behave poorly as a DNS. Linux is good as a DNS. Comments
welcome. I am planning Samba management shortly, so if you have idea about how
to link information from the dhcpd server to the Wins configuration (lmhosts
file), welcome also.
- Do not attempt to read your current /etc/dhcpd.conf file with it.
Especially if you use share-net. A good explanation on this concept would be useful.
- Validation of port range and port list was broken. It was giving the
impression that only numeric values were accepted. For the protocol ICMP
and ALL, ports are meaningless and are not accepted. The message is
- I am thinking about revamping the firewall dialogs. I intend to do a
larger dialog when one will see all the configuration for all 3 protocol
(ICMP, UDP, TCP) between to network. Comments are welcome about this.