hi, Am Freitag, den 25.09.2009, 12:56 +0200 schrieb Stefan Below: > Oliver Grawert schrieb: > > comparing the speed of NX with its insecure and outdated snapshot of the > > old included xlibs with recent implementations of xcb is somewhat like > > comparing netscape 2 with firefox 3.5 :) ... > And i think the most important think is "user experience". What should i > tell the users? tell them you install the known fix immediately and be done ?
> to say you cannot compare an old library/system with the
> new one? .... thats silly .... than the new library is not as good as
> the old one or its programmed for a different purpose.... (and the your
> comparison with netscape2 and firefox 3.5 does not fit here)
the new lib is written to support the old features as well as future
ones, ltsp is just a user of xorg, we dont write it, if xorg developers
make a decision to change something, please dont blame ltsp developers
for that (or call them silly) without the hard work sbalneav, stgraber
and others did put in to find a fix for the breakage thats only seen in
networked X connections the bug wouldnt have been fixed, please honor
their work.
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 ?
> 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 !!!
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
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
------------------------------------------------------------------------------ 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
