Re: fedora: where are the client's logs kept?

jam <[email protected]>
Newsgroups gmane.linux.terminal-server.devel
Message-ID <[email protected]>
On Monday 18 August 2008 03:01:25 ltsp-developer-request-5NWGOfrQmneRv+LV9MX5uuRhgaa4a2kL@public.gmane.orgnet 
wrote:
> > I'm curious, while I am thankful that you're fixing up the x86_64 client
> > support, how is x86_64 thin clients a benefit to you over i386?
> >  
>
> The guy I'm helping went out and bought a bunch of sub-$500 x86_64
> boxes.  He'd
> like to get use out of the hardware.  
>
> Plus I'm expecting great performance with ltsp-localapps.

I'm still following Warrens thought chain ...

Why do you believe a 64 bit system is better-performing than 32 on same 
hardware?

My tests show about the same, some slightly worse, some slightly better.
64 bit IS better with RAM > 1G, depending on what you do maybe much better.

A bunch of Sub-$500 will work beautifully on 32 bit. No reason to not play 
with 64bit clients, but for real-work I see no benefit and some disadvantages 
eg the whole flash ndpluginwrapper saga.

So to reask :-) Warrens question:  how is x86_64 thin clients a benefit to you 
over i386?

> Plus I'm expecting great performance with ltsp-localapps.
You are going to be disappointed :-)

Thanks
James

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.