• 0 Posts
  • 83 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2024

help-circle









  • 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.






  • 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.



  • 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.