From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OT: linux complexity trends
Date: Mon, 26 Nov 2001 22:37:38 +0000 [thread overview]
Message-ID: <20011126223743.C358919A41@mail.cse.psu.edu> (raw)
>>Ipaq's, for example, have very limited memory but can have a
one of the nice things about wandering in after microsoft
on any given platform is that `limited memory' means something
quite different from what it might mean elsewhere.
for instance, the newer iPAQs seem to be 64mbyte RAM and
32 mbyte flash (minimum).
next reply other threads:[~2001-11-26 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 22:37 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-26 19:01 presotto
2001-11-26 17:56 presotto
2001-11-26 18:48 ` Dan Cross
2001-11-27 10:16 ` Thomas Bushnell, BSG
2001-11-26 14:54 rob pike
2001-11-26 17:40 ` Ronald G Minnich
2001-11-26 18:24 ` Alexander Viro
2001-11-26 14:42 forsyth
2001-11-26 14:00 presotto
2001-11-26 13:13 forsyth
2001-11-26 18:36 ` Dan Cross
2001-11-26 19:45 ` Ronald G Minnich
2001-11-26 12:41 steve.simon
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=20011126223743.C358919A41@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).