Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!execu!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F. Haugh II)
Newsgroups: comp.unix.admin
Subject: Re: Different uses of the 5th field of the passwd file.
Message-ID: <18729@rpp386.cactus.org>
Date: 14 Nov 90 05:11:23 GMT
References: <723@dynasys.UUCP> <1990Nov6.045108.20266@riacs.edu> <1990Nov8.060424.1828@blackbox.lonestar.org> <3851@dftsrv.gsfc.nasa.gov>
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: Lone Star Cafe and BBS Service
Lines: 20
X-Clever-Slogan: Recycle or Die.

In article <3851@dftsrv.gsfc.nasa.gov> williams@nssdcs.UUCP (Jim Williams) writes:
>"GCOS field.  Typically the user's complete name.  It can also contain other
>things such as a phone number, or silly comment.  In other words, it isn't
>defined.  It is called the GCOS field historically because it was originally
>used to define an accounting ID that was submitted with remote batch jobs to
>the GCOS system at Bell Labs."

I'd say that what BSD does with it is about as close a definition as
one gets.  finger(1) "knows" where the various pieces of information
all live, and I believe it is the only program anymore which cares.
The BSD chfn command will prompt for the appropriate information and
splatter it all over the password file for you.

The source to a "chfn" was posted to alt.sources a while back.  You
might try digging around an archive site somewheres.
-- 
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh@rpp386.cactus.org
"SCCS, the source motel!  Programs check in and never check out!"
		-- Ken Thompson