From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Multiseat -- LTSP?
Date: Tue, 31 Jan 2012 00:49:35 +0000 [thread overview]
Message-ID: <EB8F44ED-EBD8-4EF6-BABC-59E2FCA2CDE5@stellar.eclipse.co.uk> (raw)
In-Reply-To: <CAN0CFw2GCkD33GONu6nSMkaNbRwDpn43Ag=c-KCU5tm-=pHnPw@mail.gmail.com>
On 30 January 2012, at 17:41, Grant wrote:
>> ...
>> Can you rely on Xorg devs to ensure that they are not going to break your
>> multiseat system in the future?
>
> Maybe I'm wrong, but I don't know why there would be (much) more
> likelihood of regression with Xorg multiseat than with anything else,
> including LTSP and all of its dependencies.
Because fewer people are testing it.
You can get low-powered Linux systems for $100 or $150 - either a little MIPs ShivaPlug or (I guess) a secondhand atom nettop (Acer Revo).
If you save 2 hours per machine by using a standard and common thinclient configuration, then the hardware has paid for itself.
If you have to employ a Linux sys admin to help you fix a complicated problem with Xorg multiseat, then it will run you at least $100 or $150 for those 2 hours. That's how you should be valuing your own time, too.
Stroller.
next prev parent reply other threads:[~2012-01-31 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 5:26 [gentoo-user] Multiseat -- LTSP? Grant
2012-01-29 12:02 ` Mick
2012-01-29 23:29 ` Grant
2012-01-30 9:19 ` Helmut Jarausch
2012-01-30 17:19 ` Grant
2012-01-30 10:35 ` Mick
2012-01-30 17:41 ` Grant
2012-01-31 0:49 ` Stroller [this message]
2012-01-31 2:53 ` Grant
2012-01-31 19:46 ` Grant
2012-02-03 15:34 ` [gentoo-user] " James
2012-02-03 16:32 ` [gentoo-user] " Stroller
2012-02-03 18:24 ` [gentoo-user] " Grant
2012-02-03 18:35 ` Michael Mol
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=EB8F44ED-EBD8-4EF6-BABC-59E2FCA2CDE5@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox