From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uq.net.au(fox.uq.net.au[203.101.255.1]) (1734 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Tue, 20 Feb 2001 23:23:29 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from data.home (mail@dyn-12-99.dialin.uq.net.au [203.100.12.99]) by uq.net.au (8.9.3/8.9.3) with ESMTP id OAA22485 for ; Wed, 21 Feb 2001 14:23:26 +1000 (GMT+1000) Received: from geoff by data.home with local-esmtp (Exim 3.12 #1 (Debian)) id 14V6wg-0001CG-00; Tue, 20 Feb 2001 17:10:46 +1000 Date: Tue, 20 Feb 2001 17:10:46 +1000 (EST) From: Geoff Shang To: "'speakup@braille.uwo.ca'" Subject: RE: /proc/speakup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: On Mon, 19 Feb 2001, Kirk Wood wrote: > I think that this idea is the best one. Perhaps the ownership of the files > could be root.speakup. Then a person can add anyone they desire to the > speakup group for access. This is a good idea, but can't be done (or at least, can't be done easily). Remember that the proc files are vertual files, not actual files. Because of this, you can't change the ownership of them like you would ordinary files. Jim or Kirk can't hard-code in this ownership either. The reason is that the ownership is determined by user and group ID numbers. Kirk and Jim have no way of knowing what group ID such a speakup group would have on a system, and speakup wouldn't be able to look in /etc/group when it loads because the file system wouldn't yet be mounted. So, as far as I can see, root has to be the owner and group since you know that they are user and group 0. Geoff.