5 Sep
2017
5 Sep
'17
12:32 a.m.
When did LF replace CR/LF in UNIX?
Never. Unix always took LF as newline--an interpretation
blessed by the ASCII standard. The convention was
inherited from Multics.
Interpolation of CRs was the business of drivers, not file
formats.
As far as I know, the only CR/LF terminal that original
Unix dealt with was the model 33 console. That was identified
by the fact that the login name was received in all caps.
IIRC the TTY 37 conformed to Multics practice on the advice
of Joe Ossanna.
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.
Doug
5 Sep
5 Sep
7:02 p.m.
New subject: Line Terminators in Text Files
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")
7:18 p.m.
New subject: Line Terminators in Text Files
Random832 <random832(a)fastmail.com> wrote:
|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")
If i recall correctly the email standards go for case-preserving
all through, to leave it up to the destination to apply whatever
is appropriate locally.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
8:46 p.m.
New subject: Line Terminators in Text Files
“We're doomed to repeat the past no matter what. That's what it is to be
alive. It's pretty dense kids who haven't figured that out by the time
they're ten.... Most kids can't afford to go to Harvard and be
misinformed.”
― Kurt Vonnegut Jr.
<https://www.goodreads.com/author/show/2778055.Kurt_Vonnegut_Jr_>, Bluebeard
<https://www.goodreads.com/work/quotes/6582745>
On Tue, Sep 5, 2017 at 9:02 AM, Random832 <random832(a)fastmail.com> wrote:
As for email, the email standards don't make any guarantee that the
username portion of addresses will be case insensitive.
Actually they do, RFC722 was not quite as crisp as this which 833 replaced,
but even with 722 the intention was pretty clear and examples described
"case independence of certain special atoms." With 833, Crocker cleaned
up the language to be simply:
From RFC833, Section 3.4.7 CASE INDEPENDENCE
Except as noted, alphabetic strings may be represented in any combination
of upper and lower case. The only syntactic units which requires
preservation of case information are:
- text
- qtext
- dtext
- ctext
- quoted-pair
- local-part, except "Postmaster"
When matching any other syntactic unit, case is to be ignored.
9:44 p.m.
New subject: Line Terminators in Text Files
On Tue, Sep 5, 2017, at 10:46, Clem Cole wrote:
Except as noted, alphabetic strings may be represented
in any combination
of upper and lower case. The only syntactic units which requires
preservation of case information are:
- local-part, except "Postmaster"
So... the username portion.
10:05 p.m.
New subject: Line Terminators in Text Files
On Tue, Sep 5, 2017 at 11:44 AM, Random832 <random832(a)fastmail.com> wrote:
On Tue, Sep 5, 2017, at 10:46, Clem Cole wrote:
so the "postmaster" (username) does not preserve case by this rule.
It had to work that way, because CDC machines in particular in those days
had very funky character sets (lots of them actually). IBM's were not much
better. Remember, IBM was the primary driver behind ASCII (the System 360
was supposed to be IBM's first ASCII system).
Upper and Lower were very much a luxury because bits were expensive. Not
just in registers, but main memory, registers, disk storage.
I think it's hard for modern users to really understand the extremes that
programmers had in those days because so much was done to encode things in
small numeric codes. This was just another example if it.
The 8-bit 'byte' is only so because Fred Brooks, kept throwing Gene Amdahl
out of office during the 360 project. Gene thought anything over 6 bits
was a waste. Fred said if it was not a power of 2 don't come back, he
could not program with it.
Clem
Except as noted, alphabetic strings may be
represented in any combination
of upper and lower case. The only syntactic units which requires
preservation of case information are:
- local-part, except "Postmaster"
So... the username portion.
10:10 p.m.
New subject: Line Terminators in Text Files
On Tue, Sep 5, 2017, at 12:05, Clem Cole wrote:
On Tue, Sep 5, 2017 at 11:44 AM, Random832
<random832(a)fastmail.com>
wrote:
Yes, but, say, "clemc" or "random832" or "tuhs" does (the
endpoint
system might not actually care, but other systems are not free to
capitalize it in the assumption that it won't matter). Postmaster, in
particular, is an exception to the exception.
On Tue, Sep 5, 2017, at 10:46, Clem Cole wrote:
so the "postmaster" (username) does not preserve case by this rule.
Except as noted, alphabetic strings may be
represented in any combination
of upper and lower case. The only syntactic units which requires
preservation of case information are:
- local-part, except "Postmaster"
So... the username portion.
2665
days inactive
2666
days old
6 comments
4 participants
participants (4)
-
Clem Cole -
Doug McIlroy -
Random832 -
Steffen Nurpmeso