Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261454AbUK1Msv (ORCPT ); Sun, 28 Nov 2004 07:48:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261455AbUK1Msv (ORCPT ); Sun, 28 Nov 2004 07:48:51 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:57226 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S261454AbUK1Msu (ORCPT ); Sun, 28 Nov 2004 07:48:50 -0500 Date: Sun, 28 Nov 2004 12:48:47 +0000 From: Al Viro To: Miklos Szeredi Cc: ecki-news2004-05@lina.inka.de, linux-kernel@vger.kernel.org Subject: Re: Problem with ioctl command TCGETS Message-ID: <20041128124847.GA26051@parcelfarce.linux.theplanet.co.uk> References: <20041128121800.GZ26051@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 735 Lines: 15 On Sun, Nov 28, 2004 at 01:32:17PM +0100, Miklos Szeredi wrote: > > Think read(2)/write(2). We already have several barfbags too many, > > and that includes both ioctl() and setsockopt(). We are stuck with > > them for compatibility reasons, but why the hell would we need yet > > another one? > > You can't replace either ioctl() or setsockopt() with read/write can > you? Both of them set out-of-band information on file descriptors. Out-of-band == should be on a separate channel... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/