• 3 Posts
  • 31 Comments
Joined 7 months ago
cake
Cake day: February 17th, 2024

help-circle






  • I’ve been generally happy with Ubuntu. I don’t really care for snaps, but on my headless server that’s not really an issue. I suppose I could have taken the time to uninstall snapd from the server, but I haven’t cared enough to do so.

    I ran it on my desktop for quite awhile as well, but there the snap issue was much more present. I hate Firefox as a snap, and while I’m aware of the new Firefox ppa, I decided to switch to fedora since I’ve never used it and wanted to broaden my experience a bit more.

    And yes, I’m aware of Red Hat/IBM’s shitty corporate bullshit too. Maybe one of these days I’ll use Arch btw.












  • 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 command
    • chown: the utility that allows you to change ownership of files and directories
    • -R: tells chown to change ownership recursively
    • user: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.