From: Paul Ruizendaal via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix V8 Chaosnet, any takers?
Date: Fri, 15 Jul 2022 10:51:34 +0200 [thread overview]
Message-ID: <E207B623-6BF7-43EF-ACBE-6E096D357B2A@planet.nl> (raw)
> Message: 6
> Date: Thu, 14 Jul 2022 17:51:39 +0000
> From: segaloco <segaloco@protonmail.com>
>
> Given V8 being rebased on 4(.1?)BSD, I suspect the path of least resistance would be to just start grafting V8 code onto the working 4.1BSD.
I doubt that V8 is "rebased on 4(.1?)BSD": in my understanding it ported some code from 4xBSD, but it is a different code base.
As I currently understand it, the V8 kernel:
- is a further development from 32V
- retains the code organisation of the V5..32V versions
- adds virtual memory code from BSD
- adds select() from BSD
and then adds all the V8 innovation on top of that (streams, file system switch, virtual proc file system, networking, remote file system, support for the Blit terminal, etc.)
In particular in the area of networking the V8 kernel is organised quite differently from the 4xBSD kernel, including the Chaosnet driver (i.e. it is streams based).
Paul
next reply other threads:[~2022-07-15 8:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 8:51 Paul Ruizendaal via TUHS [this message]
2022-07-15 11:55 ` [TUHS] ECU Ron Natalie
-- strict thread matches above, loose matches on Subject: below --
2022-07-18 17:07 [TUHS] Re: Unix V8 Chaosnet, any takers? Noel Chiappa
2022-07-17 23:39 Noel Chiappa
2022-07-18 1:01 ` Ron Natalie
2022-07-16 20:02 Paul Ruizendaal
2022-07-16 15:51 Noel Chiappa
2022-07-16 17:02 ` Warner Losh
2022-07-15 10:25 Noel Chiappa
2022-07-15 11:53 ` Theodore Ts'o
2022-07-16 6:59 ` Lars Brinkhoff
2022-07-14 11:08 [TUHS] " Lars Brinkhoff
2022-07-14 16:37 ` [TUHS] " John Floren
2022-07-14 17:00 ` Lars Brinkhoff
2022-07-14 17:51 ` segaloco via TUHS
2022-07-14 18:19 ` Ron Natalie
2022-07-14 20:32 ` Tom Teixeira
2022-07-14 20:39 ` Ron Natalie
2022-07-15 0:33 ` Grant Taylor via TUHS
2022-07-15 4:29 ` Erik E. Fair
2022-07-14 19:36 ` Lars Brinkhoff
2022-07-14 21:50 ` segaloco via TUHS
2022-07-16 6:38 ` Lars Brinkhoff
2022-07-16 14:05 ` Warner Losh
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=E207B623-6BF7-43EF-ACBE-6E096D357B2A@planet.nl \
--to=tuhs@tuhs.org \
--cc=pnr@planet.nl \
/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).