On Fri, 2014-04-04 at 11:59 -0400, Bill Nottingham wrote:
(ignoring firewall, answering the other questions)
Matthias Clasen (mclasen(a)redhat.com) said:
> - Do we want fedora-readonly included ? This is coming from the
> readonly-root feature, but it is off by default, and don't think it is a
> tested configuration, so who knows if it works. And we're probably not
> going to turn it on for the Workstation
It's how ovirt-node and assorted smaller images run, so it is a tested
configuration in some cases. Likely less so in the Workstation case,
ah, thanks for the information.
> - What is fedora-configure, and why is it installed ? It seems
to be a
> complicated way of triggering 'system reconfiguration' which in this
> case means running a shell script as a systemd service, which in turn
> runs /usr/bin/firstboot. Since /usr/bin/firstboot has been replaced by
> anacondas initial-setup, I can only conclude that this functionality is
> also unused, untested and not working, and should probably be removed.
As the guy that merged this way back in the day, I'm fine with it going away
in favor of something like virt-sysprep for those that need to deconfigure
their system. But I don't maintain it any more - file an initscripts bug?
Filed as https://bugzilla.redhat.com/show_bug.cgi?id=1084642
Now that I'm looking at initscripts, there's a few fedora-specific
services that I find somewhat dubious.
fedora-domainname - is that still relevant ? If yes, it should probably
live with the component that handles network identify nowadays, sssd ?
fedora-loadmodules - seems redundant and should be phased out in favor
of systemd-modules-load, I'd say.
fedora-import-state - this tries to be conditionally activated when
there is state in /run/initramfs/state, but at least on my system, it
_does_ run and import an empty directory tree :-(
$ tree /run/initramfs/state/
| `-- sysconfig
| `-- network-scripts
I guess transferring network state from the initramfs will change
anyway, with networkd ante portas...