From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: dont-init-tables again
Date: Thu, 29 Mar 2007 15:38:15 -0400 [thread overview]
Message-ID: <000201c77239$cc1b6c00$ca01a8c0@quark> (raw)
In-Reply-To: <000601c77232$d073cdd0$6401a8c0@YOUR3ADE1B78A3>
I got this response from a friend of mine who is a heavy Gentoo user.
***
Sina,
Actually that's not entirely true. By default portage will prompt you when
a file has been changed, letting you merge in changes, accept the new file,
or keep the old one. That's what 'etc-update' does.
However, you can tell portage to always accept or deny changes, either for
individual files or entire directories. Granted denying changes could be
bad since you'd not know if meaningful changes happen, but...
As an example, portage would LOVE to overwrite my sshd.conf changes. I keep
having to tell it not to, *smile*
***
Hope this helps?
Take care,
Sina
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Keith Hinton
Sent: Thursday, March 29, 2007 2:48 PM
To: Speakup
Subject: dont-init-tables again
Portage in Gentoo will overite any init script modifications wich means that
editing the init script for Speechd-up won't necessarily be the best result.
The best idea is to find a configuration file for Speechd-up.
If there are any Gentoo users who have gotten Speechd-up to start with -t
automatically(I hate manually launching things!) Then please email me off
list to avoid getting oconfused.
There are too many replys eaven in digest mode to glance at and I have
little time to look at them. Regards, --Keith.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Sina Bahram [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='000201c77239$cc1b6c00$ca01a8c0@quark' \
--to=sbahram@nc.rr.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).