> Message: 1
> Date: Mon, 16 Jul 2007 08:51:26 +0200
> From: Rolf-Werner Eilert <[EMAIL PROTECTED]>
> Subject: [Ltsp-discuss] DHCP fails on Suse 10.2/LTSP 4.2
> To: ltsp-discuss@lists.sourceforge.net
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>
On 7/13/07, Anthony M Simonelli <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-07-13 at 11:24 -0500, bob wrote:
> > I bought a t5135 to test in my ltsp 4.2 network. Seems that is only
> > works with Vesa. Am I wrong?
> >
> > The specs say "VIA S3 Graphics". I tried three different s3 variations
> > but
Verner Kjærsgaard schrieb:
> Mandag 16 juli 2007 08:51 skrev Rolf-Werner Eilert:
>> Hi everyone,
>>
>> I've got a new server here to be equipped with LTSP. There is a Suse
>> 10.2 running on this machine. I can log in via X from my terminal to the
>> old server like from a big client.
>>
>> After s
Mandag 16 juli 2007 08:51 skrev Rolf-Werner Eilert:
> Hi everyone,
>
> I've got a new server here to be equipped with LTSP. There is a Suse
> 10.2 running on this machine. I can log in via X from my terminal to the
> old server like from a big client.
>
> After setting up LTSP 4.2 and copying (from
I configured the FreeNX cache to use /tmp, ltsp mounts a ramdisk at /tmp
doesnt it? My thin clients have 256Mb ram
I fully understnad your point - my observation was that the claim 'near
local speed' doesnt hold, and LTSP is still much faster on smaller
networks with low powered thin clients- that
