Learn How UNIX Multitasks 160
BlueVoodoo writes "On UNIX systems, each system and end-user task is contained within a process. Learn how to control processes and use a number of commands to peer into your system."
This discussion has been archived.
No new comments can be posted.
Learn How UNIX Multitasks
Related Links Top of the: day, week, month.
An authority is a person who can tell you more about something than you really care to know.
Re:exciting (Score:5, Interesting)
Intermediate level too! (Score:1, Interesting)
Specialized tools? Everybody uses these all the time, and I note he didn't mention nice or renice - the ones nobody ever uses. This is not intermediate level stuff, this is beginner stuff. Awk, M4 and sed are intermediate - and they aren't specialized tools either.
No, psDoom is more interactive: Re:Lavaps (Score:3, Interesting)
http://psdoom.sourceforge.net/ [sourceforge.net]
Re:Use the Firehose! (Score:4, Interesting)
Yes this is Basic Unix Command Line suff. But a lot of Unix users don't go beyond typing the command to run the program. Forking, Piping, Scripting, is more then what they really use. An some of the times these people who don't understand this are actually smarter then most of us. Say a Physicist who uses Unix to test their math or run complex simulations. Also there are a lot of people using Linux/Unix who were never formally taught how to use it. So they stick in the GUI, or Find and install programs that a simple small script can acomplish. I know you want to do your "I am an Alpha Geek" while thumping your chest. But if an article gets posted and you really don't care, then don't read it and move along. Because getting an article on information that you already know isn't a big deal, this is far more mature then say the latest Cool PC Mods.
Re:How to learn unix... (Score:2, Interesting)
Re:Use the Firehose! (Score:1, Interesting)
(Myself, I know it all, but not everyone does)
Re:How to learn unix... (Score:2, Interesting)
Re:What the flying f*ck? (Score:3, Interesting)
If you hire someone who is supposed to be working with Windows/*NIX interoperability and hadn't a clue how UNIX works, then you have a problem and, yes, the new guy is illiterate for the task he is given. If you hire a developer to make a
I am more demanding than this on developers and techs. I don't care if the project is 100% MS and
I have worked with many projects like ASP and
Another problem with such closed knowledge is even in little things, like in the example of Web development. I 'inherited' a tech that was supposed to be a great Web developer(MS tools), and when parts of the project were moved to Linux servers, the person literally did not understand why upper & lower case mixed reference tags were failing. And as scary as that sounds it very common.
But this is just like my personal stand on people in the OSS *nix world that have fallen so far away from MS that they fail to understand the newer MS OSes and what things are done right in the NT architecture that *nix has never done very well at. Techs will mislead clients because they don't understand 'easier' concepts that other people are using that came from the MS world even though they could be implemented on *nix.
This is also especially true for OSS *nix developers, if they don't know what else is out there, they could be recreating wheels that companies like MS, Sun, etc have already solved. And sadly I find this a lot even in some very well known and good OSS projects. There is something to be said for learning from your competition or people that have gone before you.
Maybe it is more like the difference between knowledge and understanding.
slownewsday tag (Score:3, Interesting)