Cas Caswell replied:
> @ >
> @ So if it's easy, it just gets slipped in, but if it's not it needs a business
> @ case... Doesn't that sound familiar !
>
>   Well it ought to. Sorry but it is a fact of life that HP wants to make
>   money off our time. So if it's easy to do, it's easy to get permission
>   to do it, or easy to do on our own time. Otherwise we have to prioritize
>   the work based on what the most customers will get a benefit from and
>   therefore continue to fund us by buying new machines. I understand the
>   frustration on your end, but I can't think of a better way to do the
>   business myself.
>
Sorry if you felt my irony was aimed at you ... it wasn't ! I was just
enjoying some civilized (I hope) HP bashing... We all recognize the
great services some of the HP engineers are doing, probably even in their spare
time.
Anyway, I've followed your advice and filed a enhancement request for remshd
on the 3k. Hope it helps some. There _must_ be others wanting this, or ... ?

>  <snip observation that TIO is a problem for interoperability and that I
>   may be linking the rlogin issue to remshd improperly in my head deleted.
>   I'll try to come back to those in a future message>
>
> @ BTW Why is remsh not served by inetd ? That's something I have never
> @understod.
>
Sorry for this DUMB question; I must have had some sort of brain lapse. Of course
remsh _is_ served by inetd (at least initially), as I darn well knew.

>
>  I haven't addressed all of Chris' points. I'll come back to the others in
>  a future message. I really want to look at this bloody ls hang he
>  discovered. It's most annoying.
>
Yes, the bloody hangs, they're the worst ;-) Good luck and let us know !

Regards,


        Chris Breemer
        Compuware Europe B.V.