From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Of login (and host) names
Date: Mon, 18 Jul 2016 10:35:14 -0400 [thread overview]
Message-ID: <1468852517.22016.for-standards-violators@oclsc.org> (raw)
Google was not the first place Rob and Dave had fun with names.
At one point, Rob had a duplicate entry in /etc/passwd,
with login name r, password empty, normal userid/groupid/home
directory, special shell. The shell program checked whether
it was running on a particular host and a particular hardwired
serial line: if yes, it ran the program that started the Research
version of the window system for our bitmapped terminals;
otherwise it just exited. The idea seemed to be to let him
log in quickly in his office.
I think that by the time I arrived at Bell Labs he'd stopped
using it, because it no longer worked, because we no longer
ran serial lines directly from computers to offices--everyone
was connected via serial-port Datakit instead.
While I was there, senior management bought a Cray X-MP/24 for
the research group. (Thank you for using AT&T.) Since it too
was accessible via Datakit (using a custom hardware interface
built by Alan Kaplan, but that's another story), it had to have
a hostname. It was either Dave or Rob, I forget which, who
suggested 3k, because (a) it was a supercomputer, so `big bang'
seemed to fit; (b) it was Arno Penzias, then VP for Research,
who got us the money, so `big bang' and 3K radiation seemed
even more appropriate; and, most important, (c) it was fun to
see whether a hostname beginning with a digit broke anything.
So far as I recall, nothing broke. Some people who were
involved with TCP/IP networking at the labs were frightened
about it; I don't remember whether that Cray was ever connected
to an IP network so I don't know whether anything went wrong
there. Of course such names are not a problem today, but
in those long-lost days when nobody worried much about buffer
overflows either, such bugs were much more common. Weren't they?
Norman Wilson
Toronto ON
next reply other threads:[~2016-07-18 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:35 Norman Wilson [this message]
2016-07-18 14:46 ` Mary Ann Horton
2016-07-18 15:15 ` John Cowan
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=1468852517.22016.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
/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).