Hi,
dhcpd is just an (maybe bad) example.
But even dhcpd needs a lot of work. I need to configure ranges, options
(which could like gateqway and dns partly automagically gathered from
the exsting network configuration), ... binding dhcpd to bind to enable
dynamic updates, ...
and double this stuff for IPv4 and IPv6.
I used this only as an example to show that nearly all daemons are not
ready-to-run.
cups and apache are not sharing user-groups with samba and nagios, ...
Integration of services is often possible, but not done when doing a
fresh Fedora installation.
What I would like is more integration to produce a working "server". If
I create a user group, it should be known in all installed services.
This might not be restricted to servers: all audio-components are there
to do some professional work: jack, pulseuaudio, alsa, Audacity,
plugins, ... but I have to fiddle them together myself.
cu romal
Am 27.01.14 21:01, schrieb Dan Lavu:
Most of the services you described do have a "working" configuration but
the service is not turned on. You are right though, when you install a
Windows CA it's ready to go. In regards to DHCP, the dhcpd.conf file has
a commented sample that needs to be edited and then turned on. Is this
what you are looking for?
On 27/01/14 14:33, Chris Adams wrote:
Once upon a time, Robert M. Albrecht <li...@romal.de> said:
If I install a Windows-Server with some services like DHCP or file
services, I get a working configuration.
Can you be more specific on what you mean by "working configuration"?
As far as I know, you still have to configure the service on Windows
before it does anything. How could a "default" install of a DHCP
service possibly know what to do without configuration?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
