Date: Tue, 04 Jun 2013 10:01:42 -0600 From: "Janky Jay, III" <jankyj@unfs.us> To: ports@freebsd.org Subject: Re: Pseudo-TTY Issues with FBSD 10 Snapshot? Message-ID: <51AE0F66.3030802@unfs.us> In-Reply-To: <E49C6934-5B4D-414D-AE68-0565535EC7C3@FreeBSD.org> References: <51AD7292.1040503@unfs.us> <E49C6934-5B4D-414D-AE68-0565535EC7C3@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Dimitry, On 06/04/2013 12:44 AM, Dimitry Andric wrote: > On Jun 4, 2013, at 06:52, Janky Jay <jankyj@unfs.us> wrote: >> So, I'm unsure if this is related to a difference in pseudo TTY's yet or >> not, but I'm having a very strange issue that I've never encountered >> before. Details as follows: >> >> Fresh install of FBSD 10 >> FreeBSD fbsd10.purplehat.org 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Mon >> May 13 00:54:58 UTC 2013 >> root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64) >> >> I've installed XFCE4 and Fluxbox as a play-around/test WM along with >> x11/aterm. Everything seems to be working perfectly aside from the fact >> that I can no longer use the 'aterm' command. Any time I try to start an >> instance of 'aterm', I get the following error: >> >> aterm: ca't open pseudo-tty >> aterm: aborting > > Have you tried "kldload pty" ? This should work for apps that still > require ptys. If that works, put the following in /boot/loader.conf: > > pty_load="YES" > > so it will auto-load at boot time. > > -Dimitry > Thanks for the reply. I figured it would be something like this if the ptys were no longer available in FBSD10. I'll give this a shot later tonight and update the list with my findings. Regards, Janky Jay, III
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51AE0F66.3030802>