Difference between revisions of "Starting packet radio on bootup"
(Explain startup of AX.25 services in particular in the new fangled world of systemd.)
Latest revision as of 13:26, 19 May 2015
All released version of [ax25-tools] and [ax25-apps] do not include the necessary scripts or configuration data to automate startup on bootup.
System V Init
Neither ax25-tools and ax25-tools nor any known distribution is shipping init scripts to start the desired daemons on bootup. Due to this startup at boot time is typically scripted by the system adminstrator in rc.local which depending on your distribution and its vintage lives somewhere in etc.
Systemd is a still relatively new, very powerful and complicated replacement for the venerable System V init. It does not use the traditional init scripts in /etc but relies on configuration files written in a simple syntax to declare in what order to start which services at boot time. As AX.25 requires configuration by default all related services are disabled. This section describes the available unit files.
Please note that everything described in in the systemd section is work in progress and currently unpublished.
To enable this service, use systemctl enable ax25d.service. If you also enable packet-radio.service (see below), ax25d will be started when the system is booting multiuser. You should review ax25d's configuration before starting this service.
To enable this service, use systemctl enable mheardd.service. If you also enable packet-radio.service (see below), mheard will be started when the system is booting multiuser.
To enable this service, use systemctl enable netromd.service. If you also enable packet-radio.service (see below), netromd will be started when the system is booting multiuser.
Starting this target with systemctl start packet-radio.target will start those of ax25d.service, mheardd.service and netromd.service which have been enabled. If enabled with systemctl enable packet-radio.target this will automatically happen when the system is booting multiuser.
There is no support for daemons other than those listed currently, that is those will still need to be started manually by the sysadmin as explained in the System V Init section above.
Upstart and others
There is no specific support for upstart and other inits. However they do suport some rc.local script like System V Init so can be treated just like that.