>>3
LLLLLLLLLLLLEEEEEEEEEEEEEEELLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL
>I SO LAUGHED
>I HAD TO FUCK MYSELF WITH SOMETHIN G XDDDDLLLEEEEEEEEELLLLLLL
Because that page OP links to seems to have been lost to time, I produce a transcript, so that when this thread is bumped by spammers in the future young /prog/lodytes will not have to stretch themselves by spending 20s at a search engine.
The Unix Hierarchy (The Eight Stages of Unix Knowledge)
Name, description and features
beginner
insecure with the concept of a terminal
has yet to learn the basics of vi
has not figured out how to get a directory
still has trouble with typing [RETURN] after each line of input
novice
knows tha "ls" will produce a directory
uses the editor, but calls it "vye"
has heard of "C" but never used it
has had his first bad experience with rm
is wondering how to read his mail
is wondering why the person next to him seems to like Unix so very much.
user
uses vi and nroff, but inexpertly
has heard of regular expressions but never seen one.
has figured out that "-" precedes options
has attempted to write a C program and has decided to stick with pascal
is wondering how to move a directory
thinks that dbx is a brand of stereo component
knows how to read his mail and is wondering how to read the news
knowlegable user
uses nroff with no trouble, and is beginning to learn tbl and eqn
uses grep to search for fixed strings
has figured out that mv(1) will move directories
has learned that "help" doesn't help
somebody has shown him how to write C programs
once used sed to do some text substitution
has seen dbx used but does not use it himself
thinks that make is a only for wimps
expert
uses sed when necessary
uses macro"s in vi, uses ex when neccesary
posts news at every possible opportunity
write csh scripts occasionally
write C programs using vi and compiles with cc
has figured out what "&&" and "||" are for
thinks that human history started with "!h"
hacker
uses sed and awk with comfort
uses undocumented features of vi
write C code with "cat >" and compiles with "!cc"
uses adb because he doesn't trust source debuggers
can answer questions about the user environment
writes his own nroff macros to supplement std. ones
write scripts for Bourne shell (/bin/sh)
knows how to install bug fixes
guru
uses m4 and lex with comfort
writes assembly code with "cat >"
uses adb on the kernel while system is loaded
customizes utilities by patching the source
reads device driver source with his breakfast
can answer any unix question after a little thought
uses make for anything that requires two or more distinct commands to achieve
has learned how to breach security but no longer needs to try
wizard
writes device drivers with "cat >"
fixes bugs by patching the binaries
can answer any question before you ask
writes his own troff macro packages
is on firstname basis with Dennis, Bill, and Ken
>>14
This is bullshit, there are people who don't ever use the unix shell utilities but write awesome hacks. Only retards use cat to write text and whoever wrote the original text is some Unix fanboy with minimal knowledge of unix.
socat is more powerful. I also want to add:
ngrep, groff, watch, sort, head, tail, exp and ssh. Ssh has some awesome features too, especially if you work with multiple systems.
Name:
Anonymous2013-08-08 13:15
I liken starting one's computing career with Unix, say as an undergraduate, to being born in East Africa. It is intolerably hot, your body is covered with lice and flies, you are malnourished and you suffer from numerous curable diseases. But, as far as young East Africans can tell, this is simply the natural condition and they live within it. By the time they find out differently, it is too late. They already think that the writing of shell scripts is a natural act.