Difference between revisions of "Blocking Updates"

From WebOS Internals
Jump to navigation Jump to search
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
Here is a quick and dirty way to block webOS updates brought to us by "psykoz"
 
−
 
 
'''We do not recommend doing this.'''
 
'''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. 
+
Updates provide important security patches as well as new features and bug fixes. One webOS-internals team member (tharris) has identified over seven security errors in webOS as of 20 July 2009, 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.  
+
That being said, sometimes an update only disables functionality, such as the 1.0.4 update, which prevented apps from being installed through email link (but which was required to fix a huge unintended security hole).
  
−
Never the less, if you insist on turning off updates, this should work.
+
Here is a quick and dirty way to block webOS updates:
  
−
<pre><nowiki>
+
<source lang='text'>
 
cd /usr/bin
 
cd /usr/bin
 
mount -o remount,rw /
 
mount -o remount,rw /
−
chmod -x *Update*
+
chmod -x UpdateDaemon
 
mount -o remount,ro /
 
mount -o remount,ro /
−
</nowiki></pre>
+
</source>
 +
 
 +
Then, either reboot or execute:
 +
 
 +
<source lang='text'>
 +
killall UpdateDaemon
 +
</source>
  
 
No more executing the update program.
 
No more executing the update program.
  
 +
== Re-Enable Updates ==
  
−
Comment:
+
If you disabled your update you might want to re-enable it at some point.  
−
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.//
 
  
 +
<source lang='text'>
 +
cd /usr/bin
 +
mount -o remount,rw /
 +
chmod +x UpdateDaemon
 +
mount -o remount,ro /
 +
</source>
  
−
''Ported by hopspitfire''
+
Then restart your phone and automatic updating should be back.

Latest revision as of 08:55, 11 September 2009

We do not recommend doing this.

Updates provide important security patches as well as new features and bug fixes. One webOS-internals team member (tharris) has identified over seven security errors in webOS as of 20 July 2009, and that process is far from done.

That being said, sometimes an update only disables functionality, such as the 1.0.4 update, which prevented apps from being installed through email link (but which was required to fix a huge unintended security hole).

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

<source lang='text'> cd /usr/bin mount -o remount,rw / chmod -x UpdateDaemon mount -o remount,ro / </source>

Then, either reboot or execute:

<source lang='text'> killall UpdateDaemon </source>

No more executing the update program.

Re-Enable Updates

If you disabled your update you might want to re-enable it at some point.

<source lang='text'> cd /usr/bin mount -o remount,rw / chmod +x UpdateDaemon mount -o remount,ro / </source>

Then restart your phone and automatic updating should be back.

Retrieved from "http://wiki.webos-internals.org/index.php?title=Blocking_Updates&oldid=5637"