Date: Wed, 21 Mar 2012 09:42:05 -0400 From: John Baldwin <jhb@freebsd.org> To: Ed Schouten <ed@80386.nl> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Sergey Kandaurov <pluknet@freebsd.org>, src-committers@freebsd.org Subject: Re: svn commit: r233271 - in head/sys: amd64/conf arm/conf i386/conf ia64/conf mips/conf pc98/conf powerpc/conf sparc64/conf Message-ID: <201203210942.05146.jhb@freebsd.org> In-Reply-To: <20120321104409.GL87507@hoeg.nl> References: <201203210838.q2L8chUM062260@svn.freebsd.org> <CAE-mSOKYO=6ib=pVQzy5iiZgB3Znu6gVr7P=sr6Rov-WXY9yNQ@mail.gmail.com> <20120321104409.GL87507@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, March 21, 2012 6:44:09 am Ed Schouten wrote: > Hi Sergey, > > * Sergey Kandaurov <pluknet@freebsd.org>, 20120321 11:18: > > Will this affect old binaries like misc/mc build for e.g. 6.x running on GENERIC > > w/o kldoaded pty(4), so that I will have to `kldload pty'? > > Currently executing old mc results in emitting the following kernel message: > > > > pid 11948 (mc) is using legacy pty devices - not logging anymore > > If it's dynamically linked against libc and libutil, it's not a problem. > Otherwise you need to rebuild mc(1). If rebuilding mc(1) doesn't help, > let me know and I'll take a look at the port. > > If apps print the "is using legacy pty devices" message, you probably > need to load pty(4). 6.x predates the symbol versioned libc, so even if it is dynamically linked it is still using older versions of the pty lookup routines. It will likely need pty(4) forever. Perhaps you could enable pty(4) by default if one of the relevant COMPAT_FREEBSD options is included? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203210942.05146.jhb>