From: James R Bruce <bruce+@andrew.cmu.edu>
To: linux-kernel@vger.rutgers.edu
Cc: linux-kernel@vger.rutgers.edu
Subject: [OT] Re: fork bomb:the come back
Date: Tue, 28 Dec 1999 14:32:39 -0500 (EST) [thread overview]
Message-ID: <QsOF1LG00Uw70MI5g0@andrew.cmu.edu> (raw)
In-Reply-To: <Pine.LNX.4.05.9912281334570.129-100000@ns.snowman.net>
Excerpts from internet.computing.linux-kernel: 28-Dec-99 Re: fork
bomb:the come back by Stephen Frost@mail.snowm
> There was a Coke machine at a university somewhere that would
tell you
> how many cans and whatnot were left at one point or another, I seem to
recall.
> Yes, over the internet (Or that may have been arpanet, not sure. :) ).
That would be Carnegie Mellon's CS department coke machine. Sadly, it
has been disconnected. There is a coffee machine online now however:
mrcoffee.res.cmu.edu
I think the general argument trying to be made is that there are a lot
of machines that are not, and will never be, connected to the internet.
The exact numbers don't matter, but it is worth noting that improvements
that only apply to non-connected machines can still be quite useful to
many.
I would still guess that most embedded systems aren't connected to the
internet; for every new machine on the internet, there's probably two
more new ones that aren't; The sheer number of computers in other words,
is growing faster than the number online. Also, a lot of such systems
are networked but not connected to the outside world; since they tend to
be proprietary and often trusted (e.g. they lack internal security).
- Jim Bruce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~1999-12-28 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.05.9912281334570.129-100000@ns.snowman.net>
1999-12-28 19:32 ` James R Bruce [this message]
1999-12-28 23:24 ` Brandon S. Allbery KF8NH
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=QsOF1LG00Uw70MI5g0@andrew.cmu.edu \
--to=bruce+@andrew.cmu.edu \
--cc=linux-kernel@vger.rutgers.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
all inboxes | Powered by JetHome®