From: "Chris Norman" <chris.norman4@ntlworld.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Permissions for /dev/softsynth
Date: Fri, 29 Dec 2006 00:12:00 -0000 [thread overview]
Message-ID: <007401c72add$fbf8bcf0$5802a8c0@WORKLAPTOP> (raw)
In-Reply-To: <20061228203447.GA15813@linden.yelavich.home>
Could you not just use chown?
HTH,
Chris Norman
<!-- cnorman@rnibncw.ac.uk -->
----- Original Message -----
From: "Luke Yelavich" <themuso@themuso.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, December 28, 2006 8:34 PM
Subject: Re: Permissions for /dev/softsynth
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, Dec 29, 2006 at 07:04:12AM EST, Hynek Hanke wrote:
>> Kirk Reiser píše v Čt 28. 12. 2006 v 14:23 -0500:
>> > If you're looking for official sanction I say go for it.
>>
>> Please, do you know what should I do to make sure the softsynth device
>> (and also /proc/) is created with group speakup each time
>> it is created?
>
> The permissions can be set for /dev/softsynth using udev. As far as I
> have gathered, the device node is created by the speakup_sftsyn module.
> It is just a matter of getting an udev rule included for it.
>
> As for /proc/speakup, IMO thats best done in the speakup code, whether
> it be a parameter to the module, or on the kernel command-line, as
> different distros may want to have the speakup group as different group
> numbers.
> - --
> Luke Yelavich
> GPG key: 0xD06320CE
> (http://www.themuso.com/themuso-gpg-key.txt)
> Email & MSN: themuso@themuso.com
> Jabber: themuso@jabber.org.au
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQFFlCpmjVefwtBjIM4RAkafAJ0WyitcX7oxOaBl4wXvoARnqxxMDQCgj+R8
> +XFz87Gpt0FfJ9WzT417Qy8=
> =HAsp
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Hynek Hanke
` Kirk Reiser
` Hynek Hanke
` Luke Yelavich
` Kirk Reiser
` Chris Norman [this message]
` Luke Yelavich
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='007401c72add$fbf8bcf0$5802a8c0@WORKLAPTOP' \
--to=chris.norman4@ntlworld.com \
--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).