-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Monday, 2008-10-06 at 11:40 +0200, Bernd Nies wrote:

...

I would like to disable/remove the opensuse updater panel applet because we don't want the users to be notified about updates every time they log in. Some updates (kernel) cause the system to be unusable because the Nvidia driver and VMware modules need to be recompiled.

For KDE i do "rpm -e kde4-opensuse-updater" in an Autoyast installation script. But I did not finde it's GNOME compliant. Must be somewhere integrated in GNOME desktop but I did not find distinct binary for this.

Any ideas?

I think it is gnome-packagekit.

A trick I used in the past was to disallow execute for all attribute on the executables, so that users have to belong to a specific group to run it. But this one contains several executables and I don't know which one to change - or all:

* /usr/bin/gpk-application * /usr/bin/gpk-backend-status * /usr/bin/gpk-install-local-file * /usr/bin/gpk-install-mime-type * /usr/bin/gpk-install-package-name * /usr/bin/gpk-install-provide-file * /usr/bin/gpk-log * /usr/bin/gpk-prefs * /usr/bin/gpk-repo * /usr/bin/gpk-update-icon * /usr/bin/gpk-update-viewer

- -- Cheers, Carlos E. R.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkjp33EACgkQtTMYHG2NR9XR1ACfZqUhBp1NilLGDH5wsMG3ibqV zL4An2scOwvjkUXNkbnfxhf9QGH9II7Z =S36d -----END PGP SIGNATURE----- --

Hey, should we think in another way ? See, if we update our kernel, the softwares which are installed by YaST can run still, But the softwares we "make & make install" ourselves don't work, unless we repeat the work of "make & make install" ? Is there any solution to this ? Or just make the YaST auto do it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 10/06/2008 07:03 PM, Carlos E. R. wrote:

For many reasons, it is a mistake to let a plain user updated a system, that is the task of root, or the user running as user but that happens to be root too.

Thus, it is also a mistake to offer a plain user to upgrade the system. Better not to bother him. It is also a mistake to run the update applet for every user that logs into the machine. It should only run for that user of users that maintain the machine. It is also a waste of resources.

Thus, there should be a configurable list of users that will get the applet running automatically (all, some, none).

So, as we don't have that feature, what hack can we do to imitate it?

Maybe it would suffice to not auto load at login by default, i.e. off by default, but when a user starts it it prompts (like some do) whether to start always, assuming the user that goes to the trouble to start it probably knows what they are doing. That user should be the user that does possess the root password. No root password then it would ignore the always start option. Seems doable for a programmer, which I am not. :-) -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org