• 0 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: June 28th, 2023

help-circle


  • The Samba service is normally run by root either way. Samba uses the logged in user’s uid to access the files. To be able to see the files, the user needs to have permissions for the directory and the contained files. The mnt folder currently only has root permissions, which is why the user can’t see the files.

    You need to change the permissions of the NTFS mount. I’m not sure what the uid of user is, but you can find that out by executing id user. The numbers are the ids you need. In fstab, you need to add the user’s uid and gid by adding uid={},gid={} to the line.

    Assuming the uid and gid are 1000, it would look like this: /dev/disk/by-uuid/2666EE3966EE097F /mnt/2666EE3966EE097F auto nosuid,nodev,nofail,uid=1000,gid=1000,x-gvfs-show 0 0 (you need to remount the partition after the change). You can check if the permissions changed in your file manager.

    This will change the mount’s permissions to the user you want to access it from, but this also means that no other user (except root) will be able to. The link below has the answer if you want it to be accessible by all users.

    I used this answer on Superuser, so it’s possible that this will not fully work, but I don’t have the devices to test it out currently.







  • I started with Pop!_OS, because it was pretty and I was told that it was made for programmers. I was overwhelmed with the options and couldn’t get Twitch to work properly (because of missing codecs), so I switched over to ZorinOS, which helped me to familiarize myself with Linux. Later I returned to Pop!_OS.

    Someday I got fed up with the major version updates, so I switched to Manjaro and later to Arch btw.






  • You don’t install the apps “sandboxed”. You can install the Google services like any normal app (in the “Apps” app). The Google services will then only have very limited permissions, for example they won’t be able to see your location, camera, contacts etc. by default and you can grant these permissions like to any other app.

    The only thing that changes is that you have the option to install Google services and that you have the option to grant them permissions they would have limitlessly on a “normal” Android phone.

    Your four mentioned apps should work on GrapheneOS without any problems, the only apps I had difficulties with were banking apps. The Google Play Store won’t be installed by default though, so you will need to install it in the “Apps” app. (I recommend using F-Droid to find alernative apps, although you won’t find something like Clash Royale on there. If you don’t want to use a Google account, you may want to look into Aurora Store (it provides anonymous access to the Play Store), which is also available of F-Droid)

    I personally still use Firefox (Mull to be exact), because Vanadium doesn’t seem to have any good way of blocking ads. I found this on the internet in some R*ddit comment:

    Chromium-based browsers like Vanadium and Bromite provide the strongest sandbox implementation, leagues ahead of the alternatives. It is much harder to escape from the sandbox and it provides much more than acting as a barrier to compromising the rest of the OS.

    (Long version of the above quote: https://grapheneos.org/usage#web-browsing)