Re: is anybody using fedora-loadmodules.service and fedora-readonly.service?

[Hedayat Vatankhah]

Hi,

/*Zbigniew Jędrzejewski-szmek*/ wrote on Sat, 7 Oct 2017 07:18:59 +:

Two boot-time services provided by the venerable initscripts package:

<...>

- fedora-readonly.service: this is used to mount parts of the filesystem rw
   in case the system is using read-only root filesystem. To do anything this
   service checks if READONLY=yes is set in /etc/sysconfig/readonly-root.

   Is anybody using this? If yes, would it be OK if the service was not
   enabled by default anymore and would require an explicit 'systemctl enable
   fedora-readonly.service' or creating a custom preset (in addition to
   setting READONLY=yes) to be active?
I do! Yes, I don't care if it should be explicitly enabled, but I really 
hope that it won't vanish. I even don't care if you do not need to 
specify READONLY=yes if it is enabled explicitly (enabling it can mean 
that you really want READONLY=yes).






See https://bugzilla.redhat.com/show_bug.cgi?id=1493479 and
https://pagure.io/fesco/issue/1779 for some more info.

<...>
fedora-readonly.service is based on mounting tmpfs dirs, copying files
around, doing selinux fixups, manually mounting rpcfs and nfs, etc. I have never
seen fedora-readonly.service actually used, but that doesn't mean much.
If people are using them I'd love to hear about their use cases, and
think if we can provide the same functionality using more modern
mechanisms. Without breaking existing setups, I'd like to disable this
by default to simplify the boot process and not encourage the use in
new installations. ]
fedora-readonly.service is actually an advanced utility to let you 
configure the system to be used with fully or partly read-only root 
filesystem. I've used it, and are very likely to use it again and again 
in future, to deploy 'reliable' Fedora instances, which are either fully 
read-only, or let you write in a very specific locations and make sure 
that your / partition will never be corrupted for any reason. It is a 
great feature for using Fedora in embedded devices.


Anyway, I don't see why it can't be disabled by default, but I hope it 
is not removed... at least not until there is a replacement with 100% of 
its features.


Regards,
Hedayat




Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

is anybody using fedora-loadmodules.service and fedora-readonly.service?

[Zbigniew Jędrzejewski-Szmek]

Two boot-time services provided by the venerable initscripts package:

– fedora-loadmodules.service: this loads kernel modules based on
  configuration in /etc/rc.modules. Identical functionality is provided by
  systemd-modules-load.service. (systemd-modules-load.service reads 
  modules-load.d directories and the kernel command line, not /etc/rc.modules).

  Is anybody still using /etc/rc.modules? It'd be nice to just drop support
  for /etc/rc.modules by not enabling fedora-loadmodules.service by default,
  and then drop it completely.

- fedora-readonly.service: this is used to mount parts of the filesystem rw
  in case the system is using read-only root filesystem. To do anything this
  service checks if READONLY=yes is set in /etc/sysconfig/readonly-root.

  Is anybody using this? If yes, would it be OK if the service was not
  enabled by default anymore and would require an explicit 'systemctl enable
  fedora-readonly.service' or creating a custom preset (in addition to
  setting READONLY=yes) to be active?

See https://bugzilla.redhat.com/show_bug.cgi?id=1493479 and
https://pagure.io/fesco/issue/1779 for some more info.

[ Why disable those services by default? The most obvious reason is that this
is additional stuff the runs during boot, making things a tiny bit slower and
the logs slightly more verbose. But this is very weak reason. More important
is that the way those services are implemented is largely obsolete.

fedora-loadmodules.service is completely duplicated by 
systemd-modules-load.service,
so it'd make sense to drop the Fedora-specific service.

fedora-readonly.service is based on mounting tmpfs dirs, copying files
around, doing selinux fixups, manually mounting rpcfs and nfs, etc. I have never
seen fedora-readonly.service actually used, but that doesn't mean much.
If people are using them I'd love to hear about their use cases, and
think if we can provide the same functionality using more modern
mechanisms. Without breaking existing setups, I'd like to disable this
by default to simplify the boot process and not encourage the use in
new installations. ]

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org