From: Rob Pike <robpike@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] retro-fuse project
Date: Tue, 23 Feb 2021 07:13:59 +1100 [thread overview]
Message-ID: <CAKzdPgxTGTLzmimQped8h-HS=raWh1=Tk2R1Mj51Xsk1abE4=Q@mail.gmail.com> (raw)
In-Reply-To: <07665269-ef0d-ca9a-ecfa-cb68e89bbf4b@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Please let us know how you go with the Macs. The system interfaces have
become more refractory lately, with virtual file systems a particular
concern.
-rob
On Tue, Feb 23, 2021 at 4:11 AM Will Senn <will.senn@gmail.com> wrote:
> On 2/22/21 10:41 AM, Jay Logue via TUHS wrote:
>
> Lately, I've been playing around in v6 unix and mini-unix with a goal of
> better understanding how things work and maybe doing a little hacking. As
> my fooling around progressed, it became clear that moving files into and
> out of the v6 unix world was a bit tedious. So it occurred to me that
> having a way to mount a v6 filesystem under linux or another modern unix
> would be kind of ideal. At the same time it also occurred to me that
> writing such a tool would be a great way to sink my teeth into the details
> of old Unix code.
> ...
> As I expected, this was a fun and very educational project to work on. It
> forced me to really understand what was going in the kernel (and to really
> pay attention to what Lions was saying). It also gave me a little view
> into what it was like to work on Unix back in the day. Hopefully someone
> else will find my little self-education project useful as well.
>
> --Jay
>
> Yay! I for one, will appreciate this!
>
> Will
>
[-- Attachment #2: Type: text/html, Size: 1934 bytes --]
next prev parent reply other threads:[~2021-02-22 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 16:41 Jay Logue via TUHS
2021-02-22 17:10 ` Will Senn
2021-02-22 20:13 ` Rob Pike [this message]
2021-02-22 20:40 ` Anthony Martin
2021-02-24 16:01 ` arnold
2021-02-24 17:40 ` Brad Spencer
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='CAKzdPgxTGTLzmimQped8h-HS=raWh1=Tk2R1Mj51Xsk1abE4=Q@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@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).