The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Revisiting 6th Edition: rxv64
Date: Mon, 1 May 2023 19:34:51 -0700	[thread overview]
Message-ID: <20230502023451.GK29744@mcvoy.com> (raw)
In-Reply-To: <CAC20D2OEU=gp3X2Uwe6z=ZE+2i6dS4S=TPrWM1M8T5D-QbrBRA@mail.gmail.com>

I have to say I'm impressed.  This is way beyond what I could do at my
age.  I think it is awesome that younger people are picking up what 
Unix meant and redoing it.

On Mon, May 01, 2023 at 09:55:26PM -0400, Clem Cole wrote:
> Very cool
> 
> On Mon, May 1, 2023 at 9:49 PM Dan Cross <crossd@gmail.com> wrote:
> 
> > I've mentioned tangentially this a few times, but over the weekend I
> > finally got around to dusting off the code and getting it running:
> > https://github.com/dancrossnyc/rxv64.git
> >
> > rxv64 is a rewrite of MIT's xv6, which in turn, reimagines 6th Edition
> > as a purely pedagogical system, implemented in ISO C for 32-bit SMP
> > x86 machines.
> >
> > Building on xv6, rxv64 is implemented in Rust and targets 64-bit
> > x86_64. It works well enough to boot up, run a shell, and run
> > commands, but it doesn't really have much of a userland at present.
> >
> > I started this as a pedagogical tool, being something that one could
> > point working engineers at as an example of a "real" operating system
> > implemented on real hardware in Rust. The code could surely be made
> > safer and more comprehensible, but cycles are short at present, and
> > it's better to just get it out there.
> >
> > Have fun.
> >
> >         - Dan C.
> >
> -- 
> Sent from a handheld expect more typos than usual

-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2023-05-02  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02  1:48 [TUHS] " Dan Cross
2023-05-02  1:55 ` [TUHS] " Clem Cole
2023-05-02  2:34   ` Larry McVoy [this message]
2023-05-02  3:05     ` Jason Bowen
2023-05-02 12:19     ` Dan Cross

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=20230502023451.GK29744@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@tuhs.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).