From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 2c/2l make sense, but why 1c/1l?
Date: Wed, 24 Feb 2021 23:29:26 +0000 [thread overview]
Message-ID: <CAOw7k5ime_fBQ9hTZGbCwEqO=QBpS=hJnBOna7_X6geBibqiCg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5iSNue4=YH7WMS99E9eJai0ybF_oZrEtFzc2er4Bzw9_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
To be fair, I probably should convert my machine with lots of disks with
lots of historical partitions into a single tree with the contents just as
subdirectories.
It's not as though anyone's going to use them as images ever again. They
only ended up that way because the originals were in strange formats on
increasingly dodgy devices, and it was easier just to copy the partitions
across to partitions of newer bigger drives.
As an aside, it still amuses me that VN's worm jukebox would now fit on an
SD card that I could easily lose.
On Wed, Feb 24, 2021 at 11:26 PM Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> I think they might have been there for some other reason and then was used
> for Inferno, which they somewhat had going on a Palm Pilot in some form
> (not necessarily as the native kernel).
> If I waded through a ton of archive material I could probably find the
> latter, to see what it was, but I'm not sure it's really worthwhile now.
>
> On Wed, Feb 24, 2021 at 8:16 PM Joseph Stewart <joseph.stewart@gmail.com>
> wrote:
>
>> Charles could probably answer this better than me, but weren't the 68k
>> compilers made to support Inferno?
>> -joe
>>
>> On Mon, Feb 22, 2021 at 11:18 PM <rt9f.3141@gmail.com> wrote:
>> >
>> > Hello,
>> >
>> > I'm wondering about the history of the 68000 compiler/tools. Support
>> for the 68020 makes sense, it had an MMU, but 68000 did not. And it had
>> some design flaws that prevented it from working correctly with the
>> external MMU, the 68451. So why does/did Plan 9 have a 68000 compiler?
>> Did Plan 9 ever run on an MMU-less 68000?
>> >
>> > thx.
>> > 9fans / 9fans / see discussions + participants + delivery options
>> Permalink
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf34475f1bb69674a-Mf5d48b33b42aa6f6e483a745
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3631 bytes --]
next prev parent reply other threads:[~2021-02-24 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 7:17 rt9f.3141
2021-02-23 10:29 ` Steve Simon
2021-02-24 19:59 ` Anthony Sorace
2021-02-24 20:14 ` Joseph Stewart
2021-02-24 23:26 ` Charles Forsyth
2021-02-24 23:29 ` Charles Forsyth [this message]
2021-02-25 1:02 ` Joseph Stewart
2021-02-25 11:39 ` Ethan Gardener
2021-02-24 21:49 ` Skip Tavakkolian
2021-02-28 21:12 ` rt9f.3141
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='CAOw7k5ime_fBQ9hTZGbCwEqO=QBpS=hJnBOna7_X6geBibqiCg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).