> Hi Mark,
> Out of this list I did #1, 2, 3, and 6, already. I had to explain to
> another responder to this post that I had to set up a very secure firewall
> from scratch (i.e. with very little knowledge of FreeBSD or Unix) in one
> week, while working a 50-hour week. Was that tough? To quote you, "Hell
> yeah, it was." But I learned a ton, and with my prior experience and
> knowledge of networking I am now enjoying the fruits of my labor (this
> firewall is probably not going to be hacked before the hardware in this
> machine starts to break down).
> The question now is to see how far I can take this knowledge and have it
> actually turn into a living. As always, if you have any good tip on that, I
> am all ears.
> Simon Chang
Here are a few of other tech things:
1: learn and use/script in a standard shell aka ksh/bash,
I recommend ksh because it is more corporate, solaris,hpux,
aix have it.
2: learn to use your system documentation, 'man man' to learn
the tool. Then read the man pages for the contents of /bin,
/sbin, /usr/sbin, /usr/bin to start with.
3: learn a "popular" scripting language, Perl ,tcl or python.
I would say start with tcl because it is simple and has lots
of real cool extensions, scotty and expect come to mind.
Both are in ports.
Here are some how get work ideas:
1: find a professional users group and join it. After you have
been to a couple of meetings start to volunteer to do stuff
and deliver it. After a while you will have some people who
are impressed with your work ethic and professional attitude.
Then ask them if their companies are hiring or if they know
anybody else who is hiring. And ask them if you can use their
name when you call their friends.
2: If there is a unix group at work go over and ask to help out.
Volunteer to do all the shit work that needs to get done and
deliver it. Again after you have built a good reputation
let them know you would like to work over here all the time.
3: do not ask stupid questions. Ask well thought out questions.
If it looks like you did no work
There is always a shortage of "good" people in the SA trade.
Once people figure out you are one they will want you. Technical
skill is only part of the job, important yes, the rest is how well
you deal with people and are you seen as someone who solves or
causes problem? Are you a bulldozer or a roadblock? If you are
my bulldozer you make me(aka management) happy and filled with
good feelings for you.
Another good piece of advice, that I should follow, is to keep
a daily work log. Use it to build weekly, monthly, quartley and
yearly reports for yourself and management, here is why I should
get a raise X times the company average. It also lets you know
if you are growing in your career as you should.
>> > Does anyone have good suggestion on how this [become a UNIX admin]
>> > can be done?
>> Buy some older computers and setup a network at home:
>> 1. Use FreeBSD and
>> 2. Set up a firewall with 2 NICs, then with 3 NICs (for DMZ)
>> 3. Set up NAT
>> 4. Set up DHCP
>> 5. Set up a DNS and mail server
>> 6. Set up an Apache web server
>> 7. Repeat 2-6 using Solaris 8 Intel.
>> 8. Repeat 2-6 using Linux (I guess Red Hat since that's the "business" one
>> even though all Linuxes suck)
>> 9. Pick your favorite Unix and use that as your desktop. Like Paul said,
>> do EVERYTHING with that desktop.
>> Does this sound like a lot? Hell yeah, it is. However, there are plenty
>> of other guys out there that know how to do some (or all) of this and this
>> is who you are competing with when getting a job. By the time you are
>> with this, you should also have a very good understanding of all of the
>> network layers, protocols, etc.
>> Good luck!
>> - Mark