The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: random832@fastmail.com (Random832)
Subject: [TUHS] Line Terminators in Text Files
Date: Tue, 05 Sep 2017 09:02:42 -0400	[thread overview]
Message-ID: <1504616562.408048.1095616240.70DA0025@webmail.messagingengine.com> (raw)
In-Reply-To: <201709041832.v84IWYF2030885@coolidge.cs.Dartmouth.EDU>

On Mon, Sep 4, 2017, at 14:32, Doug McIlroy wrote:
> Because of the model 33, login names were case-insesitive.
> Come to think of it, I don't know whether they still are
> in general, though they must be for email to be delivered by
> login name.

Looking at the code for getty in various versions, it looks like 4.2BSD
and System V changed this to "if the name was entered in all uppercase,
convert it to lowercase, else leave it alone" - 4.1cBSD and System III
(and earlier) had it unconditionally convert to lowercase, detecting
whether it was entered in all uppercase in order to set the tty mode. 

As for email, the email standards don't make any guarantee that the
username portion of addresses will be case insensitive. From what I can
find, sendmail by default converts all characters in the username
portion to lowercase (thus allowing email addresses to be
case-insensitive for delivery to local usernames that must be in all
lowercase), and has an option to treat it as case-sensitive instead.

(All of this can probably be rounded down to "Usernames should be
defined as all-lowercase")


  reply	other threads:[~2017-09-05 13:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 18:32 Doug McIlroy
2017-09-05 13:02 ` Random832 [this message]
2017-09-05 13:18   ` Steffen Nurpmeso
2017-09-05 14:46   ` Clem Cole
2017-09-05 15:44     ` Random832
2017-09-05 16:05       ` Clem Cole
2017-09-05 16:10         ` Random832
2017-09-06 15:24 Doug McIlroy
2017-09-06 18:30 ` William Cheswick
2017-09-07  9:02   ` Mutiny 

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=1504616562.408048.1095616240.70DA0025@webmail.messagingengine.com \
    --to=random832@fastmail.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).