From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] Mach for i386 / Mt Xinu or other
Date: Sun, 19 Feb 2017 17:29:54 -0800 [thread overview]
Message-ID: <1487554194.778935.886229480.27F99937@webmail.messagingengine.com> (raw)
In-Reply-To: <CAC20D2PraTNVKRTz0x1wJ1YUkeqbHVp-vd647PKAEsxAMuHGGg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4105 bytes --]
On Sun, Feb 19, 2017, at 13:19, Clem Cole wrote:
>
>
> On Sun, Feb 19, 2017 at 1:20 AM,
> <jsteve at superglobalmegacorp.com> wrote:
>> True, but It’s not 4.3 BSD … I was hoping for something vintage of
>> the era, just as Solaris 11 is SYSV, but it’s nothing like SYSVr2 on
>> the VAX….
> Fair enough... the Mt Xinu version is pretty much the CMU version
> unadorned. Which mean that it is a 4.3BSD kernel, with the BSD based
> MMU code ripped out and replaced with the CMU code, and the Mach
> interfaces (ney RIG - Mach's and Accent's predecessor) messaging
> system spliced into it; then the whole mess was built back up using a
> 4.3BSD user space (and on top of the i386, an Intel developed boot
> system - which is a different story I'll not repeat at this time - but
> thankfully was common to all the UNIX systems of the day because Intel
> developed and make it available to community at large).
>
> The other option which I would suggest to look at is the OSF/1 mk for
> the i386 (monolithic) about version 3x which as I said forked off the
> Alpha line and a couple of other systems. The i386 version of OSF/1
> supports the same chips (i386/i486/Pentium) at the CMU version, it
> also comes with more HW device support (disk, tape, network, display
> *et al*), than the CMU/Mt Xinu version -- including most importantly
> SCSI support by default, which is why is might be a little easier to
> work on today's HW and VMs. When I last used it, it lacked USB
> support; but that was being worked on around the time I started doing
> other things so even that might even be available today.
>
> FWIW: OSF/1 also started with 4.3BSD userspace, but it had a lot of
> work done to it to updating it - adding the Sys V commands that BSD
> lacked those days and adding Sys V options to many commands. * i.e.*
> its user space is a tad more "complete" / "wider" than pure 4.3BSD and
> again makes it a little easier to complete.
>
> Note that the user space commands from the mk would become the basis
> for Tru64, HP/UX and later versions of AIX. And also the OSF/1
> version will have better Graphics, Motif and a much better GUI options
> all around that Mt Xinu, which alone may be it easier to work.
>
>
> As I also said elsewhere, the uK or Research Institute (RI) version is
> a tad more fun to play with. It's a real kernel architecture moving
> things like file systems *et al* in user space. But you can do do
> things like start up multiple system interfaces. LCC had their
> DOS/Win95 interface was actually developed running instead of as a VM
> like it did for the basic mk code, but in as "second server" but I do
> not think they ever sold it. The other thing the RI never did, was
> the uk still has the pager and all the networking code in the kernel,
> so the uk, is hardly 'micro' in size.
>
> There is a OSF Version 4 and maybe even version 5 (I've forgotten, if
> some one remembers - please correct me). The OSF RI folks were trying
> to rewrite it a bit in C++ as I recall, again this part of the UI vs
> OSF wars of the day and Chorus has rewritten there version from Pascal
> to C++, and IIRC the RI was trying to counter that. I don't remember
> if that version of the uk ever saw the light of day.
>
>
>
>
> Anyway, no matter which is the 3 code streams you pick, Mt Xinu, OSF/1
> mk or uk one hardest problems for today will be that the compiler is
> of course extremely old by today's standards, and you are probably
> going to run it some walls in that area faster than you might think.
> That said, if you are willing to deal with the compiler as it comes,
> non of them should be very high, or hard to get clear, but some are
> likely to take some work.
>
> Have fun and good luck and let us know if you can get any of these
> running.
>
> Clem
Has any mtXinu stuff survived to be archives?
--
Cory Smelosky
b4 at gewt.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170219/412abed1/attachment.html>
next prev parent reply other threads:[~2017-02-20 1:29 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 7:28 [TUHS] Mushi and Bagu Rudi Blom
2017-02-16 9:36 ` jsteve
2017-02-16 10:42 ` Nick Downing
2017-02-16 13:49 ` Rudi Blom
2017-02-17 11:30 ` [TUHS] Mach for i386 / Mt Xinu or other jsteve
2017-02-17 14:22 ` Clem Cole
2017-02-17 16:13 ` Chet Ramey
2017-02-17 14:29 ` Clem Cole
2017-02-17 17:23 ` Warner Losh
2017-02-18 22:25 ` Nemo
2017-02-19 6:20 ` jsteve
2017-02-19 7:01 ` Steve Nickolas
2017-02-19 13:46 ` Jason Stevens
2017-02-19 15:44 ` Larry McVoy
2017-02-20 18:14 ` Joerg Schilling
2017-02-20 22:24 ` Larry McVoy
2017-02-20 23:16 ` Steve Johnson
2017-02-20 23:18 ` Larry McVoy
2017-02-20 23:25 ` Steve Johnson
2017-02-20 23:20 ` Steve Nickolas
2017-02-21 0:12 ` Wesley Parish
2017-02-21 1:05 ` Steve Nickolas
2017-02-21 10:30 ` Joerg Schilling
2017-02-21 13:47 ` Random832
2017-02-21 15:18 ` Joerg Schilling
2017-02-21 15:54 ` Diomidis Spinellis
2017-02-21 16:38 ` Cory Smelosky
2017-02-21 16:48 ` Joerg Schilling
2017-02-21 16:32 ` Random832
2017-02-21 16:55 ` Joerg Schilling
2017-02-21 17:10 ` Dan Cross
2017-02-21 19:44 ` Joerg Schilling
2017-02-21 21:17 ` Dan Cross
2017-02-21 21:37 ` Larry McVoy
2017-02-22 8:57 ` jsteve
2017-02-22 9:56 ` Michael Kjörling
2017-02-22 10:26 ` jsteve
2017-02-22 10:29 ` Joerg Schilling
2017-02-19 21:19 ` Clem Cole
2017-02-20 0:29 ` Nick Downing
2017-02-20 1:58 ` Clem Cole
2017-02-20 1:29 ` Cory Smelosky [this message]
2017-02-19 22:59 ` Derek Fawcus
2017-02-17 15:47 Atindra Chaturvedi
2017-02-17 16:55 Noel Chiappa
2017-02-17 20:04 ` Clem Cole
2017-02-19 5:48 Jason Stevens
2017-02-20 6:38 Rudi Blom
2017-02-21 4:16 Doug McIlroy
2017-02-21 12:02 Noel Chiappa
2017-02-21 12:24 ` Steffen Nurpmeso
2017-02-21 12:57 ` Michael Kjörling
2017-02-21 15:02 ` Clem Cole
2017-02-22 1:50 ` Dan Cross
2017-02-22 2:25 ` Steve Nickolas
2017-02-22 3:11 ` Clem Cole
2017-02-22 4:07 ` Dan Cross
2017-02-22 4:17 ` Larry McVoy
2017-02-23 15:31 ` Nemo
2017-02-23 16:00 ` Clem Cole
2017-02-23 16:50 ` Nemo
2017-02-23 22:02 ` Dave Horsfall
2017-02-24 1:30 ` Clem Cole
2017-02-24 20:54 ` Dave Horsfall
2017-02-24 1:01 ` Jason Stevens
2017-02-22 10:16 ` jsteve
2017-02-21 15:15 ` Chet Ramey
2017-02-21 16:47 ` Larry McVoy
2017-02-21 18:58 ` Clem Cole
2017-02-21 19:21 ` Larry McVoy
2017-02-21 20:17 ` Clem Cole
2017-02-21 20:28 ` Steve Nickolas
2017-02-21 20:32 ` Larry McVoy
2017-02-21 22:58 ` Wesley Parish
2017-02-22 1:19 ` Clem Cole
2017-02-22 9:00 ` jsteve
2017-02-22 0:52 ` Andy Kosela
2017-02-22 1:04 ` ron minnich
2017-02-22 1:33 ` jason-tuhs
2017-02-22 3:18 ` Larry McVoy
2017-02-22 3:45 ` ron minnich
2017-02-22 4:06 ` Larry McVoy
2017-02-22 4:11 ` Larry McVoy
2017-02-21 16:25 Noel Chiappa
2017-02-21 21:49 Noel Chiappa
2017-02-21 23:10 ` Nick Downing
2017-02-21 23:14 ` Arthur Krewat
2017-02-22 1:22 Rudi Blom
2017-02-22 3:08 ` Cory Smelosky
2017-02-22 3:51 Rudi Blom
2017-02-26 18:33 Norman Wilson
2017-02-28 20:26 ` Dave Horsfall
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=1487554194.778935.886229480.27F99937@webmail.messagingengine.com \
--to=b4@gewt.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).