Fedora.next: I would like working configurations
Robert M. Albrecht
lists at romal.de
Mon Jan 27 18:31:58 UTC 2014
might be totaly out of scope for Fedora.next, but this is what I would
like to get better in Fedora.
If I install a Windows-Server with some services like DHCP or file
services, I get a working configuration.
- If I install a Fedora-server with dhcpd, dhcpd doesn't do anything
- If I install tftpd and syslinux, I don't get a working pxe-config
- If I install postfix, I don't get a working mail-server
- If I install Nagios, it does not monitor & report anything
I have no idea, how to change this. Debian uses some interactive stuff
to create a more or less working configuration while installing a
package. This resembles the Microsoft installation tools.
But rpm is strictly non-interactive, so this would not work for Fedora.
I think this is a real problem. The missing working default-configs are
a real hassle for replacing small servers in Windows-shops with Linux as
the non-expert-Linux-admin has an enormous entry-barrier to get some
minumum working configuration from which he can start.
To build a Fedora-Server which does the needed ip address management
stuff for a modern network (dhcpd with dynamic bind-updates for IPv4 and
IPv6 plus forwarding to the isp) is non-trivial, even for a long time admin.
Perhaps meta-packages (call them roles or stacks if you like) like ipam
(pulls in dhcpd, bind, ... plus some config-files) or mail-server (pulls
in postfix, imap, fetchmail, ...) might be the solution.
I have no idea how to do this. Combing several packages and integrating
them would produce some interessting test-problems. How to avoid
colliding apache-configs done by different meta-packages, ...
More information about the devel