• 2 Posts
  • 45 Comments
Joined 2 months ago
cake
Cake day: February 13th, 2025

help-circle


  • Another thing is that my laptop might be using Legacy BIOS, so systemd isn’t compatible with it.

    Oh sorry, then Fedora isnt a good idea. They have deprecated support for Legacy BIOS.

    Anything with LXQT 2.1 available should give the same experience however right now it seems only rolling distros ship with 2.1. Lubuntu 25.04 will ship (in ~April) with LXQT 2.1 but it wont default to wayland so you might have to do some manual config. Its also not an lts release.

    storage requirements

    shouldn’t be a big problem. lxqt is super lightweight. If you go with lubuntu, I recommend turning off snap to save some space.

    Linux Mint MATE or XFCE are really good if you dont necessarily want wayland support.

    Another option is the Raspberry Pi OS. Debian based, should be very lightweight and runs wayland. I haven’t personally tried it though.




  • Element is an app for “Matrix” (thats like lemmy but for discord) that is developed by a for-profit company (the company mostly manages deployments for big governments). But not only is it open source, its just one client of many for matrix. The vast majority are developed by individuals (Cinny, FluffyChat).

    Plus, it’s not even remotely similar to Discord.

    There are probably discord features missing from matrix but they certainly have a lot of similarities. Though tbf Cinny is the closest to discord in terms of design and functionality not element (but they both are matrix clients).


  • I mean Fedora is open source but if they really wanted a european base, they could have gone with opensuse. AFAIK opensuse is the only fully european linux distro plus they use many of the same tech that redhat/fedora does.

    Ultimately I think it doesn’t matter too much since even the linux foundation is based in the US and large parts of what makes the linux desktop are maintained by non-EU companies (on top of all the major projects hosted by Github, Gitlab including most of Flathub). If its all open source, I think the risks are pretty low e.g. huawei was able to use Android despite all the restrictions.





  • One thing I’m doing differently in Arch this time is I’m trying out installing as many things as possible as flatpaks. I’ve successfully ignored them until now. Surprisingly, a lot of my apps are already packaged as flatpaks.

    Yeah I have grown a liking to flatpaks too but I dont think I can live with only flatpaks yet.

    The other thing I’m borrowing is distrobox+podman. I didn’t know about that before. This seems useful for dev environments.

    Distrobox is really nice, I even run some gui applications in containers.

    That being said, I’ve never had a problem with pacman breaking my system, so I don’t see major value in doing this… other than… it’s helping me procrastinate! I should be doing real work right now. 😄

    This is the only thing keeping from arch tbh. I shudder to think of all the ways I can procrastinate on arch!








  • Unfortunately it seems to be a completely proprietary kernel. I did find a paper on it (presented by Huawei in a conference): https://www.usenix.org/conference/osdi24/presentation/chen-haibo

    The first line of the abstract reads

    This paper presents the design and implementation of HongMeng kernel (HM), a commercialized general-purpose microkernel that preserves most of the virtues of microkernels while addressing the above challenges.

    Another interesting tidbit from the paper:

    We started the HongMeng kernel (HM) project over 7 years ago to re-examine and retrofit the microkernel into a general OS kernel for emerging scenarios. To be practical for production deployment, HM achieves full Linux API/ABI compatibility and is capable of reusing the Linux applications and driver ecosystems such that it can run complex frameworks like AOSP [42] and OpenHarmony [35] with rich peripherals.


  • thats a very fair point, I had not seen anyone else make this one But the problem is that in this case, this functionality was entirely undocumented. I dont think it was intended for programmers.

    Now if the firmware was open source, people would have gotten to know about this much sooner even if not documented. Also such functionality should ideally be gated somehow through some auth mechanism.

    Also just like how the linux kernel allows decades old devices to be at the very least patched for security risks, open firmware would allow users of this chip to patch it themselves for bugs, security issues.


  • It was a skin, now its a completely different OS. The initial version, HarmonyOS, was based on Android/Linux, the new HarmonyOS Next, is a proprietary version (or successor) of HarmonyOS based on an open source project/OS, OpenHarmony. It uses a new microkernel instead of the linux kernel.

    OpenHarmony is essentially an open source base for making an operating system on top. Its not like the Linux kernel, in the sense that its not just a kernel (in fact you can use the linux kernel with it), but rather a bunch of components people can build upon. And since it uses a permissive license, you can build a proprietary OS on top of it (like the HarmonyOS Next).

    Huawei actually launched OpenHarmony many years back but it was not ready for phone usage yet. It was only with the launch of the 5th version that Huawei was confident enough in it to start using it on their own phones.