public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: "'speakup@braille.uwo.ca'" <speakup@braille.uwo.ca>
Subject: RE: /proc/speakup
Date: Mon, 19 Feb 2001 12:04:37 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0102191203160.8557-100000@ignatious> (raw)
In-Reply-To: <DB56BAD3BFCED3119D3100D0B723865607BF9477@wcgtule103.wcg.williams.com>

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.



  reply	other threads:[~ UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 /proc/speakup Klarich, Terry
 ` Kirk Wood [this message]
   ` /proc/speakup Geoff Shang
  -- strict thread matches above, loose matches on Subject: below --
 /proc/speakup Holmes, Steve
 ` /proc/speakup Kerry Hoath
   ` /proc/speakup Frank Carmickle
 /proc/speakup Holmes, Steve
 ` /proc/speakup Geoff Shang
 ` /proc/speakup Kerry Hoath
 /proc/speakup Holmes, Steve
 /proc/speakup Tyler Spivey
 ` /proc/speakup Buddy Brannan
 ` /proc/speakup Raul A. Gallegos
 ` /proc/speakup Kirk Wood
   ` /proc/speakup Brent Harding
 ` /proc/speakup Kerry Hoath
 ` /proc/speakup Geoff Shang
 ` /proc/speakup Gene Collins
 /proc/speakup Tyler Spivey
 ` /proc/speakup Buddy Brannan
 ` /proc/speakup Geoff Shang
   ` /proc/speakup Steve Holmes
     ` /proc/speakup Geoff Shang
 ` /proc/speakup William F. Acker WB2FLW +1-303-777-8123
 ` /proc/speakup raul
 ` /proc/speakup Kerry Hoath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0102191203160.8557-100000@ignatious \
    --to=cpt.kirk@1tree.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).