Sven Burmeister said the following on 12/10/2011 07:54 AM:
Sorry, but to me your argumentation does not make sense – or to be more precise, it is not consistent. Either your users have no clue or they do. If they have no clue they should not install updates. If they do, there is no issue.
If you allow users without clue to update, they will just install whatever update is shown to them. This is no different than having a cron job installing updates automatically. You can just put a script on their computer that accepts all EULAs and does the updating.
+1 And I suspect that even many "smart" users and sysadmins just apply the issued updates; after all they are PGP-signed and come from the opensuse servers, so they must be right, right? Heck, I recall starting at one site and seeing a strange guy at the console of the roomful of AIX servers. He had a visitors badge and refused to answer when I asked what he was doing. I called security and the IT manager. It turned out he was from the OEM vendor and been coming in every month to apply patches/upgrades from a CD. It was in the support contract, but the IT department were unaware that he was simply applying the upgrades without telling anyone or reporting that the upgrades had been done, and there was no "change management" or "impact analysis". Of course this incident brought about changes to the process! But really, what could they do? Can you say, no we don't want upgrades! Are you in a position to examine the impact of making or not making each and every update? I realise some large corporations are, but are you, Malvern, in that position with respect to openSuse? Do you have a test-bench facility to verify the impact of every change before allowing the update? Because if you don't, and if you, like I suspect better than 90% of openSuse users, just accept and apply the updates, then there is no reason NOT to have them done automatically by CRON. In the corporate environments I've worked and been supplied with a Windows workstation or laptop and all the 'roving share' stuff, the login/start-up scripts often delay the start-up while they download the latest upgrades. The users have no control over this. By the time the GUI comes up and they can start work the updates have been applied. If you choose to treat your users dumb, not give them fine control over their machine configuration, then applying the upgrades "behind the scenes" with CRON or ACRON invoking zypper makes more sense than complaining about Apper/KPackageKit. But as I keep saying, if you really want problems, then yes, upgrade them to 12.1. -- An ounce of action is worth a ton of theory. - Friedrich Engels -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org