From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] short file names...
Date: Mon, 12 May 2014 11:44:57 -0700 [thread overview]
Message-ID: <4eb9ad31a5725d1e67cfabbcfc5eac3d.squirrel@webmail.yaccman.com> (raw)
Erg! Discussion of file name length brought back some chilling memories
of very early Unix, when file names were at most 6 characters long.
Longer names were accepted but truncated at 6 characters. So you could
edit ABCDE.c, store it, read it and edit it again, but the file system
knew it as "ABCDE." So when you compiled the program, the compiler
produced ABCDE.o, which overwrote the source code!
reply other threads:[~2014-05-12 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4eb9ad31a5725d1e67cfabbcfc5eac3d.squirrel@webmail.yaccman.com \
--to=scj@yaccman.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).