Difference between revisions of "Blocking Updates"

From WebOS Internals
Jump to navigation Jump to search
(credit to bottom, comments to discussion)
Line 1: Line 1:
Here is a quick and dirty way to block webOS updates brought to us by "psykoz"
+
Here is a quick and dirty way to block webOS updates.
  
 
'''We do not recommend doing this.'''
 
'''We do not recommend doing this.'''
Line 21: Line 21:
  
  
Comment:
+
'' brought to us by "psykoz"''  
What's the advantage in doing this? Is it to avoid mods being reverted? Doesn't it make more sense to keep backups of all changed files somewhere, accept updates, and then reintroduce your changes? - //This would be useful in the event a future update were to eliminate access to the Pre.//
 
 
 
 
 
 
''Ported by hopspitfire''
 
''Ported by hopspitfire''

Revision as of 18:23, 20 July 2009

Here is a quick and dirty way to block webOS updates.

We do not recommend doing this.

webOS is in a very early stage. One webOS-internals team member (tharris) has through 20 July 2009 identified over seven security errors in webOS, and that process is far from done.

Additionally, updates like the forthcoming 1.1 (as of 20 July 2009) will make available new functions including accelerometer to the mojo interface.

This is only for the truly paranoic - 1.0.3 did not break anything, and we always have the older webOS Doctor to reinstall an older version of webOS if something does get broken in the future.

Never the less, if you insist on turning off updates, this should work.

cd /usr/bin
mount -o remount,rw /
chmod -x *Update*
mount -o remount,ro /

No more executing the update program.


brought to us by "psykoz" Ported by hopspitfire