You, and the other poster in this thread, are precisely the type of people I hope to never meet in real life.
Have you considered that companies make large investments into software and systems, often times into Microsoft products, that they simply can not "drop" because an entire product is based around it?
Have you considered that it takes as much time to become an expert with Microsoft products as it does with <insert other product here>? It requires time and effort, like anything else in this world.
Have you considered that the industry is going through a very tight phase right now, and a number of my friends are without jobs, and a very jealous of my Win32 admin job?
Are you so clueless as to realize that basic fundamentals do not change between systems? A web server is still a process on a port that uses the HTTP protocol; an email server is still a process that stores and relays messages using SMTP,IMAP, or your favorite protocol, regardless if it's Sendmail, Qmail or Exchange.
Have you woken up enough to realize that Windows 2000 (all versions) can be configured and administered from a command line (cmd.exe for win2k)? Have you explored Active Directory Services Interface (ADSI) and Windows Management Instrumentation (WMI) as tools to built custom administration tools? Did you know perl has interfaces for WMI and ADSI?
Did you guess that I've been both a unix and windows systems administrator? I learned different skills in each, but the basic fundamentals of systems administration does not change. Not only the technical parts, but the important parts of keeping a complex system running: documentation, communication, isolating problems, showing cause-and-effect, testing, backup, the list goes on.
By the way, ActivePerl allows perl CGI apps to run under IIS quite nicely.
Cheers,
ibanix
$ echo '$0 & $0 &' > foo; chmod a+x foo; foo; | [reply]
[d/l] |
Good grief it's a joke.
As for the viability of running W2K from the command line; clearly you are mistaken. There are FAR too many things you CANNOT do from the command line. Further there are so many munged up things about W2K that it boggles the mind. Many of the tools I'll bet you use in your W2K day to day are nasty Unix hacks.
Does this make Windows evil, or unworthy? No It makes it harder. And more tedious.
--
ellem@optonline.net
There's more than one way to do it, but only some of them actually work.
| [reply] |
Good grief it's a joke
A very poor one indeed.
There are FAR too many things you CANNOT do from the command line.
Name them. I've found that most of the things that I thought I could not do from the CLI, I was able to accomplish with some scripting, the Resource Kits, and some ingenuity.
ibanix
$ echo '$0 & $0 &' > foo; chmod a+x foo; foo;
| [reply]
[d/l] |
I have a saying:
Saying you're a Windows Sys Admin is like saying you're a Flight Simulator Pilot.
Guess what I do for a living. (Please God give me the chops to be a Unix admin!)
--
ellem@optonline.net
There's more than one way to do it, but only some of them actually work. | [reply] |
I am not a Windows Sys Admin, nor do I care to be one. But I have a lot of respect for those who do the job and do it well. Large Windows networks are not necessarily easy to administer just because most of the admin tools are GUI based, or because it's cool to hate Microsoft, or...
If you'd rather be a Unix admin than a Windows Admin, that's cool. I'm just saying good Windows admins are as valuable as good Unix admins.
I realize this is OT, so I'll try to redeem myself. A good Windows admin will use scripting to get the job done better, faster, and with more fun. A really good one will use Perl for even more fun. :)
| [reply] |
