Fedora Account System
Red Hat Associate
Red Hat Customer
* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No manual intervention needed At least not yet, but the secureboot feature might generate secureboot keys in the same way the apache x509 keys are created for a webserver. * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No * Is the service non-persistent (i.e. run once at startup and exit)? Yes * What is the exact name (or names) of the systemd unit files to be enabled? akmods.service * Is this request for all Fedora deliverables or only for some Editions (list them)? ALL This service is similar to dkms that is already enabled. It should be enabled by default on every Fedora releases and EPEL7. Thx
(In reply to Nicolas Chauvet (kwizart) from comment #0) > * Does the service require post-rpm-installation configuration in order to > be useful (for example, does it need manual edits to a configuration file)? > No manual intervention needed > > At least not yet, but the secureboot feature might generate secureboot keys > in the same way the apache x509 keys are created for a webserver. > That's not an issue. These should follow https://fedoraproject.org/wiki/Packaging:Initial_Service_Setup and be set up by a systemd unit. See also https://src.fedoraproject.org/rpms/httpd/blob/master/f/httpd-init.service for an example. > * Does the service listen on a network socket for connections originating on > a separate physical or virtual machine? > No OK > > * Is the service non-persistent (i.e. run once at startup and exit)? > Yes > > * What is the exact name (or names) of the systemd unit files to be enabled? > akmods.service > > * Is this request for all Fedora deliverables or only for some Editions > (list them)? > ALL > > This service is similar to dkms that is already enabled. > It should be enabled by default on every Fedora releases and EPEL7. > > Thx This meets all of the requirements specified in the policy, so it does not need to go to FESCo. I have submitted https://pagure.io/fedora-release/pull-request/121 for the fedora-release package in Rawhide/F28.
Pushed to rawhide. Should show up in tomorrow's compose.