From owner-freebsd-current@FreeBSD.ORG Sat Jul 31 16:19:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF05816A4CE for ; Sat, 31 Jul 2004 16:19:05 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4482643D49 for ; Sat, 31 Jul 2004 16:19:05 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i6VGJ2NQ031657 for ; Sat, 31 Jul 2004 09:19:02 -0700 From: Kent Stewart To: freebsd-current@freebsd.org Date: Sat, 31 Jul 2004 09:19:04 -0700 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200407310919.04216.kstewart@owt.com> Subject: ssh message: Warning: no access to tty X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jul 2004 16:19:05 -0000 My 5.2-current system that I updated on 30 July is pretty useless. I don't know what all changed between 15 June and 30 july but I could ssh in on the 15 and a login in from a different computer on 30 July doesn't work. The world and kernel were rebuilt after the ../class/Makefile.inc error was fixed at 0920 UTC. On the console itself, I can work from the cli but konsole sessions from KDE are left blank with no prompt or login. I get the warning message from the subject when I try to ssh in. I also don't get any startup sounds from KDE but I figure the change from snd and pcm to sound has something to do with that. What I get from the console when I try to ssh in is the following: opal sshd[]: error openpty: No such file or directory opal sshd[] error: session_pty_req: session 0 alloc failed. What do I need to read about to get a working computer back? There wasn't any HEADSUP in /usr/src/UPDATING about serious changes between 15 June and 31 July. Currently, any portupgrade attempt fails because of a "clean error". I manually rebuilt everything needed by portupgrade and it still doesn't work. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html