CUPS, printcodes, stale UTMP entries, and terminal hangs

[Bill Vermillion]

On Tue, Jan 18 16:27 , Men gasped, women fainted, and small children 
were reduced to tears as Fairlight confessed to all:" 

> Only Patowic would say something like:
>
> > I have resolved this issue. It was a bug in openssh-3.8p1.
> > Ironically,

> You can't trust that as the real version number. Hell, 9.0
> still reports a 3.7pl2 but it's got all the security backports.
> Most linux vendors stick with the base product number and
> simply bump the rpm version when they do something. The scheme
> sucks.

> > appears uninterested in fixing this bug, which appears only  
> > in SuSE 9.1. One can, however, grab RPMs from SuSE 9.2, and  
> > install them on a 9.1                                        

> Nobody should be running 9.1 or 9.2 unless they -NEED- kernel
> 2.6 or one of the other features that's only workable under the
> newer dists. It's still at least six months before I'll start
> trusting that kernel. Last I saw, it was up to 2.8.10, so only
> 8 more patchlevels to go...

I wish I'd save the e-newletter I got a couple of weeks ago with
some of the testing done on the 2.6 based systems.  It looks to be
a tremendous winner for web-servers, and the different test
results I've seen run from 30 to 50% inprovments.

It really shine in the multi-cpu environment.

Since 2.6 was released in December of 2003 you are saying that
a kernel should be in use for at least 1.5 years before you trust
it?  

> They don't release them like they used to.

> > box without incident.  For those of a technical bent, it has to do with 
> > the 2.6 kernel using pseudo-tty numbers in excess of 999.  If you'd 

> *cough*  The prosecution rests.

I'm confused by that last statement.  What exactly are you tyring
to say?



-- 
Bill Vermillion - bv @ wjv . com