I've always seen system administrators as the homeostasis that regulates the operation of the nonbiological entity known as a server infrastructure.
Of course, telling people that will get you worse than strange looks. --Matt On Wed, Jan 12, 2011 at 6:21 PM, Brad Knowles <[email protected]> wrote: > On Jan 12, 2011, at 12:37 PM, Michael Ryder wrote: > >> For example.... one definition might look like this: "A System Administrator >> is one who manages computers and/or networks on a continuing basis to >> support the needs of the users of those systems. In addition, the SA may >> also be responsible for these other roles for their systems: design, >> implementation, change control, new technology evaluation, decommissioning, >> etc." > > If we're going to start with definitions, I think we should start with the > definition from WikiPedia (see > <http://en.wikipedia.org/wiki/System_administrator>): > > A system administrator, systems administrator, or sysadmin, is a person > employed to maintain and operate a computer system and/or network. System > administrators may be members of an information technology (IT) or > Electronics and Communication Engineering department. > > The duties of a system administrator are wide-ranging, and vary widely from > one organization to another. Sysadmins are usually charged with > installing,supporting, and maintaining servers or other computer systems, and > planning for and responding to service outages and other problems. Other > duties may include scripting or light programming, project management for > systems-related projects, supervising or training computer operators, and > being the consultant for computer problems beyond the knowledge of technical > support staff. To perform his or her job well, a system administrator must > demonstrate a blend of technical skills and responsibility. > > > If there's something wrong with this, or it can be clarified, or it needs to > be expanded, we can discuss that. > > I will agree that we need a simplest/briefest description, plus at least one > or two more in-depth descriptions. Keep the "thirty second elevator pitch" > in mind, and that should only be the longest form of description -- > everything else should be shorter. > > -- > Brad Knowles <[email protected]> > LinkedIn Profile: <http://tinyurl.com/y8kpxu> > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- LITTLE GIRL: But which cookie will you eat FIRST? COOKIE MONSTER: Me think you have misconception of cookie-eating process. _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
