Comment # 2 on bug 856906 from Axel Braun

Please note that your link refers to hylafax+, while the version distributed in
oS 13.2 is still hylafax.
We had planned to switch to hylafax+ but that got lost on the way....
Anyway, I checked with Lee Howard (the author of hylafax+) on his opinion on
that, here is his answer:
---
There never has been a mechanism in HylaFAX faxsetup/faxaddmodem to 
create configuration entries for /etc/inittab, upstart, or systemd. So, 
in my Fedora package I merely followed the historical approach with 
requires the system administrator to create those entries.

Historically this has not been without a substantial number of 
complaints from users who expect faxsetup/faxaddmodem to create these 
entries.

In the Debian package the maintainer has the HylaFAX startup script 
simply run faxgetty for each config.<modem> file found in the HylaFAX 
spool/etc directory.  (I don't think that this is a very good approach.)

Personally, I don't care whether we develop faxsetup/faxaddmodem to 
create the system unit files or continue to require the system 
administrator to do this.  I think that if we're trying to be nice that 
we ask in faxsetup/faxaddmodem if the user wants us to create them and 
to then do what is selected.  However, as I do most of my installs, 
myself, I haven't had much motivation to do this... since I almost 
prefer to do it by hand.
---

I have added an example for faxgetty to my hylafax+ build, feel free to test. I
run this as a send-only environment, so I cant test the faxgetty 
https://build.opensuse.org/package/show/home:DocB/hylafax+