Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Linux BBSing  <--  <--- Return to Home Page
   Networked Database  Linux BBSing   [161 / 189] RSS
 From   To   Subject   Date/Time 
Message   aaron thomas    All   Run a BBS on a Linux Server   July 3, 2019
 9:34 AM *  

I'm interested in running my Mystic (for linux) BBS on a Linux shared hosting
server.

I have limited knowledge of Linux though. How difficult would it be to upload
my BBS to the server, and have it start taking "calls?"

Does anyone already do this?

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
 * Origin: Alcoholiday / Est. 1995 / alco.bbs.io (1:123/525)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Linux BBSing  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0812 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_6b2t92vp8p1uis8j29i6s88q73, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_6b2t92vp8p1uis8j29i6s88q73, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_6b2t92vp8p1uis8j29i6s88q73, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0