|
|
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 OPENDARWIN
shell
shell(1F) FMLI Commands shell(1F) NAME
shell - run a command using shell SYNOPSIS
shell command [command] ... DESCRIPTION
The shell function concatenate its arguments, separating each by a space, and passes this string to the shell ($SHELL if set, otherwise /usr/bin/sh). EXAMPLES
Example 1: A sample output of shell command. Since the Form and Menu Language does not directly support background processing, the shell function can be used instead. `shell "build prog > /dev/null &"` If you want the user to continue to be able to interact with the application while the background job is running, the output of an exe- cutable run by shell in the background must be redirected: to a file if you want to save the output, or to /dev/null if you don't want to save it (or if there is no output), otherwise your application may appear to be hung until the background job finishes processing. shell can also be used to execute a command that has the same name as an FMLI built-in function. NOTES
The arguments to shell will be concatenate using spaces, which may or may not do what is expected. The variables set in local environments will not be expanded by the shell because "local" means "local to the current process." ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
sh(1), attributes(5) SunOS 5.10 5 Jul 1990 shell(1F)