From: P.A.Osborne@ukc.ac.uk (P.A.Osborne)
Subject: [TUHS] Re: Porting Unix v6 to i386
Date: Mon, 4 Feb 2002 11:48:28 +0000 [thread overview]
Message-ID: <20020204114828.F18315@apple.ukc.ac.uk> (raw)
In-Reply-To: <200202041057.g14AvTs78831@minnie.tuhs.org>; from wkt@minnie.tuhs.org on Mon, Feb 04, 2002 at 08:57:28PM +1000
On Mon, Feb 04, 2002 at 08:57:28PM +1000, Warren Toomey wrote:
> Well, seeing as though Paul referred to me (see below), I'll throw my
> own $0.02 in. I'd recommend V7 for several reasons:
>
> - it's more portable
> - the flavour of C used is more modern
> - it's got more useful applications (yacc etc.)
> - you get the stdio library
> - one last thing, there were some awful race conditions and
> bogosities in V6 that just had to be fixed. See the
> `50 bugs' tape, and also Dennis' own admission about
> 6th Edition savu/retu at
> http://cm.bell-labs.com/cm/cs/who/dmr/odd.html
Hmmm. I am starting (I have to admit) to lean towards V7 as my thoughts
continue. I hadn't seen the "50 bugs" tape - although I believe I have
a copy archived somewhere. Must take a gander at some point and mount
it on the emulator.
> > Pondering just this over the weekend has left me wondering whether
> > MiniUnix would be a better initial place to start - as its essentially
> > V6, but without memory management or pipes. Which as a starting point
> > for the experiment may be an easier place to start.
>
> You could port that in a short amount of time, and treat it as a
> warming-up exercise!
Thats what I was thinking - it also alows a honing of very rusty skills,
and also allows building of tools that will be needed on the way.
Also I dont suppose that anyone has the tarred up source for MiniUnix
they could mail me? (It just saves me from extracting it out of
the tape/disk images the hard way).
One thing I am undecided about though is this:
Should the source be converted to from pre K&R C to ANSI C for
the sake of updating the system to run on a newer architecture (though
not much since the PC was released in 1980 and we only need 16bits).
OR
Should we attempt to provide a new compiler (or preparser) which will
take the pre K&R C and just compile it as is?
I have to admit the above comments are straight off the top of my head,
and haven't been considered at any length and indeed should be (over
several pints of ale).
> > Also as a sideline, I don't know how the list owner of this list
> > feels about this discussion potentially swamping the list.
>
> I think the list needs some traffic :-) It might be worth setting up
> a list for the e-mails between co-developers, but also to have periodic
> status reports and questions sent to this list.
OK once we get to that stage (I am still reading up and checking out
the different architectures at present - so me writing code
isnt going to happen yet until I at least have been over the printed source
with a red pen) which could be a while, I guess either I can run
a list here at UKC or maybe Warren would like to put one up at Minnie?
Regards
Paul
next prev parent reply other threads:[~2002-02-04 11:48 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16WjYq-0005RL-00@mercury.ukc.ac.uk>
2002-02-04 9:33 ` P.A.Osborne
2002-02-04 10:57 ` Warren Toomey
2002-02-04 11:48 ` P.A.Osborne [this message]
2002-08-22 20:52 [TUHS] " russ
2002-08-22 21:23 ` Peter Jeremy
2002-08-22 23:56 ` Warren Toomey
[not found] <20020707154509.A172@muppet.labs.de>
2002-07-08 1:09 ` [TUHS] " Warren Toomey
2002-07-08 10:33 ` Sven Dehmlow
2002-07-08 13:52 ` SZIGETI Szabolcs
2002-07-08 14:15 ` Warren Toomey
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 17:02 Mike Haertel
2002-06-11 22:31 ` Peter Jeremy
2002-06-11 22:52 ` Mike Haertel
2002-06-05 18:49 Ian King
2002-06-06 7:07 ` Szigeti Szabolcs
2002-06-06 10:20 ` Warren Toomey
[not found] <200206050222.g552MHm88208@minnie.tuhs.org>
2002-06-05 11:54 ` John Chung
2002-06-04 11:53 Szigeti Szabolcs
2002-06-04 23:34 ` Warren Toomey
2002-02-15 0:07 John Holden
2002-02-04 22:23 norman
[not found] <20020131102843.C19170@apple.ukc.ac.uk>
[not found] ` <200201311847.g0VIlHj41858@ducky.net>
2002-02-01 10:24 ` P.A.Osborne
2002-01-30 23:51 Grant Maizels
2002-01-30 21:52 John Holden
[not found] <no.id>
2002-01-30 1:57 ` Aaron J. Grier
2002-01-30 9:18 ` P.A.Osborne
2002-01-30 18:00 ` Sven Dehmlow
2002-01-30 19:50 ` Johnny Billquist
2002-01-30 21:40 ` Michael Davidson
2002-01-31 10:26 ` P.A.Osborne
2002-01-31 18:51 ` Johnny Billquist
2002-02-01 10:27 ` P.A.Osborne
2002-01-31 19:04 ` Mike Haertel
2002-01-30 19:52 ` Mike Haertel
2002-01-30 20:54 ` M. Warner Losh
2002-01-30 22:47 ` Greg Lehey
2002-03-03 12:51 ` Cyrille Lefevre
2002-03-03 20:14 ` Peter Jeremy
2002-03-03 20:46 ` Tim Shoppa
2002-03-03 21:07 ` Peter Jeremy
2002-01-31 9:18 ` Lauri Aarnio
2002-01-31 11:00 ` P.A.Osborne
2002-01-31 16:09 ` Sven Dehmlow
2002-01-31 18:45 ` Lauri Aarnio
2002-02-01 0:42 ` Greg Lehey
2002-02-04 22:12 ` Michael Davidson
2002-02-05 10:42 ` P.A.Osborne
2002-02-06 16:36 ` Jeffrey S. Sharp
2002-02-07 10:23 ` P.A.Osborne
2002-01-30 22:44 ` Greg Lehey
2002-02-14 22:30 ` Aaron J. Grier
2002-02-15 3:08 ` Peter Jeremy
2002-02-15 8:08 ` Lars Brinkhoff
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=20020204114828.F18315@apple.ukc.ac.uk \
--to=p.a.osborne@ukc.ac.uk \
/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).