Hello, I’m completely new to arch based linux distros, and so for berryboot.
I installed with berryboot some OSes on my Raspberry Pi 3B+ and figured out how to configure the WLAN internet access.
Then I wanted to upgrade the 19.06 with pamac, but it wasn’t able to upgrade the databases.
Therefor I tried pacman and pacman-mirrors, but I only got 404 errors for the repository.
I learned almost nothing. Thanks anyway. I’ll download an Image with 19.06 and try to upgrade that instead to learn the upgrade process and handling of package conflicts, mirror-lists, pacman, pacman-mirrors, pamac and so on.
I feel for the op. He thinks this is a simple matter of adjusting his sources and bam he’s off to the races. And if he wanted to do that and only that, he could probably find that through a web search. But as Strit has said what he did to install it isn’t supported, I won’t provide those links.
Now the real problem that the op isn’t grasping is as has been stated plainly, the image he wishes yo use is 2 years and more out of date and its very likely that it won’t update correctly, no matter what.
So finally, as has been stated get an updated image of 21.06 and copy it with imager to a micro SD card.
This is the far easiest solution to resolve that problem.
Ask me how I know.
I’ll tell you its because I have tried to use old image files from other distros and they always require a lit if extra work and rarelyif ever work.
Okay then. I appreciate your answers. Despite my experience to upgrade ubuntu LTS to LTS, I have to admit, that I doesn’t have any experience with rolling release distributions and arch distros. That said, I was eager to try the upgrade anyway to maybe learn upgrades the hard way, but I only found one torent file with the original release Manjaro-ARM-lxqt-rpi3-19.04.img.xz (not prepared for berryboot with sqashfs etc.). The torrent got no peers, so it won’t download.
So I have two options: Using an upgraded image prepared for berryboot or following your advice and flash the current official image on a microsd to get a decent manjaro system which will then hopefully be upgradeable.
Also, I noticed, that Warnung: /etc/pacman.d/mirrorlist installiert als /etc/pacman.d/mirrorlist.pacnew gives the hint to move the pacnew to the mirrorlist.
I did so and ran directly into unmet dependencies and errors. So it won’t be a comfortable way to upgrade to the current packages.
Ubuntu and the like do incremental updates and a new point release every six months. If you tried to update a 2 yr old image from Ubuntu you could do it if you did it from one point release to the next but you would likely run into errors if you tried to go from a 2 yr old image to current without doing all the intermediate steps.
Rolling releases work by always giving you incremental updates. A point release image of a rolling release is just wherever the system happens to be at a given date, more or less. There is no upgrade path between point releases, except the incremental updates along the way. So with a rolling release you have the responsibility to keep your system up to date.
Aarch64 is almost exactly the same as manjaro arm and I see berryboot has aarch64 available.
Looking at berryboot a little more closely it looks like a virtual machine container something or other. I do wonder why they include such an old manjaro image by default for even their 2021 release…
Overall, lxqt I don’t like. Mate seems to have some lag, updating wasn’t so bad really.
When you change your mirrorlist to be an archlinux arm mirror - pacman-mirrors will be uninstalled.
The reason is that the package pacman-mirrors exist on both Archlinux Arm and Manjaro - despite both packages serves the same purpose - providing a mirrorlist - the content of the packages are very different - and mutually exclusive.
Its def some kind of VM container something or other as it uses a compressed image file. Unlike just installing an os, you can’t chroot into this manjaro machine when it is not active so if you bork it, you can’t fix it unless it boots.
I don’t think so. It’s simply a linux kernel which boots into the qt-menu of berryboot.
build system to create a minimal Linux operating system to run the boot menu under /package/berryboot/init - script that gets executed on boot, starts BerrybootUI
It does. Try accessing the berryboot system from another is, you can’t get into manjaro berryboot from another is the way you could any other is from just a file manager. You also can’t chroot into it. Don’t spam me with marketing dribble please. Just because they say its a booloading system doesn’t make it so.
I see why Strit doesn’t want to offer support for it. If you need support for berryboot problrms going forward you should def ask on their forums.