$ ls -la
should return permissions and user/group
I’m sorry if I’ve come across as rude to you, I’m honestly not trying to or getting frustrated with you in the slightest, and I’m honestly really thankful that you’re trying so hard to help me out. Was it because I italicised some words you thought I was getting frustrated? When I italicize words I’m only emphasizing them to try and bring in some tone; I’m not getting mad or anything.
I’m not deadset on sticking with the username mandriva if I don’t have to and if it causes issues, and I wasn’t implying that I’m deadset on solving the issue without re-installing the system. I was just asking questions so I could try grasp an understanding. I understand if you don’t know the answer to everything and if the answer might be a bit too complex; I just didn’t know.
As for the username thing, I decided a while ago that I just preferred using a username that was not my real name. It was nothing super serious or anything. It was just something I decided to do, and I didn’t see any reason for it to ever cause an issue by changing it.
So I’m sorry if I came off the wrong way, I didn’t mean anything bad in any of what I said to you.
2 Likes
No, I don’t think you are frustrated. I am just trying to tell you that ALL Linux file permissions are tied to User/Group and you can’t just change them whenever you get a notion to do it. I don’t care what you make your username to be, but it has to stay the same.
Why do I use my first name as my Username? Because it never changes from the day I was born till the day I die.
Look at the properties of a file in your ~/ drive like .bashrc and tell me what the User and Group are. That is what we will have to change every file on the USB to match.
2 Likes
Maybe I was the one misreading your last message then. Now I’m just embarrassed. Sorry.
I don’t appear to have a file on my root drive called .bashrc but I can check another file if it will give the same result. Checking a random file on my root drive, in this case, a file called “arch_status”, the properties say under “Ownership:” that the user is “root” and that the group is “root”.
~/ is your home directory. It is short for what I am guessing is /home/mandriva/
$ ls -la ~/.bashrc
2 Likes
Ok, I wrongly thought ~/ meant “root”. Maybe I’m getting mixed up with ~ without the /
I can see the .bashrc file now in Home when I show hidden files. It says that User is “mandriva”, and that Group is “mandriva”
The output of the command @rugyada gave me (ls -la ~/.bashrc) is:
-rw-r--r-- 1 mandriva mandriva 234 Oct 27 06:30 /home/mandriva/.bashrc
2 Likes
Then this is the command you need to run.
I would still have preferred to do this permanently with a new install using your first name, but it is what it is.
Was the command supposed to give me access to the HDD without doing the administrator password to act as administrator? Because the terminal didn’t print anything again and it hasn’t allowed me to access the HDD without acting as administrator. Look, I know it might not do anything, but I’ll restart the PC just to see if that fixes anything.
Sorry to quip in the middle, but I would be a little bit sceptical about trying to change ownership of a raw block device recursively, i.e. /dev/sdb-anything. The correct point would be the file system which this contains, if needed.
I could be wrong, of course, my information might be old.
2 Likes
Then give him the command to run the way you think it should run. I just want to get him fixed up.
I’m going to get my morning shower.
1 Like
What it looks like to me is that we have not yet found the real reason for these problems.
I suppose the file system is mounted and accessible. What I would like to see is running ‘ls -ld’ on any problematic file or directory. I do not trust that GUI is giving us the right answer.
Yeah, as I expected, restarting the PC didn’t fix it.
I know this is weird to ask, but is that -Id as in a capital i, or a lowercase L? This is a seperate issue I haven’t resolved yet and avoided brining up because it’s not on topic with the issue of this thread, but my clipboard is playing up in my OpenMandriva install for some reason and I can’t copy things 90% of the time. So I’ve just been manually typing things out. But that command you would like to see me use; I can’t identify whether the first letter in -ld is a capital i or a lowercase L. They look identical to me.
1 Like
Lowercase l (LIMA), meaning “ls” as “list statistics of files” and switches “-ld” as “long format and just directory, instead of its contents”. The d is just for safety in case you run the command for a directory. This way you get just one line.
1 Like
OffTopic:
Wayland?
I’ve honestly only had this issue with OM, no other distro had me altering the ownership but what fixed it for me was sudo chown -R yourusername /media/yourusername/mountpoint (the folder where the contents of your drive are mounted, you can find that out by rightclicking on the drive in dolphin > Properties listed as “Mounted On:” or alternatively open kde partition manager, select device then right click on partition > Properties, the folder path will be listed as “Mount point:”)
There’s probably a cleaner solution but I have yet to know (this works for me personally since I won’t be moving away from OM anytime soon), interestingly this wasn’t an issue with a recent ROME iso in live mode
1 Like
Probably related
How to set user ID to 1000 (instead of 1001)
1 Like
Live mode has “the power” 
Okay, thanks for explaining that. I need to first cd into the folder that I want to perform the ls -ld command on, right? I can’t seem to do that, because I don’t have the right permission to cd into the HDD.