automated installations (9)22 Feb 2006 Old and busted: exim4
new hotness: postfix
After specifying that the kulnet-common-packages (a package that depends on all the common packages we want on all servers) CONFLICTS with exim4 and all other exim-* packages, postfix was installed automatically.
The only problem was the configuration. Apparently, configuring postfix through preseed is a bad idea (if it works at all). But that's ok!
We have several differently configured postfix instances on our servers. Some need to be just a satellite system, while others should be fullfledged mailservers.
I made a package kulnet-postfix that writes the standard config for a satellite system, from the postinst script. And it works nicely :)
The kulnet-postfix package will be installed separate from kulnet-common-packages because not all servers need that kind of mail configuration.
[TODO: I need a question in the debian installer to select what kind of system should be installed. All other questions so far are asked from within the netcfg package. I'm considering asking that new question there aswell. It doesn't exactly have anything to do with network configuration, but I'm too lazy to find out where the right place would be. In fact, it's probably better to add it there to make the patch to go from a standard debian CD to our install CD, smaller]
I've also made a kulnet-ntpdate and a kulnet-openntpd package, both depending on ntpdate and openntpd respectively. The kulnet- packages just (over)write the default configuration. In our case, we use ntp.kuleuven.be instead of the standard pool.ntp.org. For some reason, restarting openntpd from the kulnet-openntpd postinst script, makes the debian installer hang after the postinst script exits. I have no idea why. For now, I just commented out the restart of openntpd.