Super!

youruser:youruser just means the user’s group. For instance, on my fedora 40 install, my user (bippy, just a silly name), is the username for my user, but also the name of the group that my user belongs to.

So when I do a chown, I typically do chown -R bippy:bippy path/to/directory

If you wanted to give permissions to a different group on your system, but also to your main user, you could do a chown -R bippy:wheel /path/to/directory (wheel is an example group name, which is similar to sudoers)

It’s not that Linux can’t do what you specify, but that it may not do it in the way you require, which is based on your windows experience. Lots of what you describe can be done

For example, using command line tools like sed, rename, ffmpeg, find, etc…, you can do all of the text manipulation you can imagine.

But you also specify that you want gui wrappers, and in all likelihood, there are gui wrappers for what you want to do, but to meet your exact specifications, maybe not.

If you’re willing to do some adapting, which it sounds like you are, the. I think you can pretty easily adapt to Linux, as it’s perfectly capable of handling your high level requirements. It’s in the minutiae of how those requirements are met that is in question.

Awesome!

You could write yourself a bash script to do this.

If it’s a MacBook that no longer gets updates from Apple then it’s probably from around 2014ish, and is definitely an Intel Mac. This is a great candidate for Linux. If you want an environment that is similar to Mac, go with gnome as the desktop environment. Outside of that, any of the major distributions should be fine. I’ve run KDE Neon, Ubuntu, and am currently running fedora on a 2014 iMac and all of them worked without issue.

Man I miss basic.

Depending on the file it’s either dot notation or flat case.

Awww. The poor pkcell!

Ubuntu LTS. Currently on 22.04.

I will! I’m happy with fedora so far, and right now I’ve been focusing on really learning bash and bash scripting. I’ve always been comfortable using the command line, but never really learned it beyond the most basic stuff, I’ve written a number of scripts now as part of this process and it’s been really fun and useful.

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.

Ah. I didn’t catch that it was the 3.10 kernel. But, as you say, still dated. I thought it was a bad idea, especially in new hardware.

For me, it was A Quiet Place. I found it incredibly dumb and impossible to believe that nobody on the whole of the planet ever considered that these aliens with ultra incredible hearing weren’t somehow vulnerable to noise? Just dumb as fuck, especially when you consider that sonic weapons already exist and are used, and sound is routinely used in torture/incarceration scenarios.

Awesome! Glad I could help.

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.

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

Watching sports/sports fandom. I just dont give a fuck about sportsball in any way shape or form.