Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Berryboot self update functionality #371

Open
macmpi opened this issue Feb 20, 2017 · 8 comments
Open

Berryboot self update functionality #371

macmpi opened this issue Feb 20, 2017 · 8 comments

Comments

@macmpi
Copy link
Contributor

macmpi commented Feb 20, 2017

Hi,

I would like to update Berryboot with latest without touching installed distributions, nor moving around microSD card.
I've unsuccessfully searched for "Berryboot's built-in self update functionality" mentioned here: can you please explain how it works?

Also would be nice if Berryboot could display current running version number in some window (like within "?" window button)?

Thanks.

@macmpi
Copy link
Contributor Author

macmpi commented Feb 27, 2017

I guess @maxnet needs to set stuff in [berryboot] section within http://dl.berryboot.com/distro.smime in order to trigger such update, right?
Any chance this may be activated?

@macmpi
Copy link
Contributor Author

macmpi commented May 31, 2017

@maxnet would it be possible to make available latest 20170527 release within http://dl.berryboot.com/distro.smime so that we can effortlessly update to latest, without wiping all existing images?
Thanks in advance.

@maxnet
Copy link
Owner

maxnet commented May 31, 2017

I usually wait some days after releasing a new version on the website, before offering it as update to see if any new issues pop-up.

If you want to upgrade sooner, simply extract the zip on the website to the FAT partition of your card, and select "use existing files" during installation.
Or do not overwrite cmdline.txt

@macmpi
Copy link
Contributor Author

macmpi commented May 31, 2017

Don't I need to gzip -dc /boot/shared.tgz | tar x -C /mnt/shared too?

So, is the "manual" method below ok:

  • download new version and replace all files in FAT, except cmdline.txt and config.txt
  • boot SD (will it boot fine due to updated kernel and old /mnt/shared modules discrepancy ?)
  • under console, do gzip -dc /boot/shared.tgz | tar x -C /mnt/shared
  • reboot again -> done!

@maxnet
Copy link
Owner

maxnet commented May 31, 2017

Don't I need to gzip -dc /boot/shared.tgz | tar x -C /mnt/shared too?

Only if you do not overwrite cmdline.txt
If you do overwrite it, and select "use existing files" during installation, the installation procedure will do that for you.

@ghost
Copy link

ghost commented May 31, 2017

Hey,

first of all I would like to say that I love your work and support. I followed all you steps: DL the actual ZIP, extracted it, overwritten all files and started berryboot.

Since the new update my CEC is now working. Thatś awesome.

Thank you!!!

Greetings from Germany.

@macmpi
Copy link
Contributor Author

macmpi commented Jun 1, 2017

Thanks for the clear instruction @maxnet , updated with cmdline.txt overwriting (preserving original).

Then how can we tell which Berryboot version we are using, from Berryboot menu screen or console?

@macmpi macmpi mentioned this issue Jul 1, 2017
@macmpi
Copy link
Contributor Author

macmpi commented Feb 17, 2018

@maxnet the cmdline.txt overwrite method may not work in cases where cmdline.txt contains necessary partition schemes information (encrypted, full MSD boot,...).

Couldn't such manual update be triggered by existence of a specific file in boot partition (like update), instead of current logic on existence of declared partitions incmdline.txt?
This would allow to simply do the update while leveraging existing parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants