Jerry Feldman writes:
> In an engineering
> environment, the engineer frequently needs to test on his/her own
> system. Many times there is a need for the engineer to have thew ability
> reconfigure the system as necessary without bothering the system
> admin people.
Let me just chime in and agree with Bob and Jerry here.
In my world, the sysadmin staff are busy running the network and
keeping servers up and running. If an engineer needs help maintaining
his or her system, he or she can ask the sysadmin staff for help. But
in general, engineers do most of their own sysadmin work on their own
development systems.
(For example, our sysadmin staff is pretty busy, so, for example, when
it came time to add a new drive to my system a few years ago, I did it
myself because if I had waited on the sysadmin staff, I would have had
to have waited *days* for this to get done. So I picked up a manual
and figured how to do this myself (hey, I'm an engineer, this is
basically what I have to do all the time anyways).)
The only caveat I should mention is that the sysadmin staff pretty
aggressively says to the engineering staff "don't hose the network".
This means "don't kill the backbone routers" and "don't attach a modem
to your system and comprimise security" and "don't mess with the
firewall".
Everybody seems to keep busy enough this way, and I don't know of any
complaints that are specific to this arrangement.
--kevin
--
Kevin D. Clark | |
[EMAIL PROTECTED] | [EMAIL PROTECTED] | Give me a decent UNIX
Enterasys Networks | PGP Key Available | and I can move the world
Durham, N.H. (USA) | |
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
