Mailinglist Archive: opensuse-bugs (13069 mails)

< Previous Next >
[Bug 464453] Disabling automounter during installation does not work
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 22 Jan 2009 05:03:13 -0700 (MST)
  • Message-id: <20090122120313.F4056245390@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=464453

User vuntz@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=464453#c30


Vincent Untz <vuntz@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|vuntz@xxxxxxxxxx |aschnell@xxxxxxxxxx




--- Comment #30 from Vincent Untz <vuntz@xxxxxxxxxx> 2009-01-22 05:03:12 MST
---
(In reply to comment #22)
Yes, glib is the culprit. I already get blamed for the dependencies of
yast2-storage so I won't add more.

How can glib be an issue if hal is not?

vuntz@lyon ~/>rpm -q --requires hal | grep glib
dbus-1-glib >= 0.61-1
libdbus-glib-1.so.2
libglib-2.0.so.0

(In reply to comment #28)
Why do I have to hack something in the last minute? Just as well the
former solution can be hacked back.

The former solution is not upstream and it will not be accepted upstream. I'm
proposing a solution that works as well (if not better because this mechanism
is used by more people) and that doesn't require patching all applications that
can automatically mount devices.

And as far as I can tell, the only reason to not use this solution is a
packaging issue. This just sounds wrong, I'm sorry. And I'd really like to
avoid putting this in a GNOME-specific package because we certainly want the
solution to be valid for non-GNOME stuff.

So here's another proposal, to solve it the right way:

+ to lock: hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive
--run "sh -c 'while true; do sleep 60; done'"

+ to unlock: kill the previously launched hal-lock

No new dependency. How does that sound?

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References