Quote:
Originally Posted by jcblitz
See, heres an example. I haven't touched my ubuntu install in a month so I decided to fire it up after posting this...and this is what I get. It's just stuck here.
|
Well first, its because you're using Ubuntu - atleast get a real desktop, ie: KDE
Ant, theres ALOT to deal with in Linux. I have not used windows at home in *years*, and I'm quite happily getting all my stuff done in KDE. However, I began with linux around 1994.
Can he learn enough to get a good intro to it in a few days? Yes.
Will he be able to do more than the basics? Doubtful.
If he is going to be supporting Linux from an admin standpoint, he should be familiar with the various scripting languages out there (perl, python, some bash scripting), some programming (primarily C++ with KDE, C for kernel modules, C with an ugly gui would be gtk/GNOME), etc.
It also heavily depends on what kind of Linux box he'd be supporting - if its servers, it may be anything from Slackware (complicated, but simple once you get it) to Debian (stable as balls, but always behind) to Red Hat (Easily managed using Red Hat's administrative tools, but RPM is a shitty pain in the ass package format, and GNOME is ugly
). Also, I've met some management types that refer to Solaris, the BSD's, and even AIX as "Linux" because they don't know the difference. In serverland, the BSD's are very nice to administer, I'm personally not a Solaris fan, but they are all quite popular.
If they are using it on the desktop (as a number of companies are doing this now), there are an assload of tools that come into play. Often times a server will be set up in house to handle package management, where the desktops check this in-house package repository for security and application updates so that they can be tested locally. The nice thing is, if the machines use PXE, it is EXTREMELY easy to install Linux on a shitload of desktops. Create once, install everywhere - a work of beauty.
The problems depend on how they are using Linux. It could be as a webserver, in which case problems can arise from php scripts not working properly (such as an older version of php is being used, or perhaps apache needs to be upgraded to a more recent release to make use of it); it could be a CUPS (Common Unix Printing System) server handling all the print jobs in the building over ipp, where the CUPS server going down halts printing; it could be alot of things.
There are tons of questions I could ask - just find out what they are using Linux for, and I could create a friggin test
****************
EDIT
****************
Jared, are you using Ubuntu on a mac?
Thats the only time I've ever seen it fail like that. PS: Macs also suck.