https://bugzilla.novell.com/show_bug.cgi?id=464453 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c27 Vincent Untz <vuntz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #27 from Vincent Untz <vuntz@novell.com> 2009-01-21 05:11:16 MST --- Can we step back a bit here? It just sounds wrong to close the bug because of a packaging issue. A few comments: + as I already mentioned, yast2-storage already depends on glib indirectly (through hal), so glib is nit really a new dependency. + the small tool I wrote is only an example. You can take the relevant code and integrate it in yast2-storage. libhal_acquire_global_interface_lock() is the important function. + if you don't want those solutions, you can still hack something around hal-lock. Just launch hal-lock with a small program that will read from, say, a UNIX socket, and will exit when yast writes something to this socket. This will remove the lock. -- 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.