*nix may not update itself, but some are still 'phoning home', which to me is about as bad as one component updating itself. And 'asking for permission to update'...
The 'self update'/automatic updates are for the 99% of other users who do not want to know what is happening.
And if they get a 'something ready for you' popup/baloon/whatever (on MS or *nix) they will simply click 'ok' to get rid of it.
Do you actually check what updates you get and selectively answers yes/no? (btw I do with WSUS although I have setup a lot of defaults)
Until users get educated (or a 'drivers license' is required for the internet) automatic updates is about the only thing to do really, I'll bet you that when *nix gets above 50% of the desktop market everybody will want to have automatic updates activated except for the select few.
Bashing Microsoft is easy (hey I do not like them at times, certainly not as a programmer) but I am not going to run *nix and miss 90% of the programs/hardware I use. UMPC with touchscreen under *nix anyone?, I said *with* touchscreen! Oh, and do remember the hardware is there because there are enough *windows* users to want it, I have not seen consumer hardware inovated because it is used by *nix users.
(exception is maybe the iPhone but that is to closed a system still)
Until *nix groupies get of there lazy backs and develop some more drivers I will be running MS*something so I can do what I want to do.
I do not want to remember the number of times I installed XP to see what hardware there is in the system (and the parameters used) and only then I could fire-up a Linux distro and answer all those questions about hardware it could not detect correctly.
Back to the origional problem: the article writer simply didn't know what he was doing, making his tandrum just something to

about.
End of line.