|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Sink or Swim
Post 309 by Neo on Tuesday 21st of November 2000 05:24:35 PM
11-21-2000
Administrator
The paraphrase or interpretation of our posts to the tune "trial-by-fire" and "sink-or-swim" is somewhat misleading, but interesting 
Throughout all the posts, the advice has been to get the foundation texts (and the references are provided below),
build your own UNIX system(s) and learn step-by-step. As PxT says, the limiting factor is your own personal motivation to learn.
If you have not bought the texts, built your own systems, learned to code, or learned the basics of the UNIX operating system (or plan to before moving into the UNIX field) I suggest that seeking a UNIX job is not for you.
UNIX is a vast field which requires a great amount of personal motivation, late night wrangling, reading, and hands on practice. There is no trial-by-fire or sink-or-swim. If you follow the suggested path, you will be an expert. There are no shortcuts to learning a powerful infrastructure such as UNIX, network programming, C or C++, shell programming, etc. These are skills which are acquired by fire, not tried by fire. First, you must acquire the skills.
One analogy is martial arts training. At a good school, two years of training gives a black belt. The black belt is a symbol of learning the basics; not of finality. The black belt signifies some (small degree) of acquired knowledge. A yellow belt who gets into the ring with a 'second degree black belt' is a fool and no 'real' black belt would allow that to happen.
UNIX is very similar. Only a foolish novice tries to pass themselves off a black belt and get into a job which requires advanced "black belt" UNIX skills. There is no sink-or-swim and no trial-by-fire. There is only hard work, patience, practice and more hard work. If you follow the advice in the threads on which books to study and build you own systems, you will progress. There are no shortcuts to becoming a UNIX master just like there are no shortcuts to becoming a master of any other discipline.
My sincere apologies if this post is too direct and has an impatient tone. That is not my intent. It is difficult, for me, to explain to someone that there are no shortcuts in life and we are only limited by the barriers that we create as individuals. One does not 'jump to UNIX', one 'becomes familiar with the UNIX operating system and environment'. Just like golf, you don't just go out, buy clubs, shoes and balls and then play par golf. There is no 'sink or swim' in golf, you practice, learn to play, progress, and practice more. It's just Zen, really, and in this context, Zen means 'understanding things for what they actually are, not what we want them to be'.
[Edited by Neo on 11-21-2000 at 11:15 PM]
Throughout all the posts, the advice has been to get the foundation texts (and the references are provided below),Quote:
If you have not bought the texts, built your own systems, learned to code, or learned the basics of the UNIX operating system (or plan to before moving into the UNIX field) I suggest that seeking a UNIX job is not for you.
UNIX is a vast field which requires a great amount of personal motivation, late night wrangling, reading, and hands on practice. There is no trial-by-fire or sink-or-swim. If you follow the suggested path, you will be an expert. There are no shortcuts to learning a powerful infrastructure such as UNIX, network programming, C or C++, shell programming, etc. These are skills which are acquired by fire, not tried by fire. First, you must acquire the skills.
One analogy is martial arts training. At a good school, two years of training gives a black belt. The black belt is a symbol of learning the basics; not of finality. The black belt signifies some (small degree) of acquired knowledge. A yellow belt who gets into the ring with a 'second degree black belt' is a fool and no 'real' black belt would allow that to happen.
UNIX is very similar. Only a foolish novice tries to pass themselves off a black belt and get into a job which requires advanced "black belt" UNIX skills. There is no sink-or-swim and no trial-by-fire. There is only hard work, patience, practice and more hard work. If you follow the advice in the threads on which books to study and build you own systems, you will progress. There are no shortcuts to becoming a UNIX master just like there are no shortcuts to becoming a master of any other discipline.
My sincere apologies if this post is too direct and has an impatient tone. That is not my intent. It is difficult, for me, to explain to someone that there are no shortcuts in life and we are only limited by the barriers that we create as individuals. One does not 'jump to UNIX', one 'becomes familiar with the UNIX operating system and environment'. Just like golf, you don't just go out, buy clubs, shoes and balls and then play par golf. There is no 'sink or swim' in golf, you practice, learn to play, progress, and practice more. It's just Zen, really, and in this context, Zen means 'understanding things for what they actually are, not what we want them to be'.
[Edited by Neo on 11-21-2000 at 11:15 PM]
|
|
We Also Found This Discussion For You
1. Solaris
I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies
LEARN ABOUT HPUX
sh
sh(1) General Commands Manual sh(1) NAME
sh - overview of various system shells SYNOPSIS
POSIX Shell option] ... string] [arg ...] option] ... string] [arg ...] Korn Shell option] ... string] [arg ...] option] ... string] [arg ...] C Shell [command_file] [argument_list ...] Key Shell DESCRIPTION
Remarks The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line. However, the command has historically been associated with the conventional Bourne shell, which could confuse some users. To meet stan- dards requirements and also clarify the relationships of the various shells and where they reside on the system, this entry provides com- mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in greater detail. The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5. Please use the POSIX shell as an alternative. Shell Descriptions The HP-UX operating system supports the following shells: POSIX-conforming command programming language and command interpreter residing in file Can execute commands read from a terminal or a file. This shell conforms to current POSIX standards in effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects. Similar in many respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various other useful features. Korn-shell command programming language and commands interpreter residing in file Can execute commands read from a terminal or a file. This shell, like the POSIX shell, contains a his- tory mechanism, supports job control, and provides various other useful features. A command language interpreter that incorporates a command history buffer, C-language-like syntax, and job control facilities. Restricted version of the POSIX shell command interpreter. Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user shells. restricted version of the Korn-shell command interpreter Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user shells. An extension of the standard Korn Shell that uses hierarchical softkey menus and context-sensitive help. +--------------+--------------------+ | To obtain: | Use the command: | +--------------+--------------------+ | POSIX Shell | /usr/bin/sh ... | | Korn Shell | /usr/bin/ksh ... | | C Shell | /usr/bin/csh ... | | Key Shell | /usr/bin/keysh | +--------------+--------------------+ These shells can also be the default invocation, depending on the entry in the file. See also chsh(1). WARNINGS
Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref- erence to ``see sh(1)''. SEE ALSO
For more information on the various individual shells, see: keysh(1) Key Shell description. ksh(1) Korn Shell description. sh-posix(1) POSIX Shell description. csh(1) C Shell description. sh(1)