05-03-2008, 09:26 PM | #1 |
Colonel
236
Rep 2,547
Posts |
any UNIX people in here???
I have an interview for a junior developer position and it requires Unix. They think I might be a good candidate with a strong SQL background. Now for the question, how hard is it to pick up Unix?
|
05-03-2008, 10:31 PM | #2 |
Lieutenant
71
Rep 526
Posts |
Strong SQL background eh? Do any site designing? I need a web designer.
__________________
|
Appreciate
0
|
05-03-2008, 10:45 PM | #3 | |
Major
199
Rep 1,010
Posts |
Quote:
Seriously, it won't be too difficult to pick up for you since you have a SQL background - I found learning AD more difficult since it's a bastardized version of NDS and a lot of things don't make sense.
__________________
|
|
Appreciate
0
|
05-04-2008, 12:18 AM | #4 |
Second Lieutenant
4
Rep 205
Posts |
what does knowing SQL have anything to do with Unix? NOTHING.
it's hard to pick up UNIX if you don't use it, but like any command line interface, you can learn some of the basic commands and be able to make your way around. i'd suggest you install linux and start messing around with it. you don't need a book since all your resources can be found online, but i think for a jr dev position, you can get away with just knowing basic, cp, rm, md, cd, ls, grep, find, ps, mount and umount. know how to redirect IO, setup your network, and how to start and stop services. maybe learning some of the more important conf files would help as well. |
Appreciate
0
|
05-04-2008, 12:29 AM | #5 |
Major
199
Rep 1,010
Posts |
Correct. What I meant was, he already has a background in a programming language, so he wouldn't find it too difficult to learn an OS like Unix. Just trying to encourage the chap
__________________
|
Appreciate
0
|
05-04-2008, 12:41 AM | #7 | |
Gobble gobbledygook
5
Rep 287
Posts |
Quote:
The amount of experience required increases if we need to interact more with the system, for instance if we deal with firewalls then we have to understand iptables (for Linux), how routing takes place, firewall rules and polices, etc. At this level, I find it easier to read the documentation that comes with the packages, or google them, rather than read a book which is likely to be outdated by the time it's published. If I were you I would try and get some idea of the kind of development required. For instance if it's some website Ruby thing, then I'll run through the Ruby installation process, try writing some code, and get it to run. Trying it yourself has got to be the most important step |
|
Appreciate
0
|
05-04-2008, 06:32 AM | #8 |
Mmmmmkay
70
Rep 433
Posts |
I run a software company which currently has about 45 servers in 3 datacenters. The majority of these servers were windows up until about 1 year ago when I decided i was just sick and tired of Mircrosoft.
We have made a 90% switch to Linux Red Hat and CentOS (free version of RHEL). It took me about 5 installs in VMWare before I was comfortable with everything from networking, configuration, building stuff from source, etc. We are running pretty advanced configurations which include Bonded NIC devices and High Availability with DRBD and the LinuxHA (heartbeat) project. anyway the moral of the story is that if you are a smart guy and understand computers... you will have no problem whatsoever. -G |
Appreciate
0
|
05-04-2008, 09:01 AM | #9 |
287
Rep 6,510
Posts |
IMHO... The harder part of running unix is dealing with the major differences in how each distribution handles packages, networking, config file locations, startup scripts, etc... but all of that is easily googled.
When it comes down to learning the basics, just get a book, and run some non-gui flavors of unix at home to play around with, and configure. |
Appreciate
0
|
Post Reply |
Bookmarks |
|
|