From: tfb@cley.com (Tim Bradshaw)
Subject: [TUHS] Re: TUHS digest, Vol 1 #145 - 2 msgs
Date: Fri, 18 Apr 2003 02:10:33 +0100 [thread overview]
Message-ID: <16031.20617.522109.587474@cley.com> (raw)
In-Reply-To: <20030417034500.GK26145@work.bitmover.com>
* Larry McVoy wrote:
> Right. Joy left Berkeley and joined Sun and the work got done at Sun.
> I'm pretty sure that SunOS 4.0 was the first release with mmap working
> as it was described.
yes, i think so. I think 3.x had a special-purpose thing which would
only map devices (and maybe only framebuffers...)
> I was at Sun for the 4.1 release; 4.0 was the new
> VM system, and it wasn't "new" like "we changed some stuff", it was new
> as in everything was rewritten.
Or alternatively "new" as in "didn't work very well yet". I remember
there were things you could do (and do quite easily) in 4.0.1 and
4.0.3 which left the system in a state where it thought it had several
K of memory for paging (and a lot of unused file buffers).
--tim
next prev parent reply other threads:[~2003-04-18 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304170249.h3H2nQJ8001840@minnie.tuhs.org>
2003-04-17 3:45 ` Larry McVoy
2003-04-18 1:10 ` Tim Bradshaw [this message]
2003-04-18 1:35 ` Larry McVoy
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=16031.20617.522109.587474@cley.com \
--to=tfb@cley.com \
/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).