From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: ux as a minicomputer ?
Date: Sat, 13 Apr 2002 19:35:30 -0700 [thread overview]
Message-ID: <20020413193530.D1735@pegasys.ws> (raw)
In-Reply-To: <E16wSh5-0000ue-00@the-village.bc.nu> <3CB88713.4070209@zytor.com>
On Sat, Apr 13, 2002 at 12:29:23PM -0700, H. Peter Anvin wrote:
> Alan Cox wrote:
> >
> >>This is fundamentally the problem with these kinds of schemes -- they
> >>get outcompeted on price and availability by the massmarket items.
> >>This is part of the very attraction of Linux -- it's running Unix on
> >>stock, cheap, hardware.
> >
> > The hardware is now massmarket - otherwise I'd agree wholeheartedly. Video
> > cards are cheap, USB2.0 cards have 4 root bridges per card.
> >
>
> Oh yes, but the *expensive* part of the machine -- the multiprocessor
> box -- isn't.
>
> Also, when using massmarket systems of more than 2 or 3 monitors you
> start having cabling problems. VGA connectors aren't impedance matched
> and cause nasty reflections at high resolutions, so they don't extend
> well. I guess digital video is coming, but is not yet mass market.
>
> -hpa
>
A single 1000Mhz+ CPU is overkill for most desktop users.
Most medium to large workplaces are vast cubicle farms. Put
one box at the intersection of 4 cubes...bingo 2meter VGA
cables reach fine and you get 1/4th the maintenance, 1/4 the
network drops, etc. This would even be advantagious for two desks
side-by-side or back-to-back.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2002-04-14 2:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 15:46 linux as a minicomputer ? John P. Looney
2002-04-11 16:43 ` Dr. David Alan Gilbert
2002-04-11 16:49 ` Vojtech Pavlik
2002-04-11 17:07 ` Ed Sweetman
2002-04-11 17:12 ` Vojtech Pavlik
[not found] ` <3CB69032.D332FA51@aitel.hist.no>
2002-04-12 8:08 ` Vojtech Pavlik
2002-04-11 17:09 ` Dr. David Alan Gilbert
2002-04-11 17:13 ` Vojtech Pavlik
2002-04-11 17:49 ` John P. Looney
2002-04-11 17:59 ` Rene Rebe
2002-04-11 18:46 ` James Simmons
2002-04-11 19:06 ` Vojtech Pavlik
2002-04-12 7:41 ` Helge Hafting
2002-04-12 8:09 ` Vojtech Pavlik
2002-04-11 18:01 ` James Simmons
2002-04-11 19:07 ` Vojtech Pavlik
2002-04-13 19:03 ` Alan Cox
2002-04-11 19:45 ` H. Peter Anvin
2002-04-11 20:05 ` James Simmons
2002-04-12 7:31 ` Helge Hafting
2002-04-13 18:56 ` Alan Cox
2002-04-13 19:29 ` H. Peter Anvin
2002-04-13 19:37 ` Richard Gooch
2002-04-13 19:40 ` H. Peter Anvin
2002-04-13 19:49 ` Richard Gooch
2002-04-13 22:08 ` J.A. Magallon
2002-04-13 23:46 ` Richard Gooch
2002-04-13 19:51 ` Alan Cox
2002-04-13 19:36 ` H. Peter Anvin
2002-04-14 4:30 ` Bill Davidsen
2002-04-14 13:45 ` Alan Cox
2002-04-14 16:44 ` Sten
2002-04-14 16:50 ` Dr. David Alan Gilbert
2002-04-14 20:20 ` H. Peter Anvin
2002-04-15 16:05 ` Thomas Molina
2002-04-15 0:37 ` Rob Landley
2002-04-15 8:46 ` Helge Hafting
2002-04-15 9:10 ` Alan Cox
[not found] ` <3CBB522C.8070704@bcgreen.com>
2002-04-15 18:09 ` Rob Landley
2002-04-14 2:35 ` jw schultz [this message]
[not found] <1018751811.22396@whiskey.enposte.net>
2002-04-14 6:16 ` ux " Stuart Lynne
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=20020413193530.D1735@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.