chrome://messenger/locale/messengercompose/composeMsgs.properties:
On Tue, 09 Feb 2010 23:58:10 +0100, Dale <rdalek1...@gmail.com> wrote:
chrome://messenger/locale/messengercompose/composeMsgs.properties:
On 2/9/2010 3:16 AM, Dale wrote:
On Mon, 8 Feb 2010 21:17:08 -0500, Walter Dnes wrote:
My solution to simplify Gentoo...
waltd...@d531 ~ $ cat /etc/portage/package.mask
sys-libs/pam
sys-apps/dbus
sys-apps/hal
You'll have to do a manual depclean (very carefully) and
revdep-rebuild, but it's worth the effort to purify your Gentoo
system.
Simpler than that, just add -hal to xorg stuff in package.use and then
run emerge -uvDNa world.
I'm not saying your way won't work but I think mine is easier.
His way is also *way* more Luddite than yours. Note the 'pam' and
'dbus', two things basically standard (and very stable) on modern
Linux desktop systems.
--K
I don't agree with the term Luddite here. It's not being against new
things and new ways of doing things. He just doesn't need those
things for his hardware to work properly. Me, I don't need hal for
my mouse and keyboard to work. As a matter of fact, mine doesn't
work WITH hal. I have to remove hal to get mine to work.
So, hal may be progress to you but it is a step backward for me.
It's the opposite of progress.
Dale
:-) :-)
I think, that hal was a lot harder for a lot of us, than the good old
xorg.conf. This may because we (linux user in general) are used to
xorg.conf. For my personal experience, I hadn't been using linux for
about 4 years, so I'd completely forgotten the xorg syntax, but that
was still a more simple process to relearn the xorg.conf syntax, than
understanding the hal configuration files.
A project such as hal necessarily has contact with the user with an
"unusual" (read: at least a non-us keyboard) setup. Therefore the
syntax in which it is configured has to be "easily" (read: a quick
google search/documentation search away) accessed by the users to whom
it may be necessary. And I believe that this is the point where hal
truly fails, other than cases like Dale's.
The xorg.conf is simply a more simple, and easier configuration file
than the various hal policies.
Well, actually, if hal would have worked I wouldn't have cared if it
uses xorg.conf at all. That was the point of using hal. Thing is, I
followed the howto and it didn't work. The fact that the config files
are in xml only became a problem after hal locked me out of my GUI and
required a hard shutdown.
So, hal failed on my system not just because of the config files being
in xml but because it just didn't work at all. Bad things is, this
system is a 5 year old rig. Heaven forbid I had something new that had
"iffy" support.
Dale
:-) :-)
