From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup and locales
Date: Fri, 29 May 2009 18:55:53 +0800 [thread overview]
Message-ID: <EE4EE5191B454EFB9028EE536EB56F40@bouncy> (raw)
In-Reply-To: <87ab4wckir.fsf@onlinehome.de>
the /sys file system is exported by the kernel as is /proc
kernel interfaces cause files to be created in this file system to which you
can read and write.
You are not meant to create files in this directory yourself; only read and
write values to them.
If a file does not exist then the version of speakup is too old to have the
direct function.
files that exist in /sys/speakup allow you to change speakup's behaviour if
you write values into certain files.
If the file does not exist then the feature is not present in the kernel you
currently run.
Regards, Kerry.
----- Original Message -----
From: "Hermann" <meinelisten@onlinehome.de>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 29, 2009 5:42 PM
Subject: Re: Speakup and locales
On 28.05.2009 at 22:00:47 William Hubbs <w.d.hubbs@gmail.com> wrote:
> Hi Hermann,
>
> On Thu, May 28, 2009 at 09:27:45PM +0200, Hermann wrote:
>>> Actually, there is an easier way to do this. As root, do the following:
>>>
>>> echo 1> /sys/module/speakup/parameters/direct
>>>
I cannot add files to the /sys folder in general.
So I checked the mount options in /etc/fstab; here's what I found:
sysfs /sys sysfs rw,nosuid,nodev,noexec 0 0
Are these options set correctly?
I can replace existing files, but not create new ones. I guess it must
have to do with that "noexec" option.
Hermann
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Hermann
` William Hubbs
` Hermann
` William Hubbs
` Hermann
` Hermann
` Kerry Hoath [this message]
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=EE4EE5191B454EFB9028EE536EB56F40@bouncy \
--to=kerry@gotss.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).