From: Daniel Pielmeier <daniel.pielmeier@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Replacements for ivman
Date: Sat, 11 Oct 2008 23:40:37 +0200 [thread overview]
Message-ID: <48F11D55.5030906@googlemail.com> (raw)
In-Reply-To: <200810112306.44525.alan.mckinnon@gmail.com>
Alan McKinnon schrieb am 11.10.2008 23:06:
> On Saturday 11 October 2008 15:18:24 Dirk Heinrichs wrote:
>> Am Samstag, 11. Oktober 2008 13:24:03 schrieb Alan McKinnon:
>>> Is there a replacement for ivman?
>> What exactly do you do with it, which filesystems do you mount with it?
>
> At the moment mostly just hot-plug stuff on USB with your standard
> fat/ext2,3/reiser/nfts file systems, plus optical media. I also have an
> sd/mmc reader and firewire on this notebook, neither of which I've never used
> but probably should.
>
> HAL and the various things one could do with it's events is something I've
> stayed away from studying. Maybe early versions were confusingly
> documented... and all those xml files... I was reading a wiki page on my
> make/model notebook to see if I could improve on how I was using the
> hardware, this came up and looked useful. Automounting is the most obvious
> case, especially as e17 doesn't do it well - I get an ugly icon on the
> desktop and a long description string that is truncated at about 10
> characters, so the system is worse than useless. I resort to using konqueror
> with it's media:/ kio-slave instead, which feels clunky and more of a
> work-around than a proper desktop configuration.
>
> If there's something better than ivman, or if I really should be configuration
> HAL directly, then I'm all ears, but I do get the impression that one really
> should be working with HAL via a front-end for true ease of use
I also think having software that is unmaintained or updated very seldom
is not a good thing. I mean you lack features, bug and security fixes
here. When I see no progress for an app that I use quite often I search
for alternatives and get used to it.
You are right hal is quite messy and it is not worth to struggle with as
it is not developed any longer [1]. It will be replaced with
devicekit, maybe this will be a better implementation.
Thunar in combination with thunar-volman works fine here. But it also
uses hal and dbus quite much, as most xfce apps. I have no problems with
it though. Optical media and external USB devices work fine, other
things I don't need.
Regards,
Daniel
[1] http://lists.freedesktop.org/archives/hal/2008-May/011560.html
next prev parent reply other threads:[~2008-10-11 21:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 11:24 [gentoo-user] Replacements for ivman Alan McKinnon
2008-10-11 12:59 ` Florian Philipp
2008-10-11 21:08 ` Alan McKinnon
2008-10-11 13:18 ` Dirk Heinrichs
2008-10-11 21:06 ` Alan McKinnon
2008-10-11 21:40 ` Daniel Pielmeier [this message]
2008-10-11 21:56 ` Alan McKinnon
2008-10-11 18:53 ` Erik Hahn
2008-10-11 20:24 ` Norberto Bensa
2008-10-11 20:53 ` Erik Hahn
2008-10-11 21:01 ` Dale
2008-10-11 21:14 ` Alex Schuster
2008-10-11 22:52 ` Dale
2008-10-12 7:54 ` Alan McKinnon
2008-10-12 9:34 ` Dale
2008-10-11 20:58 ` Dale
2008-10-11 21:10 ` Alan McKinnon
2008-10-11 22:56 ` Dale
2008-10-12 21:47 ` [gentoo-user] " James
2008-10-14 15:04 ` [gentoo-user] " Neil Bothwick
2008-10-14 20:11 ` Dale
2008-10-14 15:05 ` Neil Bothwick
2008-10-14 20:13 ` Dale
2008-10-11 20:50 ` Alan McKinnon
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=48F11D55.5030906@googlemail.com \
--to=daniel.pielmeier@googlemail.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