Menu

Disable and Re-enable automatic updates

Follow

Comments

16 comments

  • Avatar
    Lasse Bachmann (Edited )

    NP hope it'll help ya'll. Note that you can test the compatibility of future build by writing to USB and booting without installing: if you log in and test and things are working it'll *MOST LIKELY* be safe to turn on automatic updates on to get the ota.

    Don't pin me up on this though, hence: *MOST LIKELY*

  • Avatar
    tijndesign (Edited )

    Hi Lasse, Thanks for the instructions.
    57.1.91-64bit is giving me troubles on the Macbook late 2008 so I want to stick to cloudready-free-56.3.82-64-bit. but there is only one small issue..

    When I follow your instructions I get: mv: cannot move '/etc/init/update-engine.conf  to '/etc/init/update-engine.conf.backup' : Read-only file system. ?

    the steps I have taken
    - install V.56 stand alone from USB
    - Boot from mac and login with my Google account
    - Pressing "Alt + Ctrl + t"
    - followed your instructionsbut after #3 I get: Read-only file system.

    This "shell thing" is completely new for me so I guess I'm doing something wrong.

    Hope you or anyone else can give me some help

    Best regards,Tijn
    the Netherlands. 

  • Avatar
    Joseph Honnoll (Edited )

    Added to My Guide LINK

     

     

  • Avatar
    Forrest Smith

    Updated this article with alternate method that should remain functional release-to-release.

  • Avatar
    CLFORD (Edited )

    NEWBIE Question...

     

    Are the 3 lines of commands in step 7 supposed to all be typed before hitting enter, or do I hit enter after each line? If its all one command, should I assume a space at the end of each written line or not?

  • Avatar
    Joseph Honnoll

    I believe you just copy/paste the whole 3 lines in cmd or copy/paste each code line

  • Avatar
    Forrest Smith

    Yes - one big command.

  • Avatar
    Jakub

    Hi maybe stupid question but how can i reverse that after i lost that release.bak backup?

  • Avatar
    Jakub (Edited )

    I figure this out, if someone else will want to do this you need to change to proper update server addresses, ready to use line of code:

     

    sudo sed -i '/CHROMEOS_AUSERVER/c\CHROMEOS_AUSERVER=https://cloudready-free-update-server.neverware.com/update' /etc/lsb-release && sudo sed -i '/CHROMEOS_DEVSERVER/c\CHROMEDEV_AUSERVER=https://cloudready-free-update-server.neverware.com/' /etc/lsb-release

  • Avatar
    Forrest Smith

    Reinstalling is really the way to go if you get in a pickle with CluodReady - that will always reset things back to the original format.

  • Avatar
    Carmelo

    Hi Forest (or anyone that can help), I have a couple of questions.  

    Does this change affect all users or just the account that I'm signed into?  

    I followed the instructions and no errors were reported, however when I go to About Chromium OS > Check for updates, it behaves as before (checking for updates... then says Your Chrome device is up to date).  I just installed yesterday with the current version and so I imagine that it is correct that is up to date.  When there is an update available, I hope that it will not be installed.  Is there any way that I'll know if the change has been applied as intended? (without waiting for the next version and seeing if it updates or not)

    Thanks for your help!

    Writing from Calgary, Canada

  • Avatar
    Joseph Honnoll

    HI,

     

    From my experience it does change for All Users. Why would you want to Disable by chance?

  • Avatar
    Carmelo

    Hi Joseph, I am setting up a laptop for someone that rarely uses it, and he only uses when internet is tethered to his smartphone, and he has a limited data plan.  Don't want to consume data downloading updates.  I gave him this laptop originally with Windows 10 on it, and it was downloading so many updates that it would consume lots of data (no surprise).  Afterwards I realized that I could set the connection as a metered connection in the wifi settings in Windows 10, however that doesn't stop downloading all updates, just some of them.  Also, he has limited knowledge of computers, so if it's working fine I don't want CloudReady to download an update that breaks it.  I can get his computer once in a while from him and update it myself when I choose to.   

    I did some more playing around with the server addresses in the /etc/lsb-release file and even when I put both servers as xxx, the machine still behaves as before (checking for updates... then says Your Chrome device is up to date).  

    So there must be a better solution so that after I'm done making this change, instead it would report, could not check for updates or something to that effect.

    I assume that you've successfully disabled updates on your CloudReady system.  If so when you check for updates what happens on your system?  What does it report?

  • Avatar
    Joseph Honnoll

    It says your system is Up-to-Date or gives an error (Can't remember) but either way no more updates unless YOU re-Enable the Auto-Update Function

  • Avatar
    Jakub

    it will always show Up-to-Date

  • Avatar
    Forrest Smith

    There's no "disable updates" trick that will give you proper feedback in the UI that I know of - but if you've permanently edited the update URLs as described here, rest assured that there's no issue.

     

    Since we just updated to v61.2 on our dev channel, you can test your fix by switching the machine to the dev channel and checking for updates - see if the new dev release downloads or not.

Please sign in to leave a comment.

Powered by Zendesk