• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 22nd, 2023

help-circle






  • jasondj@ttrpg.networktoLinux@lemmy.mlThe future of Linux
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I’m a big fan of retired systems for every day use. A 14 year old server has more function as a space heater and whitenoise generator than a desktop, though.

    7th-8th gen Intel retired corporate desktops and laptops from Dell/Lenovo/HP are a dime a dozen on eBay man. Lenovos tend to run Linux very well out of the box. And Linus himself sent his daughter to college with a Dell XPS.







  • I never use them but I can see the point. Like when you’re poking around for a log file, not sure what it’s called or where it’s stored and just going on a hunch…but you’re in an SSH session and don’t want to deal with X shenanigans.

    It’s a legit PITA to ls, look for files, cat/tail them, etc. sometimes you just want to ls -alR but your corporate build runs tmux on SSH sessions with no configuration so you can’t scroll back since your shortcuts don’t work so you have to pipe everything to more and it just sucks.





  • Actual reason is system permissions.

    Most the default installation path is Program Files. That needs elevation to write to. Fine when you’re installing something, but not something you want to need just to run the game.

    Writing to %APPDATA% or really anywhere in %USERHOME% is guaranteed to have the right permissions for this user.

    Granted, a lot of home PCs and gaming PCs are single-user environments. The “personal” computer. In that case there’s no reason games and applications can’t be installed in %LOCALAPPADATA%, and in fact, I think windows has an environment variable or registry setting for that.

    It’s no different in Linux. You don’t want users writing to /etc. And you may expect multiple users. So all of that stuff goes to dot files in $HOME.