Earlier quoted context omitted.
Unless someone 'fessed up to it, you really have no way of knowing who did this. It could just as easily have been a drive-by script. And regardless, it was a hard, cheap, early lesson in the importance of ensuring fundamental levels of system security. I've ... suffered worse. I strongly suspect you'll never forget this.
This being more than a decade and a half ago, I doubt it was a drive-by script. I was dialed into AOL on a 4 letter screen name. I had just informed a channel of Linux users, who knew my public IP, that I had just installed Linux for the first time. The chances it wasn't someone from that IRC channel are near zero.
The Command Line Crash Course Controlling Your Computer From The Terminal
51–60 of 91 posts
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#52Earlier quoted context omitted.
Then why work through the examples? The "learn by rote" method he's using here is designed to help people with little or no experience catch up quickly, and remember what they've learned without the many years of daily use. If you just want to learn the odd helpful new trick, and basically know what you're doing, just ignore these parts.
That is just one example of the tone of this book, and I just don't like it, and I don't understand why it has so many supposedly adult people accepting things like: > No, seriously, type it 20 times and say it out loud. Sssh. Just do it. I supposed it was a kind of cold joke but it appears not to be. It is just very disrespectful for the reader. Grown up human beings are not to be taken by the hand like /this/ to le…
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#53Earlier quoted context omitted.
This being more than a decade and a half ago, I doubt it was a drive-by script. I was dialed into AOL on a 4 letter screen name. I had just informed a channel of Linux users, who knew my public IP, that I had just installed Linux for the first time. The chances it wasn't someone from that IRC channel are near zero.
stop crying
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#54File and directory names can contain spaces and require special treatment. This should be addressed up front, before introducing commands with side effects.
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#55Am I just a cranky old geek or does anyone else find Zed teaching CLI skills mildly amusing? Or is there truly a large population mentally bound by the graphical interface? Know the basic commands of getting things done isn't just for the experienced admins/developers like myself who have been using keyboards and terminals since the early DOS and VMS days. Ordinary users were able to create documents, check mail and…
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#56On page 3, about "whoami" > type this command 20 times and say it out loud I have many years of daily command line use behind me and never needed to use this command. I don't like being taken for a child.
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#57On page 3, about "whoami" > type this command 20 times and say it out loud I have many years of daily command line use behind me and never needed to use this command. I don't like being taken for a child.
I agree. The tone is not for me and it sounds really put on. "The only piece of advice I am going to give you is this: Shut the hell up and type this in then try to understand it. Sorry to be mean, but that's what you have to do. You have an irrational fear of the command line and the only way to conquer an irrational fear is to just shut up and fight through it." Why say "shut the hell up"? Why assume that the reade…
As for why I wrote it: You may not have an irrational fear but a huge number of Windows and OSX users do. They've been told that the CLI is dangerous and antiquated so they avoid it and panic over it. Having someone like me just push them through actually gets them past that and on to learning how to use it.
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#58I know the OP is not the author, Zed Shaw, but I simply wanted to say Thanks to Zed for this.
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#59I got 1 upvote for anyone that can provide me a pdf of this thing.
But, PLEASE, do not pass the PDF around to newbies until I say it's ready. Having old versions with potential errors floating around or that are half-done is really bad for them.
Re: The Command Line Crash Course Controlling Your Computer From The Terminal
#60Earlier quoted context omitted.
Your characterization of both is wrong.
Pray explain a bit in which ways my characterization of both is wrong. (As any short description, my "portrait" maybe a bit of a caricature but I believe it expresses the meaning well enough.)
1. All geeks learned the command line at some point. Even Linus. Calling the next Linux a "wannabee geek" is wrong.
2. basic training is for all soldiers, not just infantry soldiers. You choose infantry for the baggage it carried, and you didn't care that you were flat wrong.
3. I find your use of "pavlovian reflex" wrong. It has a negative connotation, but is all reflexive action "pavlovian". If so, all of my command line use is pavlovian because I do it reflexively without conscious thought. With that in mind, the military style is perfect because it's designed to train people to do things reflexively when the time comes.
4. basic training teaches many great things. You're dismissal of it as teaching people to "run below a shower of bombs" is wrong. I learned CPR amongst many other good things in basic. Things that again require one to do them almost reflexively, just like I use the command line.
In short, you are wrong.