From: charles.unix.pro@gmail.com (Charles Anthony)
Subject: [TUHS] Early Internet work
Date: Wed, 8 Feb 2017 16:37:40 -0800 [thread overview]
Message-ID: <CANV78LTwpdTxFLBsJXzh=QkOtdb-35imHMo9JGud930nTYbjxw@mail.gmail.com> (raw)
In-Reply-To: <CANV78LSSV6XiOZ1vh-8mHbkc_jvnh86ps92jswzpDZ-E9NCvcw@mail.gmail.com>
On Wed, Feb 8, 2017 at 3:47 PM, Charles Anthony <charles.unix.pro at gmail.com>
wrote:
>
>
> On Wed, Feb 8, 2017 at 3:16 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
> wrote:
>
>> > Hi, we just read the second tape, which read without error.
>> > ...
>> > So at this point we have access to everything that was on that
>> machine.
>>
>> So, in the process of transferring this all to a TAR file, we found a bug
>> in
>> BSD 4.1b. (The length of some directories whose last sector held only one
>> entry was being incorrectly set to the actual length of the directory,
>> not a
>> multiple of the sector size.)
>>
>> Anyone know where I can report a BSD 4.1b bug? :-)
>>
>> Sigh. That tops my Multics bug report.
>
> Maybe not. The Multics segment containing the error is marked "WRITTEN
03/26/76". BSD4.1 is circa 1890?
(Sorry for drifting off-topic)
-- Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170208/db3c222d/attachment-0001.html>
next prev parent reply other threads:[~2017-02-09 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 23:16 Noel Chiappa
2017-02-08 23:47 ` Charles Anthony
2017-02-09 0:37 ` Charles Anthony [this message]
2017-02-09 1:31 ` Chet Ramey
-- strict thread matches above, loose matches on Subject: below --
2017-02-17 16:51 Noel Chiappa
2017-02-17 17:06 ` Larry McVoy
2017-02-13 23:20 Noel Chiappa
2017-02-14 7:37 ` SPC
2017-02-09 1:32 Noel Chiappa
2017-02-09 1:46 ` Dan Cross
2017-02-08 18:00 Noel Chiappa
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='CANV78LTwpdTxFLBsJXzh=QkOtdb-35imHMo9JGud930nTYbjxw@mail.gmail.com' \
--to=charles.unix.pro@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).