|
|
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 MOJAVE
net::server::proto::unix5.18
Net::Server::Proto::UNIX(3) User Contributed Perl Documentation Net::Server::Proto::UNIX(3) NAME
Net::Server::Proto::UNIX - Net::Server UNIX protocol. SYNOPSIS
See Net::Server::Proto. DESCRIPTION
Protocol module for Net::Server. This module implements the UNIX SOCK_STREAM socket type. See Net::Server::Proto. Any sockets created during startup will be chown'ed to the user and group specified in the starup arguments. PARAMETERS
The following paramaters may be specified in addition to normal command line parameters for a Net::Server. See Net::Server for more information on reading arguments. unix_type Can be either SOCK_STREAM or SOCK_DGRAM (default is SOCK_STREAM). This can also be passed on the port line (see Net::Server::Proto). However, this method is deprecated. If you want SOCK_STREAM - just use proto UNIX without any other arguments. If you'd like SOCK_DGRAM, use the new proto UNIXDGRAM. METHODS
NS_unix_path/NS_unix_type In addition to the standard NS_ methods of Net::Server::Proto classes, the UNIX types also have legacy calls to NS_unix_path and NS_unix_type. Since version 2.000, NS_unix_path is simply an alias to NS_port. NS_unix_type is now redundant with NS_proto. These methods were missing between version 2.000 and 2.003 but have been returned as legacy bridges. QUICK PARAMETER LIST
Key Value Default # deprecated UNIX socket parameters unix_type (SOCK_STREAM|SOCK_DGRAM) SOCK_STREAM port "filename" undef # more recent usage port "filename / UNIX" port "filename / UNIXDGRAM" LICENCE
Distributed under the same terms as Net::Server perl v5.18.2 2012-06-06 Net::Server::Proto::UNIX(3)