• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Or Windows gives you a blue screen and just “BAD_POOL_HEADER”.

    I got that intermittently at work on an instrument about every week or two. The best answer I could find was “it could be software or hardware related”. Yeah, thanks for that, problem solved. Wish I had thought of that. Not even a time stamp. Finally found out when it occurred to within 20 minutes and there was jack shit in the logs.

    IT ended up calling in a service tech to re-image the computer.




  • Drivers are on the computer, firmware is in the component. Firmware can be updated in both windows and Linux and will affect both systems. Drivers live solely on the OS, so fedora drivers will not be affecting windows. There’s an incredibly small chance that your firmware was updated and caused this, but I don’t recall a firmware update ever occurring automatically on Linux, I’ve always had to do it manually.



  • EDIT: Wow! thanks for all the detailed and super quick replies! I’ve been reading all the comments here and am concluding that (even though I am currently running only one service) it might be interesting to start using Docker to run all (future) services seperately on the server!

    This is pretty much what I’ve started doing. Containers have the wonderful benefit that if you don’t like it, you just delete it. If you install on bare metal (at least in Linux) you can end up with a lot of extra packages getting installed and configured that could affect your system in the future. With containers, all those specific extras are bundled together and removed at the same time without having any effect on your base system, so you’re always at your clean OS install.

    I will also add an irritation with docker containers as well, if you create something in a container that isn’t kept in a shared volume, it gets destroyed when starting the container again. The container you use keeps the maintainers setup, for instance I do occasional encoding of videos in a handbrake container, I can’t save any profiles I make within that container because it will get wiped next time I restart the container since it’s part of the container, not on any shared volume.







  • I don’t keep a Swiss army knife set of distros anymore. I put tumbleweed on a USB. It’s rolling so I update it when I plug it in, then do what I need to do.

    I used to have a USB with Ubuntu LTS and whatever the newest Ubuntu was. Then another would get something else that I needed/wanted. I always ended up wiping the drive and adding the newest release every single time. I was always out of date by the time I needed one of them for boot repair or something. This was also a time when persistence… Wasn’t very persistent. With tumbleweed I can install whatever I need and it’s there next time. I’m sure you can do the same with any other rolling release, but tumbleweed is in my opinion on par stability-wise with incremental distros. It’s my first grab whenever I need to check a PC. If I need another distro or boot USB, I can make it from this one with a second USB. I suppose the only thing I can’t do is make a bootable USB if the computer I’m on can’t access the Internet



  • I used both tumbleweed and leap for a bit and they really are good. I’m actually using tumbleweed on a home server right now and it’s been a champ. But…

    1. My biggest gripe is opensuse seems to use different package names than any of the other distros for basic packages. I had to install a package that used capitals in the package name, and coming from mostly debian based distros, that made me rationally angry when trying to find the package I needed. I think it was network-manager or something that’s usually installed by default and I wanted something familiar.

    2. Online directions for setting something up usually has deb and/or fedora rpm directions, which is usually just some difference in package names and the equivalent install command, searching the base package will let you figure it out. I had very few issues following debian/Ubuntu directions and translating them for fedora. Opensuse is always non-existent so you always need to translate those directions for opensuse, which is usually like doing it for fedora until you run into point (1).