Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
install:nix [2019/09/12 17:30] – [Using CVS] Document that the CVSTAG=xxx method doesn't always work because I moved files in cvsroot sometimes digital man | install:nix [2020/03/21 14:42] – [Non-CVS] wrong filename (sbbs_src.tgz, not sbbs_dev.tgz) digital man |
---|
| |
If you want to build a stable release, replace the archive filenames above with valid release filenames: | If you want to build a stable release, replace the archive filenames above with valid release filenames: |
- replace ''sbbs_dev.tgz'' with ''ssrc**317b**.tgz'' | - replace ''sbbs_src.tgz'' with ''ssrc**317b**.tgz'' |
- replace ''sbbs_run.tgz'' with ''srun**317b**.tgz'' | - replace ''sbbs_run.tgz'' with ''srun**317b**.tgz'' |
| |
# chkconfig --add sbbs | # chkconfig --add sbbs |
| |
== Debian == | == Debian (systemd) == |
| |
If using a Debian based Linux, you should use either of the following methods to add the Synchronet system service to your startup configuration for the ''sbbs'' daemon to start automatically during system startup: | Modern Debian-based Linux systems use [[https://wiki.debian.org/systemd|systemd]] to start and control system services (daemons). See [[howto:systemd]] for detailed instructions on configuring Synchronet as a daemon that is started automatically and controlled via systemd. |
| |
| == Debian (SysVinit) == |
| |
| If using an **older** Debian-based Linux which still uses a SysV/init.d daemon/service control system, you should use either of the following methods to add the Synchronet system service to your startup configuration for the ''sbbs'' daemon to start automatically during system startup: |
| |
# insserv -v sbbs | # insserv -v sbbs |
| |
**Note**:\\ | **Note**:\\ |
If you elect to build //debug// binaries (instead of //release// binaries), then you'll need to //exclude// the ''RELEASE=1'' portion from the ''cleanall.sh'' command. Otherwise, you'll be cleaning the ''*.release'' output directories when you really need to be cleaning the ''*.debug'' output directories. Likewise, if you're building and running //release// binaries, then you need to //include// the ''RELEASE=1'' portion on the ''cleanall.sh'' commandsas well. Alternatively, you can set your default build type in the file ''localdefs.mk''. The ''localdefs.mk'' file should be created by you in either in the ''src/build'' directory (to apply to //all// builds), or within each directory you run ''make'': | If you elect to build //debug// binaries (instead of //release// binaries), then you'll need to //exclude// the ''RELEASE=1'' portion from the ''cleanall.sh'' command. Otherwise, you'll be cleaning the ''*.release'' output directories when you really need to be cleaning the ''*.debug'' output directories. Likewise, if you're building and running //release// binaries, then you need to //include// the ''RELEASE=1'' portion on the ''cleanall.sh'' commands as well. Alternatively, you can set your default build type in the file ''localdefs.mk''. The ''localdefs.mk'' file should be created by you in either in the ''src/build'' directory (to apply to //all// builds), or within each directory you run ''make'': |
RELEASE=1 | RELEASE=1 |
| |