Hej Mats,
512mb ram? 256 for cache? I seriously doubt I need that much.
I wouldn't bet on it - we've got some older P1 thin clients with only a
few MB RAM. Sure, they boot. Sure, the user may log in sometimes.
But sooner or later those terminals will crash if not helped by swap
memory on the
2007/2/8, Eilert [EMAIL PROTECTED]:
Hej Mats,
512mb ram? 256 for cache? I seriously doubt I need that much.
I wouldn't bet on it - we've got some older P1 thin clients with only a
few MB RAM. Sure, they boot. Sure, the user may log in sometimes.
But sooner or later those terminals will
Mats Lundqvist schrieb:
2007/2/8, Eilert [EMAIL PROTECTED]:
Hej Mats,
512mb ram? 256 for cache? I seriously doubt I need that much.
I wouldn't bet on it - we've got some older P1 thin clients with only a
few MB RAM. Sure, they boot. Sure, the user may log in sometimes.
But sooner or later
On Thu, 08 Feb 2007 11:59:09 -, Eilert [EMAIL PROTECTED] wrote:
In ltsp.conf just set USE_NBD_SWAP = Yes
and make sure ltspswapd is running
--
From Ben Green
-
Using Tomcat but need to do more? Need to support web
2007/2/7, [EMAIL PROTECTED] [EMAIL PROTECTED]:
On Wednesday 07 February 2007 05:09,
[EMAIL PROTECTED] wrote:
I've been looking into thin client tech, WinTS, Thinstation, NX etc...
And I've actually used Thinstation and Win TS.
But I can't say that I've really got a grip on how LTSP
I am taking the fat client approach:
Athelon M 2800+
1GB RAM
17 LCD
All apps local
Total client cost is $300US. Some advantages I have found.
Sound is pitifully easy.
Server is just a client with drive(s) added.
Users have full applications
On Wednesday 07 February 2007 21:24,
[EMAIL PROTECTED] wrote:
Running firefox as a local app is expensive!
IMHO you need 512M ram (256M for firefox to cache in plus the ram to
run the thin client and firefox app, java, flash etc)
You need a processor to do the work, so 200MHz
Hi
I've been looking into thin client tech, WinTS, Thinstation, NX etc...
And I've actually used Thinstation and Win TS.
But I can't say that I've really got a grip on how LTSP 4.2/5 works.
From what I can gather, LTSP seems more like something aimed at
diskless fat clients?
Booting from PXE
Mats Lundqvist schrieb:
Hi
Hej Mats,
I've been looking into thin client tech, WinTS, Thinstation, NX etc...
And I've actually used Thinstation and Win TS.
But I can't say that I've really got a grip on how LTSP 4.2/5 works.
From what I can gather, LTSP seems more like something aimed
On 06/02/07, Eilert [EMAIL PROTECTED] wrote:
Mats Lundqvist schrieb:
Hi
Hej Mats,
I've been looking into thin client tech, WinTS, Thinstation, NX etc...
And I've actually used Thinstation and Win TS.
But I can't say that I've really got a grip on how LTSP 4.2/5 works.
From
Mats-
To add what the others had said about how LTSP works: every thin client
(eg Wyse WinTerm) that you purchase has to have some sort of operating
system on it to operate. This generally is just enough OS to initialize
the hardware, initialize the graphics mode, provide a local
I've noticed that when running with thinstation, I can max out the
switch and really push the server when many users are running java or
flash, and is for me a real show stopper.
I can't speak for Flash, but for Java Swing applications and especially
Java apps that use the Java2D library,
On Wednesday 07 February 2007 05:09,
[EMAIL PROTECTED] wrote:
I've been looking into thin client tech, WinTS, Thinstation, NX etc...
And I've actually used Thinstation and Win TS.
But I can't say that I've really got a grip on how LTSP 4.2/5 works.
From what I can gather, LTSP seems more
Having said all that the current audio is a mess. So local app to support
audio apps is quite nice.
Lots of people have made audio work to some extent.
James-
I recall at one time when ALSA was superceding OSS that in theory, a
server-side ALSA driver could be made network-transparent
14 matches
Mail list logo
