From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: how to remove HAL
Date: Wed, 28 Jul 2010 23:22:27 +0200 [thread overview]
Message-ID: <201007282322.27601.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <i2q68m$pb7$1@dough.gmane.org>
On Wednesday 28 July 2010 23:08:45 Nikos Chantziaras wrote:
> On 07/28/2010 11:54 PM, Andrey Vul wrote:
> > On Wed, Jul 28, 2010 at 14:50, Nikos Chantziaras<realnc@arcor.de> wrote:
> >> On 07/28/2010 08:23 PM, Neil Bothwick wrote:
> >>> On Wed, 28 Jul 2010 19:31:21 +0300, Nikos Chantziaras wrote:
> >>>> And why do you want to remove it in the first place? It's not gonna
> >>>> eat your cat.
> >>>
> >>> Although it may kill your crew.
> >>
> >> I think most people don't understand what X used HAL for. They think
> >> that they can remove HAL and still have stuff like USB
> >> hotplugging/automounting working. But that's wrong. Gnome/KDE use HAL
> >> for this, not X. And if you disable HAL completely, that stuff will
> >> stop working.
> >
> > E.g. solid-hardware for HAL-mounting devices by uuid/volume-id.
> >
> > I just got rid of policykit - too much trouble.
> > But I kept HAL because it's very useful.
>
> If you're on KDE, you will need policykit again in the future, since
> with KDE 4.5 (to be released in a matter of days) it's not really
> optional anymore. I got hit by this when updating to it (now at RC3):
>
> https://bugs.kde.org/show_bug.cgi?id=244444
Something tells me the kde.org admins didn't *really* intend to show me all
this info:
Software error:
DBD::mysql::db selectrow_array failed: Unknown table engine 'InnoDB' [for
Statement "SELECT bug_id FROM bugs WHERE bug_id = ?"] at Bugzilla/Bug.pm line
3366
Bugzilla::Bug::ValidateBugID(244444) called at
/home/bugzilla/public_html/show_bug.cgi line 62
For help, please send mail to the webmaster (sysadmin@kde.org), giving this
error message and the time and date of the error.
tut, tut, kde.org. Big fail. Need to learn how to trap errors properly.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2010-07-28 21:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 2:44 [gentoo-user] how to remove HAL sam new
2010-07-28 5:01 ` Alan McKinnon
2010-07-28 13:34 ` sam new
2010-07-28 15:08 ` Alan McKinnon
2010-07-29 2:26 ` sam new
2010-07-29 6:39 ` Alan McKinnon
2010-07-29 8:07 ` sam new
2010-07-28 16:46 ` Volker Armin Hemmann
2010-07-28 8:05 ` Neil Bothwick
2010-08-17 19:49 ` Enrico Weigelt
2010-08-18 13:22 ` Mike Edenfield
2010-08-19 3:05 ` [gentoo-user] autodepclean script (was "how to remove HAL") Walter Dnes
2010-08-21 10:07 ` [gentoo-user] " Francesco Talamona
2010-08-21 23:32 ` Walter Dnes
2010-08-22 9:45 ` Francesco Talamona
2010-08-19 9:57 ` [gentoo-user] how to remove HAL Neil Bothwick
2010-07-28 16:31 ` [gentoo-user] " Nikos Chantziaras
2010-07-28 17:23 ` Neil Bothwick
2010-07-28 18:50 ` Nikos Chantziaras
2010-07-28 20:54 ` Andrey Vul
2010-07-28 21:08 ` Nikos Chantziaras
2010-07-28 21:22 ` Alan McKinnon [this message]
2010-07-29 0:31 ` [gentoo-user] " Andrey Vul
2010-07-29 0:38 ` [gentoo-user] " Nikos Chantziaras
2010-07-29 0:44 ` Nikos Chantziaras
2010-07-29 0:33 ` [gentoo-user] " Andrey Vul
2010-07-29 2:24 ` [gentoo-user] " sam new
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=201007282322.27601.alan.mckinnon@gmail.com \
--to=alan.mckinnon@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