From: doug@remarque.org (Doug Merritt)
Subject: [Unix-jun72] UNIX V1 bootstrap
Date: Sat, 17 May 2008 20:23:48 -0700 (PDT) [thread overview]
Message-ID: <20080518032348.3D6E65A523@remarque.org> (raw)
In-Reply-To: <20080518012410.GA59280@minnie.tuhs.org>
Warren wrote:
> I'm going to take a "devil's advocate" stance here, and argue to keep the
> existing "as" binary untouched.
As first priority, certainly. We want to preserve original
data for posterity.
As second priority, there may be several possibilities.
A best-guess reconstruction of an approximation of V1
is one such additional possibility. Interpolation based
on noisy data sources is a time honored practice -- as
long as one carefully differentiates the results from
pristinely clean data.
I don't see one kind of reconstruction as inherently better
or worse than another kind; it depends on what the goal is.
I think Apout, for instance, is a *really* nice variation
on the usual approach of a closed-world simulation.
And certainly there are sharp limits on what we have available
right *now*, but I would be quite cautious about saying "never".
Additional data sources may become available; who knows.
Doug
--
Professional Wild-eyed Visionary Member, Crusaders for a Better Tomorrow
next prev parent reply other threads:[~2008-05-18 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 1:04 James A. Markevitch
2008-05-18 1:24 ` Warren Toomey
2008-05-18 3:23 ` Doug Merritt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-18 6:18 James A. Markevitch
2008-05-18 6:28 ` Warren Toomey
2008-05-11 14:13 James A. Markevitch
2008-05-17 18:06 ` Tim Newsham
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=20080518032348.3D6E65A523@remarque.org \
--to=doug@remarque.org \
/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).