

If you are looking to pad your resume, after learning Docker, spend a tiny bit more time to learn the basics of Kubernetes (just the basics). Maybe install Minikube. Then you can add that to your resume as well.
If you are looking to pad your resume, after learning Docker, spend a tiny bit more time to learn the basics of Kubernetes (just the basics). Maybe install Minikube. Then you can add that to your resume as well.
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.
The kernel part of the NVIDIA driver is Open Source now.
The NVIDIA problems are almost entirely legacy at this point. Unless you are using something that ships ancient packages (looking at you Debian Stable), you should be fine.
Interesting to see the Clang attributes on there
Interesting to see the Clang attributes on there
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.
Glad you are enjoying Arch. I agree, it is no longer hard to install.
Do you have an example of something in the Arch wiki that does not apply to EOS?
I mean, I guess most people self-installing Arch are not choosing Dracut (though you could and the Arch wiki covers it). I cannot really think of anything else though.
I use KDE with Chimera Linux which is only in beta. Rock solid.
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.
I agree with you. But there is Distrobox if you want to “bring your distro”
People recommend Mint mostly as a better Ubuntu I think. Ubuntu is still the most popular and, increasingly, not the best distro to start with.
Fedora currently fills the space that Ubuntu used to fill. Probably the biggest caveat with Fedora now is the lack of codecs by default.
Arch benefits not just from documentation but from its repo. Whatever you get told you need, it is always a relief to find it waiting there for you already tuned for your distro.
My current distro uses APK 3 as a package manager and that is already atomic. So I guess my current setup works fine, without any of the other hassles and limitations.
ffmpeg will do CPU detection and use features like AVX2 if available even on vanilla distros.
Amazing! Thank you for diagnosing this issue for the rest of us.
This is exactly why Open Source works and why even huge companies cannot keep up with Open Source software once it has taken hold. The users drive it forward in a way that money alone cannot match.