A help system built into the terminal of *NIX systems that has a very specific format used to describe a command for the terminal or otherwise.
Description:
Believe it or not, you’ve been reading man pages here on this blog, since I started. Man pages were some of the first help files that you could get on any UNIX system, and has since been expanded to include other Non units systems. It has a very rigid format, and goes to some detail about all the options and other parameters that any terminal needs to run successfully. This is by far the hardest help system to use, with the Info files system and the TLDR system being easier to use for beginners.
A description of this blog and its conventions and guidelines.
DESCRIPTION:
Welcome to my blog.
I hope that you will follow to get (at least) thrice-weekly technology definitions. But to make things easier on those who read it, I have some housekeeping to share.
Starting with… tags!
The #mcctd series of tags are the organizer for this blog. I'm going to try and include at least three tags in each post—
The #mcctd tag
One or more category tag(s)
And #mcctd definitions
This way, if you're looking for a specific term, you don't have to wallow through them! I'll add them all to the bottom of this post.
Second… the format!
I love the format of MANPAGES— a very specific term that perhaps might be the second definition I make on this blog.
Definition posts consist of four things:
The date,
Title,
SYNOPSIS, and
DESCRIPTION.
The date is self-explanatory.
The title shows the term being described.
The synopsis describes the term in one sentence while the description fills it out. Ocassionly, I'll add in SEE ALSO and CITATIONS sections to clarify where I got my information. As you've seen, sometimes I'll use CAPS to highlight important words.
And finally, USER CONTRIBUTIONS!
ASKS
Asks should typically be (polite) questions, errors, or really just anything (that's not NSFW and not directly related to the content of the blof). The only two rules are
Kindness rules and
STAY SFW
Preferably use #mcctd ask so I can see it on my main blog as well.
Anything random should be in an ask, and not in a reply.
Treat replies and DMs as asks for the purpose of rules.
SUBMISSIONS
Please follow the rules in both ASKS and (as close as you can) the formatting description. I'd prefer you defining a specific term in your own words, if at all possible. Also, double check sources and spelling. If you aren't sure how to do font formatting, say so at the beginning of your post. Don't add a date; I'll take care of that for you :)
REPERCUSSIONS
Off-topic: 2x⚠ then 1strike
Improper submission/ask format: ⚠ then 1strike.
Spamming/submitting an repost (already defined): ⚠ then 1strike
NSFW: immediate BAN
With the exception of NSFW, you get 3 strikes. Once you have 3 strikes, you'll be muted.
WALL OF SHAME
This will be replaced with those who have worn the cone of shame by breaking the guidelines set above.
CURRENT CATEGORY TAGS
#mcctd housekeeping is the meta tag of this blog. I'll post updates using this tag.
#mcctd definitions general is for general topics.
#mcctd definitions *NIX is for definitions that is for the *NIX family of operating systems
#mcctd misprints is for goofs— posts intended for @maccorecrazy but ended up here.
DM or ask me with any submission categories.
That's it for now! As I expand this blog, I'll edit this post with more information!
#MCCTD Ep.1| Está no ar! Sejam bem vindos! Vídeos todos os dias do mês de junho! Inscreva-se! Beijos Redes Sociais: @mi_shirai instagram Twitter: @miceliblack Snapchat: mishirai facebook.com/MichelleBlackCanalYouTube miceliblack.tumblr.com E-mail: [email protected] Edição com Programa: iMovie '11
