• 0 Posts
  • 84 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle





  • The thing with Debian is that yes, it’s the most stable distro family, but stable != “just works”, especially when talking about a PC and not a server (as a PC is more likely to need additional hardware drivers). Furthermore, when the time comes that you DO want to upgrade Debian to a newer version, it’s one of the more painful distros to do so.

    I think fedora is a good compromise there. It’s unstable compared to RHEL, but it’s generally well-vetted and won’t cause a serious headache once every few years like Debian.



  • You make some pots for the neighbors, think your work is done, then suddenly it’s “Oh no Arkadios we dropped one of our urns and also we want to store extra grain for the cold season” and here I am making MORE FUCKING URNS.

    What I wouldn’t give to live in the old days before people had to learn a trade to get by!


  • The thing with Debian distros (like Ubuntu, Mint, PopOS) is that they’re extremely stable releases. This does not necessarily mean everything “just works”, but rather that they will not experience major code changes that could disrupt a working system. This means that if some apps don’t work out of the box, that state is going to be pretty much the same in any distro based on the same Debian version.

    A more “agile” distro might be less stable, but as a result could see some updates to apps that Debian is still lagging behind on. Fedora is probably the “next step” in this direction: it’s still reliable but gets updates more frequently than Debian (it’s sort of a “proving ground” for code before it gets pulled into Red Hat, which is a distro focused on long-term stability).

    As for desktop environments: I’ve always thought GNOME was the most Mac-like DE, but KDE has enough configuration options that you can kind of turn it into anything you want. Since this is on a very old laptop, you might consider LXDE, which isn’t the prettiest DE, but it’s super lightweight and might let you squeeze out a bit more performance if you’re wasting a lot of compute power just rendering the desktop.





    1. Yes, portainer will see every container you make, regardless of how it was created.

    2. No, creating a docker container doesn’t make a compose file. It’s like cooking a meal doesn’t output a recipe.

    3. You can save the compose file(s) wherever you want, you just need to run “docker compose up” from that directory. If you make the container within portainer, I believe it stores the compose files in its own volume. Not sure about that, I keep my compose file separate from portainer for most services.






  • Their first product was a BASIC interpreter for a very early Microprocessor, which they wrote without ever getting their hands on the hardware (because the Altair 8800 was basically vaporware at the time, with no software there was no demand), and Paul Alien wrote the bootloader for the program on the flight to the product demonstration.

    Frankly, that sounds like legit computer wizardry to me. Yes, they made their billions on business more than tech, but they were legit tech guys at the start.