Closed JFLim1 closed 2 years ago
kernel.org
will release a new version of the kernel, unifreq will synchronize and compile the latest kernel, and I will refactor the new kernel to the latest firmware for release. (This update can be achieved through armbian-update
)debian
and Ubuntu
upstream will fix some bugs and update new features, these can be updated with apt update
armbian
official will add new features or fix bugs from time to time, but these generally do not affect the firmware being used.wget
Your suggestion is very good. I think it is possible to do a [one-click script management] to upgrade, maintain and add services in a way similar to armbian-config.
- Every Wednesday or Sunday,
kernel.org
will release a new version of the kernel, unifreq will synchronize and compile the latest kernel, and I will refactor the new kernel to the latest firmware for release. (This update can be achieved througharmbian-update
)- Every week
debian
andUbuntu
upstream will fix some bugs and update new features, these can be updated withapt update
- The
armbian
official will add new features or fix bugs from time to time, but these generally do not affect the firmware being used.
@ophub Item 1, 2 and 3, have been performing them since installing the image on 2022-01-16. Started with kernel 5.15.15-flippy, older armbian-config, armbian-firmaware and now upgraded to kernel 5.16.16-flippy-71+ and armbian-config v22.02.2 and armbian-firmware v22.02.2, etc.
4. For some other scripts, you can generally download the specified script to your own device through
wget
This I have not done. Not familiar with the script/features to the newer builds.
I think it is possible to do a [one-click script management] to upgrade, maintain and add services in a way similar to armbian-config.
This will be a good feature which will be much easier for newbie to perform and basically have a new image just like your newer pre-built images.
I think this will be better option than performing Item 4 especially for many users.
Edit: Read with interest on your new image now uses /extlinux/exlinux.conf instead of uEnv.txt. What are the advantageous? How to convert the existing firmware using uEnv.txt to /etxlinux/extlinux.conf? Thanks.
Hi @ophub
Just a feedback. I am currently running one of your earlier build Bullseye (Package Date = 2022-01-16).
Noticed that you made quite a number of changes or added features to your newer pre-built images.
Is there a way to include all the new features that you have added to the older image by installing a package onto older image without having to re-flash a new image? It will good to have this option.
Just one example like you have now change from using uEnv.txt to /extlinux/extlinux.conf.