From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: editing a file in /sys/accessibility/speakup/i18n
Date: Thu, 15 Jun 2017 07:41:26 +0200 (SAST) [thread overview]
Message-ID: <alpine.DEB.2.20.1706150733390.3139@willempc.meraka.csir.co.za> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1706140929580.3019@southernprince>
Willem here.
Those are kind of special files.
Copy the file to somewhare, edit it and then use cat to overwrite
/sys/accessibility/speakup/characters i.e. cat /etc/my_changes >
/sys/accessibility/speakup/characters
/sys/accessibility/speakup/characters is not a real file. you will have to
do the cat every time you want the changes effected.
What I mean that changes to most of the /sys/accessibility/speakup files
are not permanent and get set to its default on a reboot.
Regards, Willem
On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> Mark Peveto here,
> When trying to edit a file called characters in /sys/accessibility/speakup/i18m, I try to save the file, and it says error saving file, bad file
> descriptor. I'm usign sudo with my nano command, which usually works.
> what's the problem here?
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
Please consider the environment before printing this email.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [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=alpine.DEB.2.20.1706150733390.3139@willempc.meraka.csir.co.za \
--to=blinux-list@redhat.com \
/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).