9/27/2023 0 Comments Alpine linux versionsYou can test if your environment variable was set: Now that you have your /etc/lbu/lbu.conf configured for your needs, we will set the environment variables (note the leading. But remember that both the media where you have your Alpine system AND the media where you have your config need to be in your box when booting it. Note: Even if you have you alpine installed on CF, HD or USB you can still choose to save your config on some other media that suits your needs. The media you choose will be the media where you store your settings/configuration. You also need to set a appropriate value for your LBU_MEDIA. Make sure that the variable LBU_MEDIA is not commented (by removing the leading '#'). To make the documentation a bit more "generic" we start by setting some environment variables. That is what the following steps describe how to do. For the general solution, you'll need to upgrade your boot medium (Compact Flash or USB). However, this is not an adequate general solution because it won't honor any kernel upgrades and the like. (If you want the new packages to be used after a reboot, you should enable APK caching.) Updating your repositories using the procedures detailed above, then running: The following instructions are for run-from-RAM Alpine installations running on Compact Flash or USB media. Lbu ci Upgrading Alpine Linux on other removable media (such as CF/USB) If the kernel is upgraded, it's required to reboot to begin using the upgraded version:Īfter upgrading the packages, save the upgraded configuration changes. Note: All services that have been upgraded need to be restarted, to begin using the upgraded version. If you have locally installed and configured additional packages using APK caching you should also perform the following steps.īackup the local configuration prior to upgrading. If booting from a CD, this would simply mean replacing the CD with a CD made from the new image and rebooting the Alpine Linux box. If the boot media being used (such as a CD, for example) is separate from the media used to store the configuration information, simply download the latest ISO, and replace the boot media contents with the contents of the latest ISO. Either use edge or stable.Īfter upgrading to edge, the currently installed edge version may be checked withĪnd referring to the build date that is attached to the release. Warning: Do not enable stable and edge repos at the same time. Note, subsequent manual changes of the version numbers in /etc/apk/repositories may be avoided for future release upgrades by having the repository lines refer to "latest-stable" instead of an absolute value: Or, use a one-line command to edit all version numbers in the file "in place".Then editing the repository lines to reflect the new version number. Setup-apkrepos and pressing e to edit /etc/apk/repositories. Launching the corresponding Alpine setup script,.However, for specific info always refer to the appropriate release notes.įirst thing is to to edit or check the /etc/apk/repositories file.īesides doing it manually (see below) this may be done using one of the following shortcuts. on a hard drive, upgrading to the next stable version should be a straightforward package manager operation. When Alpine Linux is installed in sys mode, e.g. not just upgrading from the last release to the subsequent version as covered by the individual release notes, also check Upgrading from older versions for potential specifically required upgrade steps. In case an older version needs to be upgraded, i.e. Upgrading an Alpine Linux Hard-disk installation Upgrading from older versions Warning: Before actually upgrading your system, make sure that you have a backup of your important data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |