I wouldn’t consider arch minimalist. It just defaults to a netinstall with no desktop. Debian’s default net install also doesn’t have a desktop. Arch is more “vanilla” than debian, but not noticeably more minimal on first install.
I wouldn’t consider arch minimalist. It just defaults to a netinstall with no desktop. Debian’s default net install also doesn’t have a desktop. Arch is more “vanilla” than debian, but not noticeably more minimal on first install.
In Bash, Ctrl+r is super handy too.
If I figure out how to do something in the terminal, then I know I can automate it eventually.
If I figure out how to do something in a GUI I might be able to automate it.
I believe they changed some of their licensing from the fallout of their IPO. Just worth noting for the selfhosting crowd. I know terraform is being forked entirely, but I’m unfamiliar with the specifics beyond that.
Is oneko the modern-ish version? As this sounds adorable.
deleted by creator
No amount of polishing that turd will make me ignore the fundamental user unfriendliness that is nested text drop-downs.
Can you give me an example of this? From my perspective, using something like Kate, the extremely user friendly experience of discovery is vastly better than something like vi. In Kate, I appreciate the discoverability of having a list of options. I recently learned it can interact with LSP’s because of the menus. I don’t use it for that all that much, but it was cool to even know it could do that. Maybe vi is bad comparison, but off the top of my head GTK apps just have the hamburger menu, that then opens up the list of text menu options. Seems like its just hiding the option menus by nesting them in an additional layer of a button.
For the record, I haven’t used a windows computer as anything more than an appliance in over a decade, so maybe the influence is lost on me.
I don’t know if this is what you are looking for but I used :z with podman mounting and it Just Works*.
podman run -d -v /dir:/var/lib/dir:z image
From the documentation :z or :Z relabels volumes for host and container usage depending.
Its got a closer feature set to ZFS (tiered storage is going to be huge for me personally), but a much friendlier license. ZFS’s licensing drama solidly convinced me not to touch it with a ten meter pole. BTRFS isn’t bad as well, I currently use it, but tiered storage is excellent. Was the only reason I used to consider ZFS, but becachefs is getting to have my cake and eat it too.
Rebuild after every config change
This is pretty much the whole point of using nix. The system is declarative, so it rebuilds the parts that changed, because all changes are imperitive and atomic. If it didn’t rebuild your sshd config and restart the service when you changed the accepted key types, what would even be the point? Coming from a huge ansible background nix feels like ansible on steroids.
FHS incompatibility
Why does this matter? Nix manages all your system binaries and PATHs just like any other distro, so why would it matter where they are kept? Programs like type/which still work exactly the same, and nix imports your dependencies exactly as described in the build scripts when you need to compile something locally.
Its honestly refreshing to see a distro really pushing innovation like this by taking advantage of everything Unix systems are built with and doing something this cool.
Of course, those are discreet projects that can be picked out when there is a use case for them. Discreet solutions to problems is the hallmark of Unix systems isn’t it? Any distro maintainer can choose to enable these if they want, as is the admin.
Kinda unfair to call Debian stable old when it just got a new release a few months ago. Sure, in a year or two it’ll start to feel old, but if one were to use flatpaks as you suggested, then Debian stable is perfectly fine, as at that point you aren’t even using the system libs anyway.
Linux desktop updates are handled totally differently than Windows. I don’t even see them, as my distro just has a timer that checks for updates once a day, then updates the whole system in the background. If anything, this behavior is intended for non-power users.
Not just any cheese product, but “Pasteurized Prepared Cheese Product”, because they got in trouble with the FDA a couple of times by calling them “food” hilariously.
From the phoronix article it looked very competitive considering it been in official mainline for only a couple of weeks. Was surprise how well it was handling the first SQL tests.
This method is perfect for fully controlling your traffic. As another option, you can run a wireguard VPN on the vps and route traffic back through the VPN. In my experience wireguard has better performance than an ssh tunnel and allows for actual network topology with subnets rather than just raw port forwarding.
Would be interesting to see how this compares to XMPP or Matrix. Obviously the development costs something for each of those, but the hosting costs are spread out across each of those hosting an instance.
I use NixOS, but before that I was on openSuse. I have not thought about Bluetooth in at all in the last few years. Zero issues. I pair it in KDE’s default bluetooth manager and then never really touched it since. Media keys all work, I control it over WiFi from my phone with kdeconnect no problem.
I think a few months ago I had to turn my headphones off and on again when the quality got really low for a second. Reading this thread I guess I’m extremely lucky? I don’t produce music or anything like that, so I might not be taking advantage I’d some its more exotic features.
EDIT: I am using a basic USB Bluetooth dongle I bought at least 8 years ago for my desktop, and my laptop just uses the built in Bluetooth. If that’s any consolation.
Works the other way too, can do a LVM with RAID underneath. I currently use LVM raid 5 with XFS underneath. Though all the news around bcachefs has got me pretty excited to go that route and cut out the LVM middleware.
This wouldn’t be a distro though, at least not in the context of the question being asked by the OP. My point being that Arch isn’t “minimalist”, because its not really any more minimal than Debian, or Fedora. It is more vanilla than them, preferring to not modify the original sources beyond their packaging, while Debian does do a lot more changes in this regard.
Something like Tinycore, or Puppy are minimalist focusing on running in memory entirely, or Alpine is minimalist by focusing on reducing disk space. Debian, Fedora, or Arch installs, on the other hand, are basically the same in terms of size, unless you also consider them to be minimalist. At which point we are in agreement.