starting Fedora Server SIG

Jeremy Katz katzj at
Fri Nov 14 16:09:24 UTC 2008

On Fri, 2008-11-14 at 07:43 +0100, Dan Horák wrote:
> Chris Adams píše v Čt 13. 11. 2008 v 19:59 -0600:
> > How is a daemon (or set of daemons) useful for a static configuration
> > that does not change?  For the vast majority of my servers, the network
> > config is set in the kickstart %post and not touched for the life of the
> > server (which is typically many years; I've got a RHEL 3 server that
> > hasn't had a network change since Feb 2004 for example).
> > 
> > For servers, the simpler solution (that meets the needs) is always
> > better, and running multiple daemons to configure the network is
> > definately not simpler than a text file and "ifup".
> That's 100% true and maintaining "/etc/init.d/network" for the future
> will be our SIG's job. When there is a "link down" event on the server
> then you call the network administrator :-)

It's more than just /etc/init.d/network that has to be maintained.
There's oodles of stuff in install-time configuration that will have to
be maintained, tested, and have things fixed when people report them.
There will be a need to maintain a separate initrd infrastructure[1].
And those are the two things that are closest to what I'm thinking about
today and by no means an exhaustive list.


[1] Currently, we use libdhcp in the initrd for things like iscsi,
nfsroot, and nbdroot.  libdhcp is going away in F11 so we're going to
have to rework the network config code and the sensible thing is to move
to using NetworkManager like the rest of the distro so that we don't
have to maintain another codebase.  Note that there's still a fair bit
of handwaving involved here since we haven't sat down to really figure
out how to make some of the trickier parts work yet :)

More information about the fedora-devel-list mailing list