From owner-freebsd-questions Wed Jan 17 05:27:53 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA10947 for questions-outgoing; Wed, 17 Jan 1996 05:27:53 -0800 (PST) Received: from chuma.cas.usf.edu (gray@chuma.cas.usf.edu [131.247.31.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA10942 for ; Wed, 17 Jan 1996 05:27:49 -0800 (PST) Received: (gray@localhost) by chuma.cas.usf.edu (8.6.11/8.6.5) id IAA11536; Wed, 17 Jan 1996 08:27:39 -0500 Date: Wed, 17 Jan 1996 08:27:39 -0500 (EST) From: "Chance Gray (CSC)" X-Sender: gray@chuma To: davidg@root.com cc: freebsd-questions@freebsd.org Subject: Re: 2.1 problems (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Thu, 11 Jan 1996, David Greenman wrote: > >I recently upgraded to 2.1 from 2.1-SNAP. When I log in now from a > >remote machine I can barely run anything. Simple things like 'cat' and > >'ls' lock up my sessions. Everything except the ports works fine from > > It sounds like a problem that was fixed in 2.1-stable. Can you SUP/upgrade > to that and see if the problem goes away? > > -DG > > David Greenman > Core Team/Principal Architect, The FreeBSD Project > I have run sup and recompiled the kernel and all binaries successfully. Still when I log into my machine from a remote machine and run 'ls' my session hangs. Maybe it is something simpler, like incorrect permissions on my pty? Any help is much appreciated. Correction: I unaliased ls from 'ls -aF' to just 'ls' and it works. Now it seems that 'ls -a' does not work along with 'more' and 'cat'. Except they all work on the console. Chance Gray CAS Computing x2418