XM CORE: Update - we're online reddit / bbs ---------------------------------------------------------------------- denzuko · 2020-01-06 23:54 After a long battle with amazon, godaddy, and lastpass we're been able to recover our board and get back online. One still has access to the community grid and several retro mainframes from the doors menu and there is a tone of new message areas. Come check us out at https://bbs.dapla.net/ EDIT: Additional Details about our board are all over this subreddit - [http s://www.reddit.com/r/bbs/search/?q=xm%20core&restrict\_sr=1](https://w ww.reddit.com/r/bbs/search/?q=xm%20core&restrict_sr=1) ---------------------------------------------------------------------- spish · 2020-01-07 15:46 How do we access? ---------------------------------------------------------------------- CatOfTheDecade · 2020-01-07 17:18 Yeah, we kind of need an address there. ---------------------------------------------------------------------- denzuko · 2020-01-07 17:34 [https://bbs.dapla.net/](https://bbs.dapla.net/) ---------------------------------------------------------------------- denzuko · 2020-01-07 22:04 [http://bbs.guide/?post\_type=listing\_type&p=141311](http://bbs.guide /?post_type=listing_type&p=141311) ---------------------------------------------------------------------- mro_1337 · 2020-01-08 07:13 no connect ---------------------------------------------------------------------- [deleted] · 2020-01-08 19:17 [deleted] ---------------------------------------------------------------------- denzuko · 2020-01-08 23:34 and... denzuko@prlxjump:\~$ nmap -Pn -ptelnet,finger,smtp,binkp,uucp,nntp,ftp,http,https,ssh [bbs.dapla.net](https://bbs.dapla.net) ​ Starting Nmap 7.60 ( [https://nmap.org](https://nmap.org) ) at 2020-01-08 17:27 CST Nmap scan report for [bbs.dapla.net](https://bbs.dapla.net) ([52.90.75.190](https://52.90.75.190)) Host is up (0.032s latency). rDNS record for [52.90.75.190](https://52.90.75.190): [ec2-52-90-75- 190.compute-1.amazonaws.com](https://ec2-52-90-75-190.compute- 1.amazonaws.com) ​ PORT STATE SERVICE 21/tcp open ftp 22/tcp filtered ssh 23/tcp open telnet 25/tcp closed smtp 79/tcp filtered finger 80/tcp open http 119/tcp open nntp 443/tcp open https 540/tcp filtered uucp 2003/tcp filtered finger 8008/tcp filtered http 24554/tcp open binkp Lessons here, 1) mystic does not have a good support for init.d/systemd 2) amazon security groups appear to be mostly optimized for "common internet stack" usage (ie 'https/smtps/ssh/dns') and getting it do more generic takes a lot of retweaking.. 3) additional nodes are helpful. (Thanks /r/dallasmakerspace and Computer Committee). ---------------------------------------------------------------------- denzuko · 2020-01-08 23:39 As a backup one can also join the Zerotier network back pain by sending a request to cyberlord@1:124/5016.0 (FTN) via a PM in the BBS. ---------------------------------------------------------------------- denzuko · 2020-01-09 00:32 MS-DOS shell is operational, Looks like the upstream VAX machine is needing some repair. VAX access should be restored quicker than the board. ---------------------------------------------------------------------- [deleted] · 2020-01-11 00:13 Mystic _can_ have good systemd support. In fact I may just write up a github gist of my config and share it, because I think it’s pretty simple to get working well. ---------------------------------------------------------------------- denzuko · 2020-01-26 01:35 Found a blog where someone has made the scripts and systemd .service files. [https://vswitchzero.com/mystic- systemd/](https://vswitchzero.com/mystic-systemd/) ---------------------------------------------------------------------- [deleted] · 2020-01-26 01:43 Nice! I take a slightly different approach. I don’t like launching the daemon as root because it screws up some environment stuff. I’m not in front of my computer but what I do is launch it in a screen session so that I can reattach at any time and see what’s going on. Works well for me! ---------------------------------------------------------------------- denzuko · 2020-01-26 01:53 nice. good use of screen, nohup does the same mostly. But personally I've just used a crontab for the same bbs user that owns the directory. \`\`\` \\@reboot bash -c 'cd /mystic; rm semaphore/\*.lock; /mystic/mis daemon' That way I'm sure its started at reboot, cleans the locks and is executed as a non root server whom also has dialout group permissions. I do that since the files folder is also shared with uucp and gopher. ---------------------------------------------------------------------- denzuko · 2020-01-26 12:00 Secondary node is up for telnet, binkp, nntp, and pop3 only [p2.f5017. n124.z1.ddn.dapla.net](https://p2.f5017.n124.z1.ddn.dapla.net) ​ User database, files, messages, and menus are pending recovery from amazon.