The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: paosborne@gmail.com (Paul Osborne)
Subject: [TUHS] Of login names
Date: Sun, 17 Jul 2016 00:04:56 +0100	[thread overview]
Message-ID: <CABoOk8bovORuXn7w2aazhHDffW-V_oNqVUahDhNfXVJcq=7noA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1607170234350.65801@aneurin.horsfall.org>

Heh. At a previous site around 20 years ago we used initial letters of
names generated automatically with a number following so at one point had:

kunt2 Chinese student who didn't raise an issue until 2. 5 years into his
course, we changed that one and put in a rude word filter on login checks.

jc8 so the student was nicknamed "digger" who was not happy so we naturally
refused to change his login as the name had stuck.

we3 - who was quite proud of that one I was told.

Am sure there were many more.

Cheers

Paul

On 16 Jul 2016 11:56, "Dave Horsfall" <dave at horsfall.org> wrote:

> Time to start a new thread :-)
>
> Back when Unix was really Unix and dinosaurs strode the earth, login names
> were restricted to just 8 characters, so you had to be inventive when
> signing up lots of students every term (ObUS: semester).
>
> A wonderful Japanese girl, Eriko Kinoshita, applied for an account on some
> box somewhere.  Did I mention that login names defaulted to the first 8
> characters of the surname?
>
> Understandably annoyed, Plan B for assigning logins was applied, which was
> the first name followed by the first letter of the surname.
>
> Sigh...
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160717/eca317d5/attachment.html>


  reply	other threads:[~2016-07-16 23:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-16 16:54 Dave Horsfall
2016-07-16 23:04 ` Paul Osborne [this message]
2016-07-18 12:24   ` Tony Finch
2016-07-18 13:21     ` John Cowan
2016-07-17  2:56 ` Win Treese
2016-07-17  6:39 ` Tim Bradshaw
2016-07-17  8:06 Rudi Blom
2016-07-17  8:16 ` Greg 'groggy' Lehey
2016-07-17 11:42 ` Ronald Natalie
2016-07-17 22:59   ` Greg 'groggy' Lehey
2016-07-18  0:37     ` Brantley Coile
2016-07-18 10:51       ` William Cheswick
2016-07-17 12:05 Norman Wilson
2016-07-17 12:32 ` Ronald Natalie
2016-07-17 23:09 ` Greg 'groggy' Lehey
2016-07-18  4:06   ` scj
2016-07-18  4:09     ` Larry McVoy
2016-07-18 10:42     ` William Cheswick
     [not found] <mailman.79.1468802270.30583.tuhs@minnie.tuhs.org>
2016-07-18 14:06 ` David
2016-07-19 12:41   ` Aaron Jackson
2016-10-19 20:53     ` Michael-John Turner
2016-10-19 22:35       ` Aaron Jackson
2016-07-18 14:35 Norman Wilson
2016-07-18 14:44 ` Mary Ann Horton
2016-07-18 14:55   ` Ronald Natalie
2016-07-18 18:07 ` Steve Simon
2016-07-19  9:50   ` Tony Finch
2016-07-26 12:45   ` Tim Bradshaw
2016-07-26 13:07     ` George Ross
2016-07-18 15:44 Doug McIlroy
2016-07-18 15:50 ` Joerg Schilling
2016-07-18 18:03   ` Ronald Natalie
2016-07-18 18:12     ` Steve Nickolas

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='CABoOk8bovORuXn7w2aazhHDffW-V_oNqVUahDhNfXVJcq=7noA@mail.gmail.com' \
    --to=paosborne@gmail.com \
    /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).