The 32bit libtcmalloc_minimal.so.4 that all Source 1 games ship with needs to be updated. You can symlink it to your system’s version to get TF2 running again. It’s usually only a matter of time before it starts to effect more downstream distros.
The other problem I have with TF2 is queueing for casual just stops for no discernable reason or error every time, even if I’m not the party host. But then I come back later and it works again? Only real solution I’ve found is to have my friends queue without me and then join after they’ve found a match.
See, I did all that… and then audio broke. So, I couldn’t anymore, man. I probably could’ve copied the install, kept it updated and held it for a resolution but I just don’t demand that much from my builds anymore really. I went with Mint with XFCE and haven’t had a single issue since install. I’m good. If it comes down to Ubuntu’s base, a lot more eyes will be on the problem and I’ll sort it out then.
Debian guy could have just downloaded the nonfree installer that includes some common wifi and other hardware firmwares. There are some pragmatists at Debian.
Well… Say that to my live USB I tried booting off of a machine with a very modern nVidia card. I had to create a new boot entry to disable nouveau and install nVidia proprietary graphics into a persistent partition.
I understand nVidia is shit, and doesn’t play nice with others. But my point is - it’s not always that easy. (I thought it would be! I lost many hours, and pulled out lots of hair!)
Not in the good old days. Back in 2000something I built a custom installer image with a backported kernel from testing and some firmware to get debian installed on a new laptop.
Agree but Debian is still damn manual compared to many Fedora quality of life improvements.
Meanwhile, removing snaps and replacing with flatpaks on a set up ubuntu system is crazy! All those loop mounts suddenly start showing up when snapd is gone
I love it, because you can also get best out of both worlds in relation to the comic discusses. You can personalize OS to your liking, and the entire configuration is in a file, so you can redeploy the same setup again.
I feel like I keep posting this everywhere but there’s a project called AstOS that attempts this. Also someone clued me in on this distro neutral solution. AshOS. Full disclosure I haven’t used either.
It looks like solutions like these miss the whole point of what Nix is trying to do. Nix comes with the belief: “Unix has some fundamental issues, because it was designed in specific way. If we store things differently it works really well, and we even get those cool properties for free”.
The authors of those projects instead of thinking “this looks interesting, and it is a paradigm shift but it might be worth to to try feel like Linux noob for some time and start thinking a bit differently how the file system is structured to see if this change is really worth it”
Instead it is: “I don’t need to be PhD in Computer Science (whatever that means), here is how I can force this Nix feature or two on traditional Linux, with ansible, bubble gum and some duct tape and make it immutable-ish, which fails sometimes but, hey, it has the same feature on paper.”
Well to be fair I think it’s because they aren’t trying to be NixOS. You could leverage those arguments against any distro that’s trying out an immutable flavor. Which is mostly accomplished through btrfs features.
I agree that Nix/NixOS does a lot more and it’s a genuinely impressive and paradigm shifting project but it does break with traditional Linux layouts and thinking in a way that immutability doesn’t necessarily have to do.
You could also make the same argument with the systemd and non-systemd crowd.
Either way I look forward to the future of both immutability projects and NixOS. I feel like both areas still need a bit of work but they’re both really exciting fields.
Just add rescue to kernel options (if you use GRUB, press e to edit it for the current boot) and it will boot into console from which you can do downgrade.
When I started using Arch I just set it up on a btrfs filesystem and wrote a simple btrbk hook to take a snapshot before any package updates. That made it trivial to unfuck anything that broke after an update. I can’t remember the last time I had to roll the system back but it’s nice for peace of mind.
Start by playing with subvolumes and snapshots so you can get a feel for how they work. Once you’ve got that down you can break down your root filesystem into sensible subvolume chunks (/, /home, /var/log, /var/cache etc) so that you only snapshot relevant content during each update. I wrote a btrbk config at that point, tested it a few times and then wrote a pacman hook to fire it on install, update or package remove events and went from there.
Here’s what I use to take snapshots - you’ll need to write an appropriate btrbk config file for your subvolume layout but it’s otherwise feature complete. gitlab.com/arglebargle-arch/btrbk-autosnap
Like I mentioned above, I haven’t actually needed to roll the system back in ages but I get a lot of mileage out of being able to reach back in time and grab old versions of files for comparison.
Time shift is a lot easier if you’re just starting out but it also requires a specific subvolume structure and isn’t very flexible.
Edit: pro tip: don’t make /var a separate subvolume from /, it’s way, way, way too easy to roll one or the other (/ or /var) back without the other. If you do that by accident pacman’s state becomes out of sync with the running system and everything breaks. Stick to splitting frequently rewritten data like /var/cache and /var/log off, leave /var itself in the root subvolume.
Well yeah obviously like NixOS. My reason for not using it is that they use a non standard Linux filesystem and it renders a # of packages I want to install incompatible.
My first real experience with installing/running Linux on my own machine back in the day was with Gentoo. My experience was basically the same as Arch guy there, except with the added step of compiling every single component from source. On a Celeron equipped laptop. Nobody warned me about that part.
It took fucking ages. I was stuck in textmode land with Matrix code flying up the screen for like three fucking days, before I even got to a shell prompt.
I was in an IT school around 2012. I thought I was the only one using Linux besides Windows (predominantely though). I wasn’t. He was daily-driving Gentoo where most of the students haven’t even heard of Linux the kernel before confronted with a bash shell in a course.
I’d say in 2000 only the nerdiest people, academics or professionals knew the difference between say Red Hat or Gentoo at least here in Central Europe. Windows 95 (and 98) came pre-installed on every OEM PC and the best windows to that date (2000) would come out that year and I guess everybody was hyped for XP. Saying you are compiling your kernel and software yourself with GCC would have only got you puzzled faces instead of kudos in 2000 here.
I did mine closer to 20 years ago, I’m guessing things might have changed a bit since then. That said I ran Gentoo on an IBM ThinkPad for about five years before switching to OSX.
I’ve found Garuda pretty much gets you all the perks of Arch without the drawbacks and installs just as quickly as debian if not faster. And I love ancient Linux memes as much as anybody but neither Debian or fedora is much to write home about nowadays IMHO.
Endeavour is a great alternative IMHO, but Garuda’s development is definitely more skewed towards gaming and comes with a lot preinstalled/preconfigured.
I’d say it’s even more simple. Comes with stuff like snapper and zram preconfigured and a bunch of tools to do various things. I use their KDE lite version since I do not like their theme AT ALL.
For some reason, this didn’t work on my old phone after installing PixelExperience 11 on it.
There’s a third way. Bluetooth. At least you don’t need a cable, and you’ll save power.
For that reason, I usually use Bluetooth instead of Wi-Fi, unless I need higher bandwidth (except during peak hours of network usage, when my connection speed is below 1Mbps anyway).
While RHEL and Fedora are siblings we can’t mix em’ like that. At least I haven’t ever seen a server with Fedora pre-installed, or anyone offering support on a Fedora server…
We have a piece of fancy and expensive radio equipment in the office, the control part is a Fedora server, with precompiled binaries that run that piece of hardware. Every system library has frozen version, if you upgrade the OS the whole system stops working, and you just reinstall the disk image from the archive, and by reinstall I mean use dd to overwrite the hard drive partition from a supplied DVD.
Huh, at least it’s Linux I guess? I’ve seen plenty Windows XP hanging around controlling expensive medical equipment and one time even a system were the control part was Windows 3.1. Air gapped not for security but because the server didn’t have a NIC.
Add comment