Oliver Grawert kirjoitti:
> hi,
> Am Freitag, den 25.09.2009, 12:56 +0200 schrieb Stefan Below:

> the xlibs in NX are several years old and lack security updates, they
> wree written in a time where hardware was a lot less powerfull, how is
> it wrong to compate these libs with a browser that was written at a time
> when hardware was less powerfull and which doesnt see any security fixes
> anymore ?

>From the user perspective there is one huge difference: Netscape does
not do what a user expects from a browser anymore: it does not render
modern web pages as expected of a web browser. NX on the other hand,
regardless of how ugly it may be under the hood, performs the task it
was designed for. On the security aspect of it I agree - although in an
thin client environment NX is used locally but a web browser over the
internet.

>> I really like the LTSP and Linux, but sometimes it makes me sad to see 
>> that the development goes in the wrong direction.

> which would be the tright direction in your opinion, stick with
> unsupported upstream software, leave security holes open. stay faster
> instead of fixing issues in new software but have support from
> upstream ? thats what ltsp4 did and it got to the point where the ltsp
> developers had to drop the ball simply because they couldnt cope with
> keeping the software safe and in a supportable state.

> if you really want the released ltsp5 versions to be bugfree, there is
> only one thing you can do to help out: 
> TEST DEVELOPMENT RELEASES !!!

In this particular bug the symptoms were visible to any user (all
users?), so there are cases a larger group of people testing devel
releases is better and cases where it had not made any difference anyway.

I realize the more people you have testing devel releases the better the
chances for a better working software, but I don't really see why a user
should have guilt for being just that: a user. I understand that people
who put time and effort to developing need gratitude and respect they
deserve for their efforts, but there should not be expectation that the
user feedback is not valuable unless the user is also a developer and/or
devoted tester of devel releases. (How many are willing to guinea pig
their production environment and make it a devel lab instead? We are a
shop of less than 10 users, so there are no resources to run a test lab
on parallel. At home I have a crappy RR DSL/LAN router that can not do
NAT properly, so it works only in bridged mode and clients are assigned
a public IP. Not much use for making home a test lab :-(


> help to identify bugs before the release so the bugs dont even go out to
> the users. if you dont do that i really dont see from where you take the
> right to complain about bugs that werent even introduced by ltsp but
> actually fixed by ltsp developers and for which exactly these ltsp
> developers offer bugfix packages to make your life easier.
> 
> ciao
>       oli

I for one am grateful this thing was fixed. My only complaint is about
the fixed stuff not making the mainstream update repository.

Wishing a nice weekend to all,

-- 
Anton

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to