From owner-freebsd-questions Fri May 28 15:15:46 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B3A0014E53 for ; Fri, 28 May 1999 15:15:44 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA05535; Fri, 28 May 1999 15:15:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 28 May 1999 15:15:34 -0700 (PDT) From: Doug White To: Jeff Ehrenkrantz Cc: freebsd-questions@FreeBSD.ORG Subject: Re: tty ? In-Reply-To: <006301bea83c$8bdbe220$3142f5cf@whyy.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 May 1999, Jeff Ehrenkrantz wrote: > I evidenty changed somthing and didn't realize it. While sting to set > stty erase ^? to allow me to work remotly from a mac :( I think i > screwed over something relatted to tty. Now any time I try to log in > from anywhere (except the consule it's 70 miles away haven't tryed it > yet) the login won't take a s as a valid key... well actuall it has > become the destructive backspace. therefore i can't login and use an s > .. funny thing is i have an s in the root password. so although i can > login as another wheel user i cand su to root to fix things. i can't > even copy stty to something that doesn't have an s in it. I'm using > 3.2 release would someone send me a copy of stty with permissions set > to enabe group write enable. And does anyone know the name of the > actual fill I most likely screwed over . Thanks..je Did you verify that it's not the Mac that's screwed up? tty settings don't generally propagate between sessions. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message