From owner-freebsd-isp Fri Nov 13 16:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23427 for freebsd-isp-outgoing; Fri, 13 Nov 1998 16:01:08 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from aniwa.sky (p17-nas1.wlg.ihug.co.nz [216.100.145.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23416 for ; Fri, 13 Nov 1998 16:01:03 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from localhost (andrew@localhost) by aniwa.sky (8.8.8/8.8.7) with SMTP id MAA01043; Sat, 14 Nov 1998 12:59:53 +1300 (NZDT) (envelope-from andrew@squiz.co.nz) Date: Sat, 14 Nov 1998 12:59:53 +1300 (NZDT) From: Andrew McNaughton X-Sender: andrew@aniwa.sky Reply-To: andrew@squiz.co.nz To: Bill Fumerola cc: Andy Farkas , freebsd-isp@FreeBSD.ORG Subject: Re: no more telnet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Nov 1998, Bill Fumerola wrote: > On Sat, 14 Nov 1998, Andrew McNaughton wrote: > > > Installing ssh won't save you a trip to the console if it's currently > > required, since you need access before you can install ssh. Once you're > > back up though you might consider installing ssh and running it as a > > daemon, (not through inetd) so that it acts as a backup access method in > > case your problem returns. > > More accuratly: Installing ssh won't save you a trip to the console, > because it too uses a pty. If there are no other shell users then the suggestion that there are to few tty's seems a bit dubious. Could be they've been locked up somehow. If one issues commands as 'ssh -l user host command', does the tty get used at all? If not, then it could be useful. I guess rsh could be used similarly and might be installed? Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message