Thoughts - Should I spend the time to learn *nix

[2canSAM]

I am somewhat new to the networking field and am really looking for a few opinions I guess. I have a general knowledge of alot of stuff but I am ready to really get back in the saddle to study. I mean I can set up an windows sytems as clients or servers, set up routers, firewalls, IIS, Exchange Svr 2000, but I cannot set it up to be the MOST efficent. So far I have only messed with Windows products and have finished 3 of the MCSE exams. I took a break from that to mess around with the Cisco side of it but have slacked off there as well. Let me tell you what I want to do. I am not looking to make a huge pile o money on this field. I know it is there to be made but I enjoy this as a hobby too much. My goal is to start consulting out to small companies (250> users) doing some networking stuff. Basically me and a few others will setup the servers, routers, clients, and anything else they need like RAS or VPN, webhosting and stuff like that. The whole Unix/Linux/Open Office thing seems great because of the cost involved to the companies. It will be cool to walk and say that the cost for the software will be $0.00. Know I learn quickly but am wondering from some of you who are already working in this field as to what you would recommend. Should I give up the time to learn *nix or stick with MS offerings. Thanks in advance.

 

[ScottMac]

Well, first off, IMO, it never hurts to diversify your knowledge. Long ago in a galaxy far away, all you needed to know was Novell, and life was good.

Then the lying bastards from Redmond* flim-flamed the market through a series of golf course hypnotizations and rodent-ranching hijinks, and look where we are now....

Well, Unix is still the best database server (outside the 390/AS400 transactional environment), and many companies of various sizes are deciding to give Linux a try ... and liking it, some of 'em are lovin' it, and putting more and more services / resources up for the Enterprise on big-build Linux boxes. Who'd a thunk it?

Bottom line: Learn *nix, if you do anything in the biz, you're eventually gonna run across it. It's best to stay neutral (like me) and be able to recognize the merits of each system, and properly apply it to the solution. If the best solution is that junk GUI-head crap from the NorthWest, then so be it..... (j/k, honest!)

* I have many friends at Microsoft, we give each other crap all the time ... relax, no flames please.

===== ====== ===== ====== =====

Next issue:

Don't even think about doing consulting work unless you know what you're doing, and how you're going to do it. Setting up business networks isn't anything like setting up a couple machines at home or at school. There are a jillion considerations, and way down the list are "IWBC - It Would Be Cool," "Athlon Rocks!," and "This thing really cranks at Warcraft."

There are also a mess of legal considerations. LIke what if the thing you just added to the network eats a primary, business-critical resource? Can you handle an Irate CIO screaming that he's gonna sue you for the US$120,347.50 that he lost because of your "careless or neglegent mistake?" They aren't gonna waht to hear that "you didn't know anything about that stuff....." you're on the hook, and it can cost you.

There's a lot to learn aside from the techy end of the deal. You gotta know the business. You have to know how to write a scope of work and live by it. Oh man, the list is long and you have to know most of it cold.

IMO, your best bet is to do some time in an established consulting group, VAR, reseller, whatever ... and see what the business side looks like before trying it yourself.

JM.02

Scott

 

[Garion]

I'll second Scott's sentiment. Unix is exceedingly valuable in the world of networking. There is a tremendous wealth of useful network applications available ONLY on Unix machines. Also, many network devices use a very unix-like command lanuage and interface structure. Understand Unix, and you'll have a much better feel for a lot of the more intricate functions of a network.

One other important thing - Many network "appliances" are actually Unix-based systems, with some custom code or hardware. A great example are F5 load balancers - They look like a switch (or a pretty stand-alone box), but it's really just an Intel PC with a P3, Tyan motherboard and a really cool case and Linur or FreeBSD. You can do a lot of the basics from the pretty GUI, but to REALLY do the advanced stuff, you need to use the command line.

IMHO, there's a lot of network guys out there, but it's Unix that separates the men from the boys..

- G

 

[Rogue]

Another thought for you to ponder is your running in and touting the benefits of the $0.00 software implementation. That's a one-sided view of it. Once you create those builds and setup that software environment, who's gonna constantly maintain it? You? Someone else? The local "IT guy"? Hate to say it, but using something like that, with all it's complexities (yes, I know it can be easy also) is going to lock you into supporting it constantly. I'm not knocking Open Source or anything like that, just know that it's much easier 9 times out of 10 to walk a dimwit through the Microsoft Support site over the phone than it is to assist them with *nix based software.

PS-I know someone going to come along and think it's totally necessary to flame me for something I've said, but chill out and relax, *nix is here to stay.

 

[2canSAM]

Thanks for all the replies. I now have a lot more to consider. I am aware of the issues involved with consulting as I have set up a few small networks here in town. Consulting is still down the road quite a bit. That is just the ultimate goal for me. I think I will get serious about the *nix study for now, as scott mac said join up with another company to get some real hands on experience of *nix in an enterprise enviroment. After I feel 200% positive that I can handle it, then I'll move on to consulting.

 

[Soybomb]

Originally posted by: Rogue
Another thought for you to ponder is your running in and touting the benefits of the $0.00 software implementation. That's a one-sided view of it. Once you create those builds and setup that software environment, who's gonna constantly maintain it? You? Someone else? The local "IT guy"? Hate to say it, but using something like that, with all it's complexities (yes, I know it can be easy also) is going to lock you into supporting it constantly. I'm not knocking Open Source or anything like that, just know that it's much easier 9 times out of 10 to walk a dimwit through the Microsoft Support site over the phone than it is to assist them with *nix based software.

PS-I know someone going to come along and think it's totally necessary to flame me for something I've said, but chill out and relax, *nix is here to stay.

Then you have to ask too though, how often do you need support? If it doesn't break....... I'll admit though it would be wise to thoroughly document configuration

 

[sml]

UNIX > *.
Don't think about being a UNIX-oriented consultant unless you have serious experience in the field; The business world likes Solaris, IRIX and AIX and tends to scoff at open source offerings like Linux; this is changing, but even 'enterprise' Linux is OS/390 zSeries type stuff