| 1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
| 2 |
> On Mon, Feb 08, 2010 at 10:20:47PM +0000, Alan Mackenzie wrote |
| 3 |
> |
| 4 |
> |
| 5 |
>> However, I'm now trying to get X up and running. "The X Server |
| 6 |
>> Configuration HOWTO", section 3. "Configuring Xorg" says: |
| 7 |
>> |
| 8 |
>> "Hal comes with many premade device rules, also called policies. |
| 9 |
>> These policy files are available in /usr/....../policy. Just find a |
| 10 |
>> few that suit your needs most closely and copy them to /etc/...." |
| 11 |
>> |
| 12 |
>> "For example, to get a basic working keyboard/mouse combination, you |
| 13 |
>> could copy the following files... |
| 14 |
>> /usr/.........../10-input-policy.fdi |
| 15 |
>> /usr/.........../10-x11-input.fdi" |
| 16 |
>> |
| 17 |
>> . Am I the only person that finds this semantic gibberish? Is there |
| 18 |
>> any explanation somewhere of what a "policy" aka "device rule" is? What |
| 19 |
>> is the semantic significance of a "device rule"? What does it mean, to |
| 20 |
>> "rule a device", or what sort of restrictions are being placed on this |
| 21 |
>> device? |
| 22 |
>> |
| 23 |
> My solution to simplify Gentoo... |
| 24 |
> |
| 25 |
> waltdnes@d531 ~ $ cat /etc/portage/package.mask |
| 26 |
> sys-libs/pam |
| 27 |
> sys-apps/dbus |
| 28 |
> sys-apps/hal |
| 29 |
> |
| 30 |
> You'll have to do a manual depclean (very carefully) and |
| 31 |
> revdep-rebuild, but it's worth the effort to purify your Gentoo system. |
| 32 |
> |
| 33 |
> |
| 34 |
|
| 35 |
Simpler than that, just add -hal to xorg stuff in package.use and then |
| 36 |
run emerge -uvDNa world. It will rebuild a couple things, maybe even |
| 37 |
just xorg, then everything is back to the old way. This allows hal to |
| 38 |
be their for other things where it does work but it disables it where it |
| 39 |
doesn't work. |
| 40 |
|
| 41 |
I'm not saying your way won't work but I think mine is easier. |
| 42 |
|
| 43 |
Dale |
| 44 |
|
| 45 |
:-) :-) |
Archives