• 2 Posts
  • 29 Comments
Joined 9 months ago
cake
Cake day: February 17th, 2024

help-circle

  • I’m no expert so take this with an appropriately sized grain of salt.

    You should be able to install KDE on whatever distribution you decide. If you want KDE 6, you may have to add a repo, but it should be as simple as sudo <package manager install incantation> whatever-KDE-is-named-in-the-repo

    If you want stability, Debian is the go to, but the tradeoff there is older packages. However if manjaro is working for you, don’t fix what isn’t broken. I don’t know how good Debian is for gaming, but honestly any distribution should be just fine for dev. Considering what steam has done with Arch as the base, it may be worth considering Arch as an option.

    To the partitions, I’m not knowledgeable enough to make recommendations as to what you should or shouldn’t touch. My instinct is to not touch /boot/efi

    Something can definitely go wrong when playing with partitions, so make that backup of everything as planned and test it before you make any changes to the system.









  • 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.