From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Date: Sat, 11 Jul 2009 22:03:03 -0700 [thread overview]
Message-ID: <9acccfe50907112203s4cf0e73dg78dc1cb1c8541419@mail.gmail.com> (raw)
In-Reply-To: <20090710224631.48511382@dartworks.biz>
On Fri, Jul 10, 2009 at 10:46 PM, Keith Dart<keith@dartworks.biz> wrote:
> On Fri, 10 Jul 2009 20:53:22 -0700
> "Kevin O'Gorman" <kogorman@gmail.com> wrote:
>
>> This is NOT the way for Linux to make progress in the desktop wars,
>> folks.
>
> Works for me. ;-)
>
> But its true that Xorg is making some rapid progress. There's some
> growing pains. If you are running Gentoo unstable mask (~<X>) then
> you are on the "bleeding edge" of open source development. Therefore
> occasional breakage is to be expected. File a bug, make it better.
>
> If you want stable, then use Ubuntu LTS release, or CentOS. Stable, but
> boring. ;-)
Thanks for the sermon, pastor. I guess.
Why did you jump to the conclusion that I am running unstable? I'm
not. I never have, though I occasionally (like twice in the 7 years
I've been using gentoo) marked a particular package for unstable. So
by elimination, the term for what I have should be "stable". Why then
try to exile me to a distro I don't want?
I do, however, pretty much need "working". A black screen, dead input
devices, and impossibly esoteric config files just don't cut it. (The
HAL learning curve is a danger in itself, and is just not worth it to
me. I don't expect to touch it for years, which means that when it
eventually gets broken I'll have forgotten it completely and have no
idea how to proceed safely).
I got a solution by disabling HAL in gentoo. And for my broken ubuntu
systems, I did indeed go back to LTS, but not so much because of the
LT, it's just that 8.04 is the last one that worked. That's the
upside of a binary distro -- my November backup was good enough (i.e.
it worked), and an overnight update brought everything up to speed and
up to snuff. The things that change a lot are all in /home, which was
not affected.
Hopefully, I can now get on with my summer projects. I'm done with
HAL and X. Until next time.
++ kevin
--
Kevin O'Gorman, PhD
prev parent reply other threads:[~2009-07-12 5:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 3:03 [gentoo-user] xorg-server mouse and keyboard woes Kevin O'Gorman
2009-07-10 3:18 ` [gentoo-user] " James
2009-07-10 3:51 ` Dale
2009-07-10 4:52 ` Kevin O'Gorman
2009-07-10 5:02 ` Dale
2009-07-10 5:40 ` Kevin O'Gorman
2009-07-10 5:33 ` Kevin O'Gorman
2009-07-10 5:52 ` Dale
2009-07-10 7:34 ` Robin Atwood
2009-07-10 11:55 ` Philip Webb
2009-07-10 15:43 ` Kevin O'Gorman
2009-07-10 15:58 ` Dale
2009-07-10 17:46 ` Alan McKinnon
2009-07-10 18:47 ` Dale
2009-07-11 6:04 ` Keith Dart
2009-07-11 6:40 ` Dale
2009-07-10 8:18 ` [gentoo-user] " Keith Dart
2009-07-10 8:24 ` Keith Dart
2009-07-10 10:07 ` Kevin O'Gorman
2009-07-10 10:10 ` Kevin O'Gorman
2009-07-10 13:19 ` Dale
2009-07-10 14:22 ` Paul Hartman
2009-07-10 14:32 ` Helmut Jarausch
2009-07-10 16:02 ` Dale
2009-07-10 16:03 ` Kevin O'Gorman
2009-07-10 8:29 ` Helmut Jarausch
2009-07-10 18:50 ` [gentoo-user] " walt
2009-07-10 19:07 ` David
2009-07-11 3:53 ` Kevin O'Gorman
2009-07-11 5:46 ` Keith Dart
2009-07-12 5:03 ` Kevin O'Gorman [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=9acccfe50907112203s4cf0e73dg78dc1cb1c8541419@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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