In article <[EMAIL PROTECTED]>,
Robert Aitchison <[EMAIL PROTECTED]> wrote:
>guys trying to "figure out" the UNIX system as they go. This is one of the
>legitimate advantages to standardizing on NT, that you don't have to hire
>(or contract) out three or more entirely different skill sets.
They're not. The idea that NT requires a "fundamentally different skill set"
from UNIX is a myth. Any administrator who can't come up to speed on a UNIX
based box, if they have the solid understanding of networking and NT they
claim to, is simply not competant. UNIX and NT are much more similar than
any operating systems back in the mainframe era: you've got the same word
size, almost the same filename syntax, the file system and permission sets
in NT are clearly an extended version of the UNIX ones. The biggest difference
between the two are in NT's use of a user-space-visible cryptographic key
rather than a hidden ID for determining permissions, and in the programming
model... and in both cases UNIX is far simpler than NT and easier to wrap
your head around.
I took on the task of administering NT with a mostly UNIX background: the extent
of my experience with Windows was setting up my son's PC. NT is a far more
complex system, but I've been able to wrap my brain around it to the point
of finding and fixing security holes without a huge effort. I've repeatedly
found that my understanding of NT is better than that of many MSCEs and
Microsoft Certified trainers.
I can't believe that goingthe other way could possibly be anywhere near as
hard. NT has so much stuff in it that was obviously modelled on UNIX that
UNIX should seem immediately familiar to anyone with enough understanding of
NT to set up a firewall.
--
In hoc signo hack, Peter da Silva <[EMAIL PROTECTED]>
`-_-' Ar rug t� barr�g ar do mhact�re inniu?
'U` "Be vewy vewy quiet...I'm hunting Jedi." -- Darth Fudd
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
