[–] 1 point 11 months ago

It is not about how well it works. They can certainly disagree about that.

The problem was that they clearly have no idea how it works and “warned” people about a bunch of things that will not happen.

If posted a comment about Linux and told you not to use it because it would cause your hardware to disintegrate, the issue is not my level of Linux advocacy. The problem would be that I am peddling actual falsehoods.

  • source
  • parent
  • context
  • [–] 4 points 11 months ago* (2 children)

    First, I use either Niri or KDE Plasma on Chimera Linux. Both are just an “apk add” away. You do not have to use GNOME. There is even a KDE live image so you do not even have to run GNOME once to install if you do not want.

    I really like the BSD utils and have come to prefer them. Well written. Sleek. Well documented. The man pages are a walk through UNIX history. They feel “right” to me.

    That said, the BSD userland is frequently a pain when interacting with the rest of the Linux universe. You cannot even build a stock kernel.org kernel without running into compatibility problems. The first time I built the COSMIC desktop on Chimera, I had to edit a dozen files to make them “BSD” compatible.

    Sed, find, tar, xargs, and grep have all caused me problems. And you need bash obviously. But bash is no big deal because it has a different name.

    The key GNU utils are available in the Chimera repos. But you get files named gfind, gtar, gxargs, gsed, etc. so scripts will not find them.

    You often have to either add the ‘g’ to the beginning of utilities in scripts or edit the arguments to work with the BSD versions.

    I mean, most things are compatible and I bet most of the command-line switches you actually use will work with the BSD utils. But I would be lying if I did not say third-party scripts are a hassle.

    If I could do Chimera all over again, I would make it bsdtar and bsdsed (or bsed maybe) for the BSD versions.

    Maybe the regular names could be symlinks with sed pointing to bsdsed by default but you could point it to gsed instead of you want. The system Chimera scripts and tools could use the longer names (eg. bsdsed) instead of the symlinks. The GNU tools could be absent by default like they are now. That would be the best of both worlds. The base system would have the advantages of the BSD tools (like easier builds as outlined on the Chimera site), the system could be GNU free if you want, and you could have a system that actually works out of the box more often with third-party scripts.

    It pains me to say this. I would prefer not to use the GNU stuff but the GNU tools are the de facto standard on Linux and many, many things assume them. No wonder UUtils aims for 100% compatibility.

    Anyway, even with what I say above, Chimera is my favourite distro. The dev can be a little prickly, but they do nice work.

  • source
  • parent
  • context
  • [–] 3 points 11 months ago (1 child)

    Chimera Linux is great. APK and cports are so good I cannot imagine going back to anything else.

    Bash is not the default shell though. Chimera uses the Almquist Shell from FreeBSD. Other Linux distros have “dash” which is basically an Almquist variant.

    Almquist is lighter than fish and fish is not POSIX compatible.

    Bash is available in the Chimera Linux repos of course and is required for many common scripts.

    “Not run by fascists”. Sometimes I wonder.

  • source
  • parent
  • context
  • [–] 9 points 11 months ago* (last edited 11 months ago)

    This is a dramatically misinformed comment. You have clearly never used Distrobox.

    1. The first bullet is the worst. This is like saying that Flatpak will break your host. It will not break the host OS. Learn what a container is.

    2. It is not tools on top of tools. It is tools in a container that you can optionally create entries for in your app menu. Apps in the container execute directly on the host kernel in the container. If you are in a shell, you are either in the container or out and the full environment will reflect that.

    3. It is not for “new users”. That said it dramatically simplifies many intermediate ones and make some advanced things possible. Once again though, there are no “stacks on stacks”.

    4. The exact opposite. Containers do not change the host. If something goes wrong in the container, you can purge it completely without impacting the host.

    In fact, one of my core uses for Distrobox is to keep my host system clean. I use Distrobox to setup dev environments, to try out new software, to work around Distro constraints, and a host of other tasks. It is great.

    There seems to be quite a fundamental misunderstanding of what a container is. Everything runs directly on the host kernel. Apps outside the container run on the host OS and do not interact with the container. Apps in the container run in the environment inside the container. The only interaction apps in the container have with the host is the kernel, the filesystem, and via servers like Wayland, Pipewire, and XDG portals.

    The entire point of a container is to create an application environment that looks exactly like an application expects regardless of system it is running on. It is clean and consistent between deployment. This is the exact opposite of what the above comment implies.

    In practice, it “feels” like apps in Distrobox are running native on the host OS but in fact everything above the kernel is running inside the container and each container is distinct from the others.

    The “example” is totally wrong. GCC is either on the host or it is not (from the host). GCC is either in the container or it is not. They do not interfere with each other. They do not even share C libraries. However, the can see the same source files.

    Distrobox is absolutely nothing like Homebrew. Homebrew is a package manager. If you are using a package manager in Distrobox, it will be the one intended to work with whatever distro you are running in Distrobox. This is a fantastic illustration of the confusion of ideas at work here.

    If you have to compare Dostrobox to something, compare it to Flatpak.

  • source
  • parent
  • context
  • [–] 4 points 11 months ago (2 children)

    The most of countries likely to invade Canada is as follows:

    • the USA

    Nobody else could manage a land assault on North America. Coming in from the arctic would be almost impossible.

    Invading from the west or south means the US is in the way. And the US is unlikely to tolerate an invasion to the continent anyway (unless they are involved). And where is an invasion from the east being staged? Europe?

  • source
  • parent
  • context
  • [–] 4 points 11 months ago*

    In practice, Finland and Poland are the greatest protection against Russia as they are very much in the way and would trigger all of NATO.

    Many European counties have very credible defence industries. From what we have seen in Ukraine, NATO (even without the US) has both a technological and tactics advantage against Russia.

    We are also seeing that warfare has changed. He who makes the most drones and cruise missiles wins.

    And Europe could massively outspend Russia, again without help from the US.

    Germany has massively stepped up their military spending. If they had to, Norway to completely fund a NATO war against Russia on their own.

    The only thing the US really brings to NATO these days is their nuclear arsenal. But again, Russia has shown that their “superiority” in this area is useless in practice. It will not help them in a war with Europe.

    The only way that Europe loses against Russia is if the US teams up with them. This used to be an insanely unlikely outcome but….

  • source
  • parent
  • context
  • [–] -1 points 11 months ago (3 children)

    I used to think the problems with Manjaro stemmed from Arch. The I tied EndeavourOS and I thought that EOS was fixing the Arch problems.

    Then I tried Arch and realized that all the problems are the result of Manjaro. Arch does not have them. None of the other derivatives have them either.

  • source
  • parent
  • context
  • view more: ‹ prev next ›