Just some Internet guy

He/him/them 🏳️‍🌈

  • 1 Post
  • 267 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle
  • The main issue you’ll run into is nicher proprietary software being hard to install, but that’s what containers are for. The main one I see is if you need to install some proprietary VPN client it gets annoying, but since you’ll be running a VM anyway you can do some network trickery. My work’s antivirus only works on Ubuntu and RHEL, proprietary kernel modules so it’s got to be at least one of those kernels.

    Linux is Linux, nothing’s impossible to solve even with Bazzite’s immutability. Worst comes to worst you make your own images and it’s not that hard, you basically just fork it on GitHub and let the CI do its thing.

    But do you have time to fiddle to make it work and take the risk, or do you want to play it safe? How confident are you with Bazzite’s more advanced topics?




  • The guy gives a ton of “I don’t care about anyone’s use cases except mines” vibes too. Also called Gnome and KDE teletubbies DEs when I mentioned xcomposite being an important feature. Basically considering the widely known issues around multimonitor vsync and mismatched resolutions and all as basically not real issues with Xorg.

    XLibre is 100% a political fork because the guy claims Xorg is deprecated by a big tech conspiracy pushing inferior software onto users. There’s nothing wrong with wanting to continue Xorg’s legacy but come on we don’t have to pretend Xorg is this perfect thing that always works. Xorg has been hated for decades for a reason. This xkcd exists for a reason: https://xkcd.com/963/




  • It depends on your overall energy use but generally that would be negligible when compared to heating and hot water, especially during winter when the furnace runs 24/7.

    In particular, during the winter, all excess energy from the oven is heat the furnace doesn’t have to provide so it’s basically free: you’d use that energy anyway.

    Generally the economy of scale should technically favor the prebaked bread, at least before the store slaps its value added surcharge for it. The store still needs to pay for the energy (but probably gets it cheaper than you), but also needs to pay to maintain a factory, equipment, employees. So you kinda need to factor in the price of your oven too and its wear and tear.

    I just buy the loaf because one thing I know for sure is if I factor in the value of my time, it’s way better and easier to work an hour than spend an hour baking a loaf of bread. The time to bake the bread costs more than if I used that time to work the equivalent time and buy 5 loaves of bread with the money.



  • If you don’t want to be monogamous, don’t, just be polyamorous and date other polyamorous people. It’s a really bad excuse for cheating when there’s plenty of relationship arrangements where this isn’t a problem. There’s no need to deceive unwilling people and cheat on them when you can find partners who think the same as you and you don’t need to cheat on in the first place. You’re still dealing with other people with feelings on the end.

    I’d have to really go out of my way to cheat on my wife when the only rule is to have safe sex (or be safe in general).










  • Max-P@lemmy.max-p.metoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    3 months ago

    In that specific context I was still thinking about how you need to run mysql_upgrade after an update, not the regular post upgrade scripts. And Arch does keep those relatively simple. As I said, Arch won’t restart your database for you, and also won’t run mysql_upgrade because it also doesn’t preconfigure a user for itself to do that. And it also doesn’t initialize /var/lib/mysql for you either upon installation. Arch only does maintenance tasks like rebuild your font cache, create system users, reload systemd. And if those scripts fail, it just moves on, it’s your job to read the log and fix it. It doesn’t fail the package installation, it just tells you to go figure it out yourself.

    Debian distros will bounce your database and run the upgrade script for you, and if you use unattended upgrades it’ll even randomly bounce in the middle of the night because it pull a critical security update that probably don’t apply to you anyway. It’ll bail out mid dist-upgrade and leave you completely fucked, because it couldn’t restart a fucking database. It’s infuriating, I’ve even managed to get apt to be incapable of deleting a package (or reinstalling it)/because it wanted to run a pre-remove script that I had corrupted in a crash. Apt completely hosed, dpkg completely hosed, it was a pain in the ass.

    With the Arch philosophy I still need to fix my database, but at least the rest of my system gets updated perfectly and I can still use pacman to install the tools I need to fix the damn database. I have all those issues with Debian because apt tries to do way too fucking much for its own good.

    The Arch philosophy works. I can have that automated, if I asked for it and set up a hook for it.


  • Max-P@lemmy.max-p.metoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    3 months ago

    Pacman just does a lot less work than apt, which keeps things simpler and more straightforward.

    Pacman is as close as it gets to just untar’ing the package to your system. It does have some install scripts but they do the bare minimum needed.

    Comparatively, Debian does a whole lot more under the hood. It’s got a whole configuration management thing that generates config files and stuff, which is all stuff that can go wrong especially if you overwrote it. Debian just assumes apt can log into your MySQL database for example, to update your tables after updating MySQL. If any of it goes wrong, the package is considered to have failed to install and you get stuck in a weird dependency hell. Pacman does nothing and assumes nothing, its only job is to put the files in the right place. If you want it to start, you start it. If you want to run post-upgrade, you got to do it yourself.

    Thus you can yank an Arch system 5 years into the future and if your configs are still valid or default, it just works. It’s technically doable with apt too but just so much more fragile. My Debian updates always fail because NGINX isn’t happy, Apache isn’t happy, MySQL isn’t happy, and that just results in apt getting real unhappy and stuck. And AFAIK there’s no easy way to gaslight it into thinking the package installed fine either.