What is Digg?Related by Keyword 
How are these related stories? Tell us!
- schestowitz, on 10/10/2007, -11/+4This a Windows-oriented guide for people who haven't explored *unix before. Maybe preaching to the choir when filed under "Linux/Unix"? In the sense that this assumes the reader only uses Windows...?
Still, great guide. Nice images to illustrate things.- bruenig, on 10/10/2007, -0/+5Probably just weighing the odds of getting it to the front page. Put it in the linux section and they will digg it, the windows and they won't.
- voyvf, on 10/10/2007, -0/+7actually, it makes sense for it to be under "Linux/Unix" - i mean, if you were searching the site for beginner's level information on the linux command line, would you search under "Windows" ?
it is a nice guide - X isn't always available, after all.- tech42er, on 10/10/2007, -0/+3And X isn't always the best way to accomplish a task.
- The_Pope, on 10/10/2007, -1/+9I found it a good read too, since I am one of schestowitz's Windows-y people who hasn't explored Linux before
- ScornForSega, on 10/10/2007, -2/+5I know my way around the command line a bit and it was still helpful.
No more ps -e > file.txt then Kill pid
htop seems to work pretty well.- bruenig, on 10/10/2007, -0/+10killall processname works. Or if you need the pid, you can just ps -e and grep for it, don't know why you would be redirecting to a file in any sense.
- liquidjamm, on 10/10/2007, -0/+1illustration: ps -ef | grep (any_string)
- tech42er, on 10/10/2007, -0/+1Is it possible to pipe that into kill? I've tried, but kill won't take a line from ps -ef filtered through grep as input. It won't even accept a PID as input. IT has to be given as an argument, not input. God, that's annoying.
- trogdoor, on 10/10/2007, -0/+2pgrep
( and pkill for non Linux *NIX systems, DO NOT try to use killall in Solaris :)
- liquidjamm, on 10/10/2007, -0/+1illustration: ps -ef | grep (any_string)
- voyvf, on 10/10/2007, -1/+4killall *processname* works nice, too. crap, ubuntu even lets you use command-line completion with it. :D
- init100, on 10/10/2007, -0/+4He didn't even mention one of the most useful tools, namely I/O redirection (to/from file/pipe).
- yvovandoorn, on 10/10/2007, -0/+1You can also do "kill -9 `ps aux | grep -i appname | awk '{ print $2 }' `"
- Philluminati, on 10/10/2007, -0/+1dude...if you pipe it to a file because it's filling the screen you could browse it one screen at a time using more
ps -auxf | more
that way you don't need the file
- bruenig, on 10/10/2007, -0/+10killall processname works. Or if you need the pid, you can just ps -e and grep for it, don't know why you would be redirecting to a file in any sense.
- zerodaysoon, on 10/10/2007, -0/+2sweet!! very useful for noobz like me
- GaryS278, on 10/10/2007, -0/+8sometimes it's just best to experience the command line and figure out stuff on your own.
- tech42er, on 10/10/2007, -0/+1So long as you're not root. But, really, the commands are not instinctive; you need to learn what they are, then read the man pages, and then play around.
- Philluminati, on 10/10/2007, -0/+1I'd say it's okay to do it as root. I mean you need to learn useradd, apt-get, yum etc which you can only do as root. Just don't execute random commands from /usr/bin and don;t do it on your only machine.
- tech42er, on 10/10/2007, -0/+1So long as you're not root. But, really, the commands are not instinctive; you need to learn what they are, then read the man pages, and then play around.
- db113456, on 10/10/2007, -0/+6Knoppix is also a good live cd/dvd to give Linux a good whirl.
http://www.knopper.net/knoppix-mirrors/index-en.html
I would go for the dvd, it has a lot more fun :-) - apologeticus, on 10/10/2007, -7/+3Nice list, but it still doesn't make me want to explore Linux. Having to learn all that command line syntax is the very thing that keeps me away from Linux. Of course, with OS X I have all of the advantages of Linux w/out the command line headaches, so why bother? Now if someone (I'm looking at you, Google) could come out with a Linux distro with a really nice GUI so we don't have to mess with the command line if we don't want to, THEN you'd see Linux use take off.
- jeffeb3, on 10/10/2007, -0/+10you should try the post 2002 versions they all have UIs
- apologeticus, on 10/10/2007, -4/+1I have. I looked at installing Ubuntu on my Macbook a while back and the amount of command line entries necessary to do so was staggering. It's easier to install Windoze on my Macbook than it is to install Linux.
- Weebs43, on 10/10/2007, -2/+1What did you really have to learn to do besides "apt-get" and the occasional compiling from source? I personally find Ubuntu to suit my needs and be simpler to me. Then again, I've always been one to prefer complete control and text-based things rather than UI based.
- trogdoor, on 10/10/2007, -0/+1Intel Macs aren't exactly known for their Linux compatibility ( in fact Apple is pretty well known for making closed, proprietary hardware ).
- apologeticus, on 10/10/2007, -4/+1I have. I looked at installing Ubuntu on my Macbook a while back and the amount of command line entries necessary to do so was staggering. It's easier to install Windoze on my Macbook than it is to install Linux.
- jeffeb3, on 10/10/2007, -0/+10you should try the post 2002 versions they all have UIs
- dougle, on 10/10/2007, -0/+2i would have said poking around in the partition editor should not be in the first half of a linux tutorial. "First we'll learn how to ride your motorbike really fast, then next lesson we'll learn about the brakes"
- ascii63, on 10/10/2007, -1/+1Uh, you have to partition your disks with windows just the same. The partition editor just has a slightly different user interface. Beyond that, If you can't successfully partition a disk, you might want to trade your computer for a speak-and-spell. It really isn't that difficult.
- daverave999, on 10/10/2007, -0/+1No, you don't. I bet at least 90% of Windows users just use a single partition and always will.
Though I agree that partitioning might not be the best 'beginner' CLI subject.
- daverave999, on 10/10/2007, -0/+1No, you don't. I bet at least 90% of Windows users just use a single partition and always will.
- Philluminati, on 10/10/2007, -0/+1I agree. Any "tutorial" on Linux for beginners shouldn't direct them into cfdisk so soon. There's a danger they might format a disk without realising it.
- ascii63, on 10/10/2007, -1/+1Uh, you have to partition your disks with windows just the same. The partition editor just has a slightly different user interface. Beyond that, If you can't successfully partition a disk, you might want to trade your computer for a speak-and-spell. It really isn't that difficult.
- animus, on 10/10/2007, -8/+0welcome to 1988 linuxfags
- Glider3, on 10/10/2007, -1/+0Oh, that was use full...
- pbgswd, on 10/10/2007, -0/+6Back in the day, they taught dos and assembly in high school it didnt freak people out, it was just the way it was. Y'all are hereby ordered to grow a pair and learn how to use the cli. For those who like wearing adult diapers, ubuntu has a number of graphical interface tools for managing software and files. Now stop whining you milquetoast desktop users! You dont know half of your computer if you dont know this!
- digitallysick, on 10/10/2007, -0/+1I'm confused, why are they running it in vmware for?
- johnstar, on 10/10/2007, -0/+3nano is your friend when X won't play nice!
- tech42er, on 10/10/2007, -0/+1Yup. It took me forever to understand how to save, though. Who thinks 'write Out' means 'save'?
- yvovandoorn, on 10/10/2007, -0/+4But vim is even more of your friend if you gave it a chance
- gazzerh, on 10/10/2007, -0/+1I agree. vi is your friend. It's installed on (almost?) every install of Unix/linux. So it's recommended you learn how to use it.
- jooo, on 10/10/2007, -0/+0very nice :)
I need to teach some newbies linux and i wanted something just like that to help me get started with them :) - gazzerh, on 10/10/2007, -0/+1I can't remember the last time i used rmdir. I always use rm -r (well actually rm -rf but i'm just asking for trouble) ;)
- foxhoundadmin, on 10/10/2007, -0/+1CHRIST! O.o
you can tell a bunch of nerds with messed up logic created unix (same goes for dos/windows). if i made an os, then i'd make LOGICAL, easy-to-remember commands. to display a file(s) contents in unix the command is "cat;" in dos it's "type." "cat.." "TYPE!!" WTF!? why not just type "file" like we do with "dir" (for directory) in dos? also, to change a file(s) permissions in unix the command is "chmod;" in dos it's "attrib." going with the whole unix, two-letter-command scheme (such as "cp," "mv," "rm," etc. (that's not a command, obviously), i'd make it "cm," but that's also what i'd use to compare file(s)... so, i'd probably just revert to the whole dos, easIER-to-remember-yet-schemeless-design... scheme and make it "mode." a few more things, why is "print" "lp" in unix? why not "print" or just "pr" (going with the whole two-letter scheme again); and why is there no "rename" in unix? how does "move" ("mv") suffice!?
i guess what i'm trying to say is command lines are pretty much useless now (unless you've already LEARNED the commands, of course; but that's the problem--you shouldn't have to LEARN them, per se--they should be easy to remember so that you see them once and say, "hey, that makes sense!" not, 'cat...' 'chmod...' WTF does that mean!?"). i mean, can't they just follow one, simple scheme!? cheese and rice!!- johnnykwest, on 10/10/2007, -0/+1I'm not so sure you would make it logical. The unix commands cp, mv, rm, ls, cat etc. are based on verbs. They are commands and are used to perform operations and therefore it makes complete sense. On the other hand, using dir, or heaven forbid 'file' for a command name makes no logical sense at all.
And I could be wrong, but I think lp stood for 'line printer' back in the day. You must realize that these commands were developed 30+ years ago, no?
Also, with mv (move) you don't need a rename command. Move suffices perfectly well. You move filename1.txt to filename2.txt and you've effectively renamed it. Explain to me what the difference is.
The command line is very powerful. And for with the amount of options and switches available for most commands, I'm quite grateful they kept the commands (and the file system tree directory names) short - it saves significant typing.
ANY system that is complex and powerful requires some kind of learning curve for the user. I don't care if it's GUI or CLI, Linux,Windows or OS-X, the learning curve is always there for some people. - Acolyte357, on 10/10/2007, -0/+1Based on the simpleminded outlook in your post, I doubt you will ever offer usable input for creating an OS let alone make one yourself.
to display a file you CAN use "cat" (which stands for catenate) or you could use "more" (which is the same as dos), "less", ect..
and OMG "dir" works in a linux CLI!
- johnnykwest, on 10/10/2007, -0/+1I'm not so sure you would make it logical. The unix commands cp, mv, rm, ls, cat etc. are based on verbs. They are commands and are used to perform operations and therefore it makes complete sense. On the other hand, using dir, or heaven forbid 'file' for a command name makes no logical sense at all.
Browsing Digg on your phone just got easier with our enhancements to the 
© Digg Inc. 2009 — Content posted by Digg users is