• 0 Posts
  • 1.04K Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle


  • This may be what you are trying to say but Docker makes reproducibility between environments far easier.

    If it works in Docker on your machine, it will likely work in Docker equally well elsewhere. Or perhaps more important for you, if it worked for the dev, it will probably work for you too. Except for the network, the app always runs in the same environment (no matter where you deploy it).

    Docker is kind of like shipping the software already installed on a laptop (just without the hardware). By that I mean that it is the software, already installed and configured, including all the libraries and utilities that it depends on.







  • Started with Soft Landing Systems (SLS). Pre-Slackware. Many hours downloading floppy disk images at school.

    Moved to Red Hat (pre-Fedora and pre-RHEL) until I think 7.3 or so and then Mandrake. I did trial runs with many distros over time but none of them really stuck. Fedora for a release or two. Spent a few years on Manjaro for desktop and CentOS for server. Have been on Arch for many years now (or EndeavourOS). Never used Ubuntu really.

    Moved to Proxmox for server. Although I never used Debian historically, quite a few of the containers I have on Proxmox now are Debian based as is Proxmox itself.

    Lately, I have been using Chimera Linux for desktop though I have an Arch Distrobox on it so I guess I am a bit of a hybrid at this point.




  • Arch users do not consider EOS as Arch but it absolutely is.

    EndeavourOS uses the vanilla Arch kernels, the vanilla Arch repos, and the AUR. There are only a handful of packages in the EOS repos and the majority of them are theming or utils that are what you would use on Arch as well (like yay and paru). There are a few quality of life utils that are totally optional and most EOS users are probably not even aware of. Plus, I suppose, the EOS keyring and a couple of packages so that the distro identifies as EOS instead of Arch. Distro identification is the only thing that “overrrides” anything in the Arch repos.

    I describe EOS as an opinionated Arch installer with sensible defaults. Once installed, it is just Arch.

    It is trivial to revert EOS to vanilla Arch if you want to. I don’t think it even requires a reboot.


  • I have never had anything in Arch take months to fix. One tip I would have is to use both the latest kernel and an LTS. If something “breaks” with a kernel module, just boot into LTS and it is probably fine there. I also had an issue with WiFi for about a week but a quick reboot into LTS and I was good to go immediately. When I tried the latest kernel two weeks later, it had been fixed there. Something similar happened with my FaceTimeHD camera. Same solution.


  • Just recently repartitioned my MacBook:

    1 GB for EFI (vfat)

    2 GB for /boot (ext4)

    11 GB for swap

    224 GB for / (bcachefs)

    Grub cannot load a kernel off bcachefs so I need ext4 to bridge the gap. Once the kernel is loaded, it has no problem using bcachefs as root.

    This is a laptop. On a desktop that can handle more drives, I would split /home onto a drive of its own.