At the terminal, go to the directory that contains the mount point for the disk (so if the mount point is /mnt/disk
go to /mnt
.
Run ls -l
. This should list everything in /mnt
with the owners and permissions. If your mount point (in this example disk
) is owned by user and group root
, then you just need to change ownership of the mount point and the disk attached.
With the disk attached, run sudo chown -R user:user disk
Replace each instance ofuser
with your system username (if you’re not sure what you’re username is run whoami
and it will tell you), and replace disk
with your mount point directory.
Here’s what this does:
sudo
: escalates your privileges to run the chown
commandchown
: the utility that allows you to change ownership of files and directories-R
: tells chown
to change ownership recursivelyuser:user
specifies the user and group that will own the files/directories you are modifying.disk
: specifies the file(s)/directories you want to change ownership for.You do need to be careful, but you can check for errors after editing /etc/fstab
by running the command sudo mount -a
. With the drive attached but not mounted. (Also good practice to use the UUID of the drive in the fstab entry)
That command runs through etc/fstab
and attempts to mount everything it is instructed to mount if it is not already mounted. And if there is an error it will let you know.
If you run sudo mount -a
and you get no output in the terminal, then there are no errors, your drive should now be mounted, and you should be fine for reboots and it should mount on startup as expected.
deleted by creator
Instead of using the gui for this, have you tried. creating a mount point and adding an entry to /etc/fstab
?
Edit: fixed stupid autocorrect
Can someone eli5 what real time kernel is?
Edit: nvm. Found a good explainer.
If you’re just doing a vanilla Linux install, ext4 is the way to go.
This is great. Thank you for sharing!! I was just thinking about how I wanted this and knew it had to exist in the settings but hadn’t gotten around to looking up how to accomplish it.
Currently running Navidrome on my server and using substreamer on mobile, with the webui on desktop.
If you’re gonna dive into sed and awk, I’d also highly recommend learning at least the basics of regular expressions. The book Mastering Regular Expressions has been tremendously helpful for me.
Edit: a letter. Stupid autocorrect.
MOAR SOCKS
I’m really happy to be hosting my own password manager.
Regarding baserow, I use it in a couple of ways. First is as a replacement for Google Sheets. For my use case, I only ever really used sheets as a dumb database, (home inventory, etc…) so I don’t need the spreadsheet parts of the spreadsheet much.
The other thing I use it for is a backend for my automations for data. Baserow has wonderful api documentation right in the gui, and I use that a lot with data logging for myself.
This is entirely anecdotally just my experience. I’m using musicbrainz Picard for my id/tagging and so far I haven’t had any issues.
I’ve got my music in Jellyfin as well, and I can always use that as a fallback if Navidrome does end up fucking me.
edit: added Forgejo
It’s not exactly desktop, but I use Voyager. It’s a web app. You can also self host it if you don’t want to use the developer instance (I’ve got mine running in docker for desktop use. I use the Voyager app for iOS)
If only. It’d be a real April fool’s if Canonical announced they were abandoning snap and throwing their supory behind flatpak.
I don’t understand the actual mechanics of it, but my understanding is that it’s essentially like what happened with Volkswagon and their diesel emissions testing scheme where it had a way to know it was being emissions tested and so it adapted to that.
The malicious actor had a mechanism that exempted the malicious code when built from source, presumably because it would be more likely to be noticed when building/examining the source.
Edit: a bit of grammar. Also, this is my best understanding based on what I’ve read and videos I’ve watched, but a lot of it is over my head.
Great read. Thank you for sharing.
Awesome! Glad I could help.