A short reply to myself.. ;) On Monday 09 April 2007 03:43:28 [EMAIL PROTECTED] wrote: > Is there any way stopping the kernel from inotify-ing a directory? Couldn't > find one yet. > So we could add a test to the ebuild, whether it is a upgrade from <0.5.9 > and prevent reloading of the files until the next reboot. > Maybe this could find it's way into an eclass, because other > applications/daemons like dbus will surely suffer from the same problem > when having the next $PV_MAJOR upgrade, so we could use the functions > global. Should I open a bug for tracking this issue? I've asked the dev of inotify-tools how to do this... it looks, like the information which file/directory is currently being monitored is not exported by the kernel, so we can't do a general check for monitored files of a package that is updated. Instead it's only possible, to exclude directory $FOOBAR from being watched (without checking, whether it was really watched before by inotify). => Postpone this eclass plan to $SOMEDAY, use ewarn instead.
> > And it is good to know that some people are using KNetworkManager - I > > don't have a machine currently with KDE installed (my KDE machine died) > > and so I haven't tested it at all recently. > > KNetworkmanager works really fine here, except of some troubles concerning > ipw3945+WPA which should be fixed in the next NetworkManager release (I > hope it gets released soon, currently, my WLAN is only WEP "encrypted" :-/ > ). Some other KDE (and probably Gnome, XFCE, etc.) related problems occured: When plugging in my USB stick or my external USB HDD, I can't mount them anymore: Permission denied: Not in active session I found two bugs in the RedHat bugtracker about this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232674 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229465 Currently, I'm trying to track down where this comes from on Gentoo. It looks, like $XDG_SESSION_COOKIE isn't set, but I didn't find out yet, how this is set in Gentoo/KDM. Also kpowersave started crashing, I've written to powersave-devel because it seems they don't have a bugtracker: http://forge.novell.com/pipermail/powersave-devel/2007-April/000763.html Until this isn't resolved, 0.5.9 shouldn't go stable. I've opened a bug for tracking this: http://bugs.gentoo.org/show_bug.cgi?id=173892 Regards, Elias P. -- gentoo-dev@gentoo.org mailing list
