From owner-cvs-all@FreeBSD.ORG Sun Aug 24 16:49:50 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 303711065675; Sun, 24 Aug 2008 16:49:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id EBEEF8FC1B; Sun, 24 Aug 2008 16:49:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 60E3946B5B; Sun, 24 Aug 2008 12:49:49 -0400 (EDT) Date: Sun, 24 Aug 2008 17:49:49 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ed Schouten In-Reply-To: <20080824160127.GW99951@hoeg.nl> Message-ID: References: <200808241006.m7OA6IbU072333@repoman.freebsd.org> <20080824160127.GW99951@hoeg.nl> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src ObsoleteFiles.inc src/libexec Makefile src/libexec/pt_chown Makefile pt_chown.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2008 16:49:50 -0000 On Sun, 24 Aug 2008, Ed Schouten wrote: > There is no need for compat libraries, because the existing ones already do > this: > > - Try to run pt_chown. > - If that fails, try to chmod/chown the slave device by hand. > - If that fails, return an error. > > Because the PTY that openpty() obtains already has the proper permissions in > place, the second step won't fail. Sounds good. The two compat cases I have in mind are: (1) Pure system call ABI: do old libraries, binaries, and synchronized configuration files work with the new kernel. The "in a jail" case. (2) Mixed ABI: do old libraries and binaries work with new configuration files, new binaries, and new kernels. On the whole we don't get too many cases of problems with (2), since many config files have fairly static content and syntax over time. The two recent cases where I've seen problems have been old libc malloc's with new malloc.conf's (lots of warnings, but works fine as far as I can tell), and with /etc/ttys. Robert N M Watson Computer Laboratory University of Cambridge