Richard Cobbe <[EMAIL PROTECTED]> wrote:
>Lo, on Thursday, July 26, Karsten M. Self did write:
>> ObligTelnetBashing: don't use telnet. Remove your telnet daemon. Use
>> SSH for all remote access. Consider removing your telnet client
>> (there's an alternative, whose name I forget, which is use
on Thu, Jul 26, 2001 at 08:36:55PM -0500, Richard Cobbe ([EMAIL PROTECTED])
wrote:
> Lo, on Thursday, July 26, Karsten M. Self did write:
>
> > ObligTelnetBashing: don't use telnet. Remove your telnet daemon. Use
> > SSH for all remote access. Consider removing your telnet client
> > (there's
Lo, on Thursday, July 26, Karsten M. Self did write:
> ObligTelnetBashing: don't use telnet. Remove your telnet daemon. Use
> SSH for all remote access. Consider removing your telnet client
> (there's an alternative, whose name I forget, which is useful for
> establishing connections to variou
on Thu, Jul 26, 2001 at 05:25:44AM -0400, [EMAIL PROTECTED] ([EMAIL PROTECTED])
wrote:
> Ok,
First: try posting followups to an existing thread rather than a new
one. It's where people will look for them, and provides context.
> freeze means that the machine don't react to ANYTHING, not even t
Ok,
freeze means that the machine don't react to ANYTHING, not even to:
- Ctrl-Alt-Fn
- Ctrl-Alt-Backspace
- login via telnet or serial line
- Ctrl-Alt-Del
Even a active telnet session from another host to that machine freezes so i
have to kill it on that host. I didn't say freeze for no reason.
5 matches
Mail list logo
