On Tue, 7 Oct 2014 18:24, Shawn W Dunn <sfalken@...> wrote:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
* alanbortu <alanbortu@...> [10-06-14 18:46]:
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
Why would you do rpm -e instead of zypper rm? I don't get it.
Because zypper looks deeper into dependencies and recomments, and will, based on that in some cases more or less try to remove your whole system instead of just the package you want to be removed. In my case, I did a "zypper al '*PackageKit*' '*packagekit*' 'apper'" on the second try of installing beta1 to avoid even installing that piece of software. My box runs much better without. zypper and rpm are enough for most of my needs, for anything else, there is yast. - Yamaban. --