From: ralph@inputplus.co.uk (Ralph Corderoy)
Subject: [TUHS] pre-UNIX legacy in UNIX?
Date: Tue, 19 Dec 2017 19:05:09 +0000 [thread overview]
Message-ID: <20171219190509.794961F96E@orac.inputplus.co.uk> (raw)
In-Reply-To: <d28cd69f-fd03-de8e-14ce-860ff9f25bdf@spamtrap.tnetconsulting.net>
Hi Grant,
> > https://en.wikipedia.org/wiki/Gecos_field
>
> Was the GECOS field meant to be consumed by a computer or human?
Computer for its original purpose. And computer again when things like
finger(1) would take it apart. As well as reading the above page,
there's http://catb.org/jargon/html/G/GECOS.html
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
next prev parent reply other threads:[~2017-12-19 19:05 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
2017-12-19 19:05 ` Ralph Corderoy [this message]
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=20171219190509.794961F96E@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
/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).