Thu Feb 18 2021 20:25:19 MST from ParanoidDelusions

I wish 

Vijaya Gadde
Had been born the second child, as a daughter, in China, when they had a 1 child policy. 

She's terrible and I don't understand how she passed high school with a brain that mushy

"Woman of color," but not *black* - who is good at sounding relatively intelligent, informed and articulate while actually saying nothing of any substance or meaning. 

Exactly the kind of person the Democrat Party wants. 

Thu Feb 18

 

She's terrible and I don't understand how she passed high school with a brain that mushy

In spirit. 

Tue Mar 23 2021 21:05:01 MST from eBear

Is this BBS located in Sacramento?

all of our bbs existed in spirit. Once upon a time sysops dreamed of exotic numbers like 212- 213- 301- 716- area codes but most of us (at least i think) worked at places like McDonalds and Blockbuster. I was fortunate to escape 80s parents and sell movie viewing via Blockbuster. So yes, it is a Sacramento BBS. It is my Philadelphia BBS too.

My BBS was pretty big at one point - in that I had a 140mb ESDI hard drive when 20mb drives were normal and 40mb drives were huge. 

So, I got a lot of traffic during that period. And I was part of the 916 room sharing network. So... I had messages from other local BBSes that you could just read there, if you wanted to. :) }

But in general - it was a pretty modest board. No multi-node, multi-user, nationwide network stuff. 

Discovering Citadel and becoming a sysop absolutely prepared me for a career in Information Technology as a system engineer. 

The software configuration of Citadel was so much like setting up an Xfree config file. Flat files with flags you either enabled or disabled. When I later got involved with Linux - it was always very nostalgic about setting up things on a Citadel BBS. 

I ran Cit on CP/M, Amiga, and PC (as well as on a C-128 for a brief moment). 

Sacramento had a particularly vibrant Citadel developer scene. We were one of the hub-regions where Citadel actually got written and distributed. 

Tue May 04 2021 00:20:04 MST from ASCII Express

It soundds pretty happening. I only ran one node also, and gradually upgraded my hard drive. I wish I would have discovered Citael earlier, but it just didn't happen that way. I always enjoyed the more message-centered software.

Well... I fixed the permissions issues with file uploads. I was hoping that would sort out the other issue with SSL/HTTPS... but no dice there. 

Something there is fubar AF. 

Ok. I'm not sure what was going wrong there - but for some reason Citadel was running multiple copies of webcit - I think on 443 - and this was causing all kinds of failures with "failure, unable to bind" error messages that were flooding my syslogs. I mean, it was happening every 3 seconds, with a ton of logging, all day and all night. It didn't appear to be taxing the resources - but it just didn't seem like a good situation. I also didn't like the idea of it trying to start a service, failing, logging it, and retrying it, with all the writes to the SSD that was incurring. 

Anyhow... there was a permissions issue when I copied the production from bare metal over to the VM and then installed Citadel. I corrected the permissions issue - that was also causing an inability to upload files in the directory rooms - and then I simply did the easy-install over the currently installed version. I tested on my testVM first - and it worked there - so... I did a backup, AND a checkpoint, and then did it here - and things look good so far. The error messages in the log are just back to the standard, occasional SSL_accept failed: sslv3 alert certificate unknown and errval=6 errors that I think are due to unsigned certs. 

But the syslog from webcit is WAY less chatty - and I am totally relieved. 

I did manage to get the dotskip to work when logging in on HTTP on port 8916 to redirect to "hello" - but it is still not working with HTTPS on 443. 

I think I'm going to just live with that for now - as I think that is how this got so effed up in the first place.

Well... I did it to myself - I kinda figured it wasn't going to work right when I migrated from bare metal to a VM - and knew permissions was the thing I didn't remember how I set up or how to recreate, and I was right. 

Then things broke, and I forgot about that, and looked for OTHER reasons for a while before I discovered the permissions thing by accident. I'm glad I tried to upload those files and couldn't and that got me pointed in the right direction for ALL the problems I was experiencing. 
A huge part of the problem is that Citadel and Linux don't explain the problems very well. The logs never really said "The problem is that I can't access files I need to access to work right." 

Instead they were saying, "these things that I need aren't where they should be..." even though they were. I see how that works... but the error messages probably *could* have told me, "permission denied". 

Anyhow... then on top of that - I have to research all these obscure linux commands every time I need to troubleshoot. So I end up spending as much time reading online - and a lot of information is outdated, incorrect, or leads to having to read me... 


"Use netstat!" 

But, the document assumes you have netstat installed and know how to use it. IF you need to tell me that I need to use Netstat, you should assume I may need to know what package Netstat is installed with. 

Hey, I remember this file!  To bad the latest version of the source code for Asgard-86 was lost.  But the source code and runtime from a few revisions back is still available.  I think 1.49e is what was uploaded here, but the latest was 1.49q (I think), or 1.49g.  I cannot remember exactly.

Wed May 05 2021 03:09:42 PM MST from ParanoidDelusions <>

NEW UPLOAD: 'asgard86.intro.txt'
Asgard 86 Readme text application/octet-stream

If you or your brother have any files from back then, feel free to upload them here. 

I'm scheming at opening Asgard-86 as a door, somehow - maybe in a DosBox running as a virtual machine accessible through a wiki-page. 

Thu May 06 2021 18:36:49 MST from Otto Roboto <otto_roboto@wallofhate.com>

Hey, I remember this file!  To bad the latest version of the source code for Asgard-86 was lost.  But the source code and runtime from a few revisions back is still available.  I think 1.49e is what was uploaded here, but the latest was 1.49q (I think), or 1.49g.  I cannot remember exactly.

Wed May 05 2021 03:09:42 PM MST from ParanoidDelusions <>

NEW UPLOAD: 'asgard86.intro.txt'
Asgard 86 Readme text application/octet-stream