From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753546AbZDVPME (ORCPT ); Wed, 22 Apr 2009 11:12:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751690AbZDVPLx (ORCPT ); Wed, 22 Apr 2009 11:11:53 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:58915 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751841AbZDVPLw (ORCPT ); Wed, 22 Apr 2009 11:11:52 -0400 Date: Wed, 22 Apr 2009 16:12:57 +0100 From: Alan Cox To: Igor Zhbanov Cc: linux-kernel@vger.kernel.org Subject: Re: Idea: Feature information / extensions dispatcher syscall. Message-ID: <20090422161257.2743ea33@lxorguk.ukuu.org.uk> In-Reply-To: References: <871vrkpyae.fsf@basil.nowhere.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > But in some cases syscalls are more convenient than reading/writing/ioctling > in /proc, /sys or /dev. A syscall and an ioctl are the same thing except that you need a file handle for one of them. > And I suggest to regulate syscalls usage and reserve a set of numbers > "home" modules used in some organizations only. We have file system naming so you can open device or sysfs and the like files to do that job. That avoids the problem of trying to keep numbering sane. Alan -- "Alan, I'm getting a bit worried about you." -- Linus Torvalds