marinetore.blogg.se

#Synchronet display menu screens install#
#Synchronet display menu screens code#
#Synchronet display menu screens password#

Lrwxrwxrwx 1 rswindell sbbs 32 Sep 30 18:58 webv4 -> /home/rswindell/sbbs/repo/webv4/ Lrwxrwxrwx 1 rswindell sbbs 29 Sep 30 18:47 web -> /home/rswindell/sbbs/repo/web Lrwxrwxrwx 1 rswindell sbbs 30 Sep 30 18:47 text -> /home/rswindell/sbbs/repo/text rw-rw- 1 rswindell sbbs 10641 Sep 30 19:04 GNUmakefileĭrwxrwx- 2 rswindell sbbs 4096 Sep 30 18:47 node1ĭrwxrwx- 14 rswindell sbbs 4096 Sep 30 18:37 repo Lrwxrwxrwx 1 rswindell sbbs 30 Sep 30 18:47 exec -> /home/rswindell/sbbs/repo/exec Lrwxrwxrwx 1 rswindell sbbs 30 Sep 30 18:47 docs -> /home/rswindell/sbbs/repo/docs If you installed with the ''SYMLINK=1'' option, the resulting installation directory tree should look like this:ĭrwxrwx- 3 rswindell sbbs 4096 Sep 30 18:47 ctrl If this is a problem, you can include ''NOCAP=1'' on the ''make'' command-line to bypass that step.

On //Linux// systems, your user password will be prompted for to execute the ''sudo setcap'' command during install.

We don't support parallel builds (e.g.

To make and install a //DEBUG// build instead, pass ''DEBUG=1'' on the ''make'' command-lines.

These commands will make and install a //RELEASE// build of the software.

NOTE: this does not work with current release tags, use the Tarball install method instead.

''$ install:nix:make install SYMLINK=1 TAG=sbbs3xxx''.

Or, if you want to build a stable release from Git, specify a valid release dev:tags on the make command-line (e.g.

''$ install:nix:make install SYMLINK=1''.

Quick installation from dev:Git (requires 100+MB of disk space): displays an error message), click the highlighted text for more details including common causes of errors.Ĭhoose a build method (using dev:Git or Tarball)((The Git install method is preferred/recommended)): If a specific step below causes problems (e.g. The remaining steps assume that the current working directory is your Synchronet installation directory: ''ln -s /home/sbbs/sbbs /'') or set the '' config:env#SBBSCTRL'' environment variable accordingly. ''/sbbs'').īy default, Synchronet executables will look for files in the ''/sbbs/ctrl'' directory, so if you install Synchronet into a different directory you will need to either create a symbolic link in your root directory (e.g. ''/home/sbbs/sbbs'') or the system root directory (e.g.

Some common locations would be the ''home'' directory of the Run-as User (e.g. You must create the directory where Synchronet will live. If you find it necessary to start the BBS servers/services as root, then you can have the BBS daemon (sbbs) automatically change to the Run-as User after it has bound the necessary TCP and UDP faq:tcpip#ports, by setting the ''User'' value of the ']]'' section of the ']/ config:sbbs.ini'' file. Use "''adduser sbbs''" (or "''sudo adduser sbbs''" if necessary) to create the user account and "''su sbbs''" to switch to it: Running the BBS servers/services (''sbbs'') as the ''root'' user is not recommended. If you install with one user account and then later run with another (non-root) user account, you could encounter permissions errors.

It is recommended that you install Synchronet while logged-in with the user account that Synchronet will be run-as. sh/bash) to install and configure Synchronet. You will to use a *nix terminal and command shell (e.g.

You will likely need to build Synchronet from dev:source code for your Unix/Linux distribution, version, and platform architecture.īefore attempting to install/build Synchronet, insure that the install:nix:prerequisites are installed.

#Synchronet display menu screens password#

#Synchronet display menu screens install#

#Synchronet display menu screens code#