public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Replacements for ivman
Date: Sun, 12 Oct 2008 21:47:04 +0000 (UTC)	[thread overview]
Message-ID: <loom.20081012T213807-446@post.gmane.org> (raw)
In-Reply-To: 48F12F34.1020107@gmail.com

Dale <rdalek1967 <at> gmail.com> writes:


> > How have you got it set up and how long has it been that way? 
Experienced any 
> > brokenness while it's been in use?

> Basically, I just emerged it and restarted KDE.  It just worked.  I
> don't recall changing anything as far as configs go.

> It has been that way for a pretty long while.  I did have a version
> problem once a while back.  I think it was when udev made some changes
> or something, but hal and ivman sort of had a fight over devices like my
> camera.  Hard drives were fine tho.


Yep, same thing here

rc-status:
dbus                                                                 
hald
ivman

It just seems to work. A while back I tried to find accurate and current docs.
That's when I got confused. It really would be nice if this was all documented
well somewhere. Occassionally, a usb device is not discovered, and then
I manually try to find traces of it, using a variety of usual tools. If not
successful then I result to brute force searches of /dev .....

Most often, Konqueror, not my browser or choice, pops up when a unknown 
usb devices is popped up. That my starting point and it works most
of the time.


I'd personally settle for a master index of products and devices
and a manual udev entry example to accompany said product/device;
as a catchall type of xml/database, for the millions of devices
out there.....

Going from manual discover to a working udev rule, has always been
a painful process for me.

hth,

James




  reply	other threads:[~2008-10-12 21:47 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
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           ` James [this message]
2008-10-14 15:04           ` 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=loom.20081012T213807-446@post.gmane.org \
    --to=wireless@tampabay.rr.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