Browse Source

new repo

cmccabe 1 year ago
3 changed files with 186 additions and 0 deletions
  1. +11
  2. +134
  3. +41

+ 11
- 0
man-page-how-to.txt View File

@ -0,0 +1,11 @@
Arch man pages kept here:
After formatting your man page document, gzip it with a -k to keep the original. E.g.
gzip -k shlog.5
Then, put shlog.5.gz in the corresponding man directory. shlog is in 5, is in 7. Normal users, just ask the admin to do this step.
~!! make sure you 'sudo cp' it and not 'sudo mv' it because the latter will not change ownership to root.
Google search for "how to create a man page" for formatting instructions. Pages like:

+ 134
- 0 View File

@ -0,0 +1,134 @@
.TH 7 "19 Apr 2019" "version 0.01"
.SH NAME (RTC) - the "slow" social network.
The (RTC) is an experimental public access GNU/Linux system for socializing, digital skill building, and collaboration through the medium of the GNU/Linux shell. RTC is not only an experiment in pubnix technology, it is an experiment in community.
Note that RTC is a heavily asynchronous social environment -- that is, you may see communications that others have left even while you were offline. You can leave notes, shlog posts, emails, chat messages, etc. for others in the same way. There are synchronous (real-time) social tools too, of course, but especially as the userbase is small, asynchronous interactions are common.
Check back to this man page periodically. This will be maintained as a living document, with information about technical and policy changes to the system.
The big experiment of the RTC is that it is user driven. You might think of RTC as the DIY social network. Many of the tools here were written by the members themselves. The RTC started as a stock Debian image in 2018, shifting to Arch in 2019, and is gradually accumulating homegrown software and system config tweaks based on member contributions.
.B Shell Blogs (shlogs)
(check the man page for 'shlog' for more info)
- a internal shell blogging (shlogging?) platform in the simplest form we could come up with.
- try out 'shlog' by ~papa, 'shlogit' by ~trnslts or 'shlogdown' by ~wangofett
.B party
- a classic shell-based chat program dating back to the origins of public access Unix systems. Run 'man party' for more information, or just 'party' to join the chat. party is asynchronous in the sense that you can view previous comments that were submitted even while you were offline. [Note that party is temporarily offline.]
.B gab
- a minimalistic, asynchronous chat program written by RTC user sloum. Run 'gab -h' to learn how to use it. And try 'partyfett' as well, the great real-time shell on top of 'gab'.
.B linkulator
- a minimalistic shell-based link aggregator, by cmccabe, asdf and sloum. Currently in beta.
.B talk
- a GNU-licensed synchronous chat program, for chatting with one or more other users.
.B write
- send messages to other users.
.B gophernicus
- the gopher server. Start your own gopher hole in your public_gopher directory.
.B mutt for email.
.B sl
- like the old UNIX 'steam locomotive' prank. Type 'sl -h' to learn how you can contribute to the hijinks.
.B train
- also like the old UNIX 'steam locomotive' prank, but this one is an actual train. Type 'train -h' to see how you can add your own boxcar to the train.
.B various text editors
; let the admin know if you have a favorite lightweight editor that is missing.
.B various compilers and scripting languages
; again, let the admin know if your favorite lightweight tool is missing.
And many more. If you don't find something that *should* be here, just ask.
Accounts on are free and available for people who are attracted by the system's values and culture.
Accounts with an extended period of inactivity (think months) will be removed. This is not without exception though. Simply make a request to the admin if you need an exception.
Some system services are restricted to users who demonstrate active involvement in the goals of this system. These include cron and systemd linger which are limited to local community-oriented purposes or for special projects on request.
Sorry be so uptight and have "policies", but a few past users have abused the system, and I now see it is easier to make it clear up front what is acceptable use and what is not.
Any violation of these policies is grounds for immediate account termination with no warning and no questions asked. Sorry, this is a small server with a trusting community of users, and it's far too easy for one abusive user to ruin it for everyone.
Harrassment of any form is not tolerated, including of other users or people outside the system.
Do not use this system to host relay services of any type (IRC bouncers, web scrapers, etc.). If you're only here for free cpu cycles or storage, you're in the wrong place.
Don't use this system to hack or disrupt other devices on the internet. Don't do this ever.
Do not do anything that could result in legal trouble for RTC or trouble from our ISP.
Keep system resource usage to a minimum. This includes network, disk space, and CPU. Learn how to monitor these metrics. Keep in mind, one of the goals of the RTC is to demonstrate how much can be accomplished with GNU/Linux using a very tiny server.
Don't hack the box! Well actually, you can hack the box, but only if (1) you ask for and receive permission from the sysadmin, (2) you agree to use the results of your quest to fix problems or improve the system, and (3) your activities do not damage the system or undermine the privacy or security of other users.
If you observe anyone violating these policies, politely refer them to this man page. If that does not work, notify the sysadmin.
Set up an internal shell blog with 'shlog'. For info, see ~cmccabe/.shlog/2019-04-26-begin-shlog.txt
Collaborate on software development projects with git. Please feel encouraged to develop software for use by the community on this system, or on other pubnixes!
Asynchronously chat with other users using 'gab' or 'partyfett', or chat synchronously with 'talk'.
Let everyone know what you're up to with your uber-simple/micro status page in your .plan or .project files. Use 'pinky -l cmccabe' to see an example of the output.
Send email from with mutt or mail.
Set up a webpage in ~/public_html Please keep your pages to plain text, and don't attract internet hugs of death. :)
Set up your public gopher phlog in ~/public_gopher
If anything isn't working, see AUTHOR below.
Contact cmccabe with any questions, comments or smart remarks. Catch him online on the RTC or email to
The RTC is just one pubnix among many. Others include:
And many more...

+ 41
- 0
shlog.5 View File

@ -0,0 +1,41 @@
.TH shlog 5 "19 Apr 2019" "version 0.01"
shlog - the shell blog
mkdir ~/.shlog
touch ~/.shlog/yyyy-mm-dd-first-shlog-post.txt
chmod -R 755 ~/.shlog/
'shlog' is the's (RTC) internal blog platform. Really it is just a file structure and naming convention that provides consistency to internal-only, shell-based blogging so that users can publish posts and other users can browse them.
Create a '.shlog' directory in the top of your home directory. Make sure it is readable by other users.
In that '.shlog' directory, simply use your favorite text editor to create posts.
Name your posts according to this filename convention: yyyy-mm-dd-post-name.txt
Make sure your posts are readable by other users. And you're shlogging!
shlog posts are intended to be privately accessible ONLY to RTC users. You may do as you wish with your own content, of course, but please DO NOT make content from other users' shlogs accessible outside of RTC.
See '~papa/share/bin/shlog -h' for an in-development shlog browser/roller.
You also have ~public_gopher and ~public_html directories for publishing internet-wide publicly viewable phlogs and blogs