Spyke

Replies

Comment on

Looking for help finding save folder

Here is how you can find it.

  • First, in Steam, go to Settings -> Storage. There you can see the path for your library.
  • Click ... icon and select Browse Folder
  • Open compactdata folder
  • Open folder 3119540 (3119540 is Steam ID number for Scriptorium)
  • Open folder pfx
  • Open folder drive_c - this is emulated C drive of the game
  • Most probably pictures are in users/steamuser folder somewhere
linux

Comment on

*Permanently Deleted*

I had laptop running Ubuntu 16.04, which was running for 2273 days without reboots or anything. It was located in safe place so not even security updates were installed during that time. And it was still completely fine after all these days (little bit over 6 years). It was finally shut down when there was electricity break, and its battery failed, and I decided that it was time to retire it.

There of course were tons of updates available then, but no one forces you to install them. and in Debian system instead of Ubuntu, there will be lot less, their release policy is much stricter.

linux

Comment on

Question about Linux culture.

First of all, in Linux everyone should only use software from distribution repositories (eg. via apt command in Debian, Ubuntu, Mint, dnf/yum command in Fedora etc...). Package managers will install software in controlled way and it is really easy to remove them too. And, there is usually gui app for installing apps from distribution repositories.

Second way is to use flatpak / snap. They are pretty much similar and will keep things easy.

Do not install sh packages or tar.gz if you really do not know what you are doing. These are only for expert cases.

One fundamental change coming from Windows is that in Linux, you should never worry about location where software is installed (except for those expert cases, which you should not use). They will be put in correct places always. In Linux, apps are sorted so that executables go to /usr/bin, library files to /usr/lib64 and /usr/lib, applicatoin other non-modifiable stuff to /usr/share etc. It gets quite a lot to get used to, but in long term it feels more natural than Windows way to dump everything in app directory.

My recommendation will be to install some user friendly distribution (Ubuntu, Fedora, Mint) and just go ahead with default package management things what it offers. If you see Android way handling software good, Fedora Silverblue is kind of like that - System upgrades are handled same way, and applications are installed as flatpaks.

linux

Comment on

App Lock under Linux?

Creating a different user account for it is out of the question btw, since you can still change the password for that user via the primary admin account.

First of all, if users have admin rights, nothing really prevents them to run that app. Even if you encrypt the app itself, they can just reinstall/replace it from standard repository.

Few ways this can be done:

  1. If app needs internet connection, you may use firewall rules to block said connections, or even application firewall (Opensnitch). Create script which unloads said rules via su (create diffrent accounts with passwords the user must know) then runs app, and after closing app loads rules again. Users must not have admin rights or they can just unload fw rules.

  2. Create encrypted container/directory, protected by password, and manually install said app under there (probably needs manual recompile of the app). Create script which asks password, unlocks the encrypted location, runs app, and locks container after use. Again, no admin rights for users or they just install same app from repositories.

  3. Use apparmor or selinux to block said app. And again create script which by using su (create diffrent accounts with passwords the user must know) allows app via selinux/apparmor policies and runs app, and blocks it again afterwards. I repeat, users must not have admin rights or they can just unload those blocks.

What app it is?

EDIT: Clarification for su usage

To have user asked password before app can be done via su + sudo like this

  • create user demouser
  • give password of that user to end user
  • give demouser sudo rights to run particular command as root without password (to unload fw rules, unload apparmor/selinux policy etc).

Comment on

I see the Reddit hivemind has arrived

Reply in thread

Have you ever upgraded the Ubuntu laptop? Cause that’s my main gripe with Ubuntu. Server upgrades work, desktop upgrades never did for me.

I wonder about this. I have been running Ubuntu on one of my laptops for years, and updated it several times withouth hitch. All the way from around 18.10 to 22.04 (non-lts, so I upgraded to every release) until the laptop was replaced.

Usually the breakage happens if one has tons of shitty third-party repos and thus will get package conflicts when upgrading. And those are solved by removing/replacing all software installed from those repos and then after upgrade reinstalling them again if needed.