Magiilaro

Maybe Canonical will expand into Hardware now and release a matching RISC-V computer too. Would match the “we want to be the Apple of the Linux World” vibe I get from Canonical for years.

The law doesn’t say that the option has to be active for everyone and all the time, but it has to be fully integrated into the OS so it can be activated fast and easy when children/teenagers want to use the PC.

Since it is impossible to implement on Linux, it may just be flagged as adult-only software.

This would render Linux unfit for use in Schools, Public Libraries, Youth Centers and other places where Children and Teenagers have access to PCs.

It is, in addition to that, possible that internal regulation of government offices prohibit the use of adult software. Not sure about it, but it would IMHO fit the mindset of bureaucrats

It is in ratification, and will (most likely) become binding law by 1st of December 2025 in Germany

German link: https://rundfunkkommission.rlp.de/rundfunkkommission-der-laender/reform-des-jugendmedienschutz-staatsvertrages-2023

Microsoft already has the S-Mode in Windows 11 that only allows to execute apps that come from the Microsoft Store. So it is already possible in Windows.

I have seen with Oracle Java and OpenOffice (as two examples) that the open source community is very good in just leaving and forking a project if the current owners fuck up.

The same will happen with systemd if needed. Red Hat may be the primary source behind systemd now, but they don’t own it. All the code is fully open source, none of your ramblings have any hint of facts or any real foreseeable danger behind it. I asked for facts, for anything with some kind of real information behind it.

There is nothing that powers the claim that RedHat or IBM could take over Linux with systemd. How would they do it? They can’t, because even if IBM would tomorrow change the license to a closed one and would want money. Who cares, everyone will just fork the version before the license change and good is.

Just as it happened back then with Xorg (I mean the change 15 or so years ago, not the current strange fork), like it happened a short while ago with Redis, and there are so many examples more.

Unfortunately yes!🫩

Ok, but how to prevent programs installed as Appimage, by source compilation or just downloaded binaries from running? You need a way to prevent this methods of installation to be legal

To make something illegal by law it is needed to have a valid reason for that law to exist. This is the case at least in every jurisdiction that has a somewhat functional separation of powers.

Due to this can’t just make it illegal to use Linux, but with a Law like the Jugendmedienstaatsvertrag it comes as a free bonus.

Yeah, as it is so often 🫩

No it would not, because as soon as they implement such a blocklists feature and provide official blocklists they take over responsibility (morally and in some countries even legally) to ensure that they provide updated filter lists in a timely manner.

Oh and then they have to implement something that vets and checks incoming scam alerts, to ensure that only valid claims are blocked. This will put unneeded strain on the personal and financial resources of KDE.

And at the same time we have the Jugendmedienstaatsvertrag in Germany (and with Germany as a strong force in the EU most likely everywhere in the EU soon) that will make all operating systems without fully integrated age restrictions illegal https://www.heise.de/en/news/Minors-protection-State-leaders-mandate-filters-for-operating-systems-10199455.html

Manufacturers of operating systems must then ensure that “only apps that correspond to the age specification or that have been individually and securely activated can be used”. The installation of programs should only be possible via distribution platforms such as app stores that take the age rating into account and have an automated rating system recognized by the Commission for the Protection of Minors in the Media (KJM).

This part of the law alone is impossible to implement on a open platform like Linux.

I don’t think that it is the responsibility of KDE or Discover to perform blacklisting or cleanup here.

It is a upstream fuck Up by Canonical, again! The solution for this can’t be that developers of a frontend, like Discover, now reserve and use time and resources to add and maintain blocklists to clean up that mess that they didn’t created.

We should get our torches and pitchforks and put all the blame where it belongs, at Canonical!

Grub is working perfectly fine.

If it breaks it is, in my experience as a grub user for over 20 years and as a guy working in server hosting for 15 years, either because of failing HDD/SSD or because of user error. People don’t read when the updater tells them that running “grub-install” is needed (or they perform it on the wrong drive/partition) and then blame grub when it fails on the next boot.

The crappy bootloader that comes with systemd very often, in my experience, fails to register that a new Kernel was installed and boots the old one (or fails to boot if the package manager removed the old Kernel).

Oh and GRUB has so many useful features, like booting a ISO image. GRUB is a piece of programmer art!

I am not seeing how IBM and/or Microsoft are winning anything here or how systemd enables them to take over Linux. But maybe I am missing something.

Last time I checked (60 seconds ago) systemd was using FOSS licences for all it’s code. So it seems to be living the FOSS culture, or not?

I am always open to learn and correct my view on things under new information, so if you can provide them I am open to read it.

I had (and still have) way more issues with Audio on Windows then I ever had on Linux.

And I have seen it all, OSS, ALSA, aRts, EsounD, pulseaudio, pipewire and most likely some more that I have forgotten.

All it does is stuff everything into one bin

Well, it is not one bin. There is no monolithic systemd bin that does everything. There are a lot of separate bin files for all the different tasks. Well and if you don’t want to use timers, then don’t and just use cron instead. If you don’t want to use journald, then just don’t and use rsyslog or whatever you want. Don’t need systemd-homed? Well, then don’t use it. You want to configure your network with something else then systemd-networkd? Great, do it if you want.

The Poettering Army will not come and force you to enable all the options 😜

My way of thinking and working is incompatible with most premade automatism, it utterly confuses me when a system is doing something on its own without me configuring it that way.

That’s why I have issues with many of the “easy” distributions like Ubuntu. Those want to be to helpful for my taste. Don’t take me wrong, I am not against automatism or helper tools/functions, not at all. I just want to have full knowledge and full control of them.

I used Gentoo for years and it was heaven for me, the possibility to turn every knob exactly like I wanted them to be was so great, but in the end was the time spend compiling everything not worth it.

That’s why I changed to Arch Linux. The bare bone nature of the base install and the high flexibility of pacman and the AUR are ideal for me. I love that Arch by default is not easy, that it doesn’t try to anticipate what I want to do. If something happens automatically it is because I configured the system to behave that way.

Linux is so great, because there is a distribution for nearly everyone out there (unless you are blind, then things are not that great apparently, but it seems to get better).

My way of thinking and working is incompatible with most premade automatism, it utterly confuses me when a system is doing something on its own without me configuring it that way.

That’s why I have issues with many of the “easy” distributions like Ubuntu. Those want to be to helpful for my taste. Don’t take me wrong, I am not against automatism or helper tools/functions, not at all. I just want to have full knowledge and full control of them.

I used Gentoo for years and it was heaven for me, the possibility to turn every knob exactly like I wanted them to be was so great, but in the end was the time spend compiling everything not worth it.

That’s why I changed to Arch Linux. The bare bone nature of the base install and the high flexibility of pacman and the AUR are ideal for me. I love that Arch is not easy, that it doesn’t try to anticipate what I want to do. If something happens automatically it is because I configured the system do behave that way.

And you can’t let it be. Well me neither, but i will just add you to my blocklist now. That will end this dumb/pointless conversion for sure.