The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] pre-UNIX legacy in UNIX?
Date: Tue, 19 Dec 2017 11:21:26 -0700	[thread overview]
Message-ID: <d28cd69f-fd03-de8e-14ce-860ff9f25bdf@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CACCFpdx0UamZwaXf=LaAjFU=SfBx6RQJirj3qcGz49zDi_L=Mw@mail.gmail.com>

On 12/18/2017 11:00 PM, Nigel Williams wrote:
> I blundered today into the GECOS field in /etc/passwd:
> 
> https://en.wikipedia.org/wiki/Gecos_field
> 
> "Some early Unix systems at Bell Labs used GECOS machines for print
> spooling and various other services,[3] so this field was added to
> carry information on a user's GECOS identity."

Was the GECOS field meant to be consumed by a computer or human?

All the descriptions I've seen about the GECOS field made me think that 
it was for human friendly information [1] and not really machine parsable.

So, was there some sort of ID in the GECOS field in a users /etc/passwd 
entry that was then used by the GECOS machine / OS to identify the user?

Or is my (complete) ignorance of GECOS (OS) showing that I'm not aware 
of something about user IDs on GECOS (OS)?

> I had forgotten about this field and I don't recall it being
> previously described as related to GECOS (I likely didn't take note at
> the time I first encountered it).

I had often wondered why it was called "GECOS", but had never really 
given it any thought as it seemed logical to have something to store the 
users contact information somewhere convenient and easily accessible by 
all applications.  Thus the /etc/passwd file seemed like a logical choice.

Now I wonder if we are using the GECOS field to store the same data as 
years ago?  Or did we re-purpose the now unneeded GECOS to store name, 
address, office phone number, home phone, etc?

I never knew about GECOS (OS) to put two and two together.

#questionsQuestions



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171219/443a14f3/attachment-0001.bin>


  parent reply	other threads:[~2017-12-19 18:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19  6:00 Nigel Williams
2017-12-19  6:21 ` Lars Brinkhoff
2017-12-19  7:07   ` Don Hopkins
2017-12-19 18:21 ` Grant Taylor [this message]
2017-12-19 19:05   ` Ralph Corderoy
2017-12-19 20:03     ` Grant Taylor
2017-12-19 20:14       ` arnold
2017-12-19 22:30   ` [TUHS] History of passwd fullname/info/"gecos" field (was Re: pre-UNIX legacy in UNIX?) Random832
2017-12-20  3:07     ` Noel Hunt
2017-12-19 18:48 [TUHS] pre-UNIX legacy in UNIX? Doug McIlroy
2017-12-19 20:08 ` Lars Brinkhoff
2017-12-19 22:26   ` Doug McIlroy
2017-12-19 20:29 Richard Tobin
2017-12-20  1:03 Noel Chiappa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d28cd69f-fd03-de8e-14ce-860ff9f25bdf@spamtrap.tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).