From: milov@cs.uwlax.edu (Milo Velimirović)
Subject: [TUHS] early cc variable and function names
Date: Fri, 17 Oct 2014 09:22:00 -0500 [thread overview]
Message-ID: <9B907A1F-0FAD-4633-8E74-17F332905E9B@cs.uwlax.edu> (raw)
In-Reply-To: <201410171407.s9HE7jXl010061@freefriends.org>
On Oct 17, 2014, at 9:07 AM, arnold at skeeve.com wrote:
> Warner Losh <imp at bsdimp.com> wrote:
>>> For VAX, 4BSD appears to use an "index into file string table", whereas
>>> 3BSD still has an 8-character string. I don't see any provision in the
>>> 4BSD linker for loading 3BSD binaries.
>
> I think System III or System V picked this up.
>
>>> Filenames over 14 characters appear to have been introduced in 4.1BSD.
>
> No, at 4.2 BSD with the Fast Filesystem. (Maybe 4.1c or some such
> already had the FFS, but the original 4.1 didn't...)
>
> Arnold
Right!
McKusick, et al. say that it came with the Fast Filesystem in 4.2 [1]
I recall a presentation at UW in Madison where he said, (paraphrasing from memory) We heard you guys. We included long file names in the Fast File System. (loud cheers)
- Milo
[1] https://www.cs.berkeley.edu/~brewer/cs262/FFS.pdf
next prev parent reply other threads:[~2014-10-17 14:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 1:51 Mark Longridge
2014-10-17 2:20 ` Milo Velimirovic
2014-10-17 2:21 ` Dave Horsfall
2014-10-17 13:35 ` random832
2014-10-17 13:44 ` Warner Losh
2014-10-17 14:07 ` arnold
2014-10-17 14:22 ` Milo Velimirović [this message]
2014-10-17 19:29 ` random832
2014-10-18 7:25 ` Greg 'groggy' Lehey
2014-10-17 2:29 Noel Chiappa
2014-10-17 2:40 ` John Cowan
2014-10-17 2:52 ` Larry McVoy
2014-10-17 3:46 ` John Cowan
2014-10-17 3:54 ` Larry McVoy
2014-10-17 19:41 ` Clem Cole
2014-10-17 20:37 ` random832
2014-10-17 20:42 ` Larry McVoy
2014-10-17 16:11 Noel Chiappa
2014-10-18 10:32 Noel Chiappa
2014-10-18 23:03 ` Ron Natalie
2014-10-18 23:11 ` Dave Horsfall
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=9B907A1F-0FAD-4633-8E74-17F332905E9B@cs.uwlax.edu \
--to=milov@cs.uwlax.edu \
/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).