From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pony.its.uwo.ca([129.100.2.63]) (1427 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Mon, 19 Feb 2001 12:48:21 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from ignatious (c716099-a.rchdsn1.tx.home.com [24.7.105.70]) by pony.its.uwo.ca (8.10.0/8.10.0) with ESMTP id f1JHmN206960 for ; Mon, 19 Feb 2001 12:48:23 -0500 (EST) Received: from cpt.kirk (helo=localhost) by ignatious with local-esmtp (Exim 3.12 #1 (Debian)) id 14Uuft-0002EN-00 for ; Mon, 19 Feb 2001 12:04:37 -0600 Date: Mon, 19 Feb 2001 12:04:37 -0600 (CST) From: Kirk Wood X-Sender: cpt.kirk@ignatious 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, Klarich, Terry wrote: > For myself, I probably be using group security. I will create a speakup > group and limit all access to these files to root and to those who are in > the speakup group. 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. ======= Kirk Wood Cpt.Kirk@1tree.net Nothing is hard if you know the answer or are used to doing it.