Red Hat Bugzilla – Bug 717397
Provide native systemd unit file
Last modified: 2011-07-21 07:58:32 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 510334 [details]
Native systemd service file for capi
How do you want to proceed with the isdn service is it possible to simply hardware activate it?
Unfortunately our guidelines are a bit short on how to do that
Hardware activation occurs when a service is installed but only turns on if a certain type of hardware is installed. Enabling of the service is normally done with a udev rule. At this time we do not have further guidance on how to write those udev rules. The service itself installs its .service files in the normal places and are installed by the normal systemd scriptlets. These services should never be enabled by the package as they will be enabled by udev.
But you can read man systemd.device and look at the bluetooth service which is doing that I believe..
--- Comment #3 from Jóhann B. Guðmundsson <email@example.com> 2011-07-11 11:33:50 EDT ---
What's the curent status on this?
If you dont have the time to package this make note of that on this bug and I
can see if I can find a proven packager you can package this for you...
frack paste fail.. ;)
Hi Jóhann, i just don't have time to fix this issue. It's great if we could find someone who can take care of this. Thanks
capi.service applied and new package built for rawhide:
The isdn service is still using SysVinit scripts so this bug still needs attention.
Created attachment 513459 [details]
Native systemd unit file for isdn
Remove the legacy sysv init script and install it as per this packaging guidelines  should work can be used as a solution until the maintainer finds time to clean that up properly port it over then we can declare the dial up group done....
it's fixed in isdn4k-utils-3.2-77.fc16