|
|
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 DEBIAN
tm::resourceable
TM::ResourceAble(3pm) User Contributed Perl Documentation TM::ResourceAble(3pm) NAME
TM::ResourceAble - Topic Maps, abstract trait for resource-backed Topic Maps SYNOPSIS
package MyNiftyMap; use TM; use base qw(TM); use Class::Trait ('TM::ResourceAble'); 1; my $tm = new MyNiftyMap; $tm->url ('http://nirvana/'); warn $tm->mtime; # or at runtime even: use TM; Class::Trait->apply ('TM', qw(TM::ResourceAble)); my $tm = new TM; warn $tm->mtime; DESCRIPTION
This traits adds methods to provide the role resource to a map. That allows a map to be associated with a resource which is addressed by a URL (actually a URI for that matter). Predefined URIs The following resources, actually their URIs are predefined: "io:stdin" Symbolizes the UNIX STDIN file descriptor. The resource is all text content coming from this file. "io:stdout" Symbolizes the UNIX STDOUT file descriptor. "null:" Symbolizes a resource which never delivers any content and which can consume any content silently (like "/dev/null" under UNIX). Predefined URI Methods "inline" An inlined resource is a resource which contains all content as part of the URI. Currently the TM content is to be written in AsTMa=. Example: inlined:donald (duck) INTERFACE
Methods url $url = $tm->url $tm->url ($url) Once an object of this class is instantiated it keeps the URL of the resource to which it is associated. With this method you can retrieve and set that. No special further action is taken otherwise. mtime $time = $tm->mtime This function returns the UNIX time when the resource has been modified last. 0 is returned if the result cannot be determined. All methods from LWP are supported. Special resources are treated as follows: "null:" always has mtime 0 "io:stdin" always has an mtime 1 second in the future. The idea is that STDIN always has new content. "io:stdout" always has mtime 0. The idea is that STDOUT never changes by itself. SEE ALSO
TM AUTHOR INFORMATION
Copyright 200[67], Robert Barta <drrho@cpan.org>, All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. http://www.perl.com/perl/misc/Artistic.html perl v5.10.1 2010-08-04 TM::ResourceAble(3pm)