KaOS, Digikam, and Monday Technical

I noted last week that Digikam does not run well with debian. This includes the Appimage. I want Digikam in my photo flow.

So, I’ve looked at other issues. Opensuse and me don’t work well together. I need something reliable, that has been around for a while, and that runs plasma. The alternatives are endeavour OS (which is running on the laptop) and KaOS. I’ve backed up everything, and am moving to KaOS.

KaOS sees a lack of focus in that respect. To create the highest quality Distribution possible, there needs to be a focus to make sure the user gets the best possible for whatever choice they made. It simply is not possible to package any and all to work perfect for every Desktop Environment or Toolkit.

KaOS has made the choice to use the Linux kernel as a base (though the Illumos kernel is under constant evaluation, and a future switch is a wish). After that choice, the best available package manager, most flexible way of package building, repository maintenance is pacman/makepkg for a rolling distro like KaOS. As for the Desktop Environment, there will never be a change, whether it is Linux or Illumos based, KDE Plasma will be the choice, Qt the Toolkit. With those choices in place, April 2013 package building for this independent distribution was started. KaOS is a build from scratch distribution, every package in every repository is build by and for KaOS. By July 2013 the initial goal of about 1500 packages was reached.

But there are issues: my very old desktop needs a DVD burned to boot. I am switching the laptop over and reinstalling things: a tuned Arch distro is a nice compromise.

Due to the file system used for compressing the KaOS ISO, creating a bootable DVD ISO needs one clear warning. Any burn-speed used above 4x will likely result in an unusable DVD. On virtual all Linux Distributions, this is no issue.

This is a problem, as k3B is very difficult to slow down… but xfburn does do this quite well.

In the meantime, my employer(s) are both moving to Office 365. For good reasons, they need to be firewalled, so I got an apple phone for one job. Mistake — not iOS, but its interface with work’s software. Let’s just say that that phone is sat in the IT department getting fixed for three days and at times had three IT techs working on it, and I normally set up my phones by hand without breaking into a sweat.

Makes me think that when my chinese Android clone phone dies, go cheap, go linux, go Pinephone. Because you can fix it.