No, the # character shows you are root in both of your examples. The tilde (~) shows your "Working directory" was changed to root's home directory (/root). See an explanation of the differences betweenwhen i use the sudo su command i get something like [root@server server]#
but if i use sudo su - i get this [root@server ~]# so the tilde thing shows i'm root user...
su
and su -
here.su -
is the only command to work properly, it's probably because of one or more of the other differences shown in the link above: the difference in environment variables, path variables, or shell settings.cd ~/
or even simply cd ~
it will take you to your own home folder (at least it does with Linux Mint). You can check your current directory with the pwd
command.# fdisk -l
(or)
$ whoami
No, I'm sorry. I'm not really following your problem and only wanted to give you clarification on the #, $, and ~ symbols because I noticed you were interpreting their meaning incorrectly.You have no idea why i'm only able to change the user:group with chown after i did the steps described above?
chown
command. And some distros behave differently than others. For example, with Linux Mint, you cannot use the su
or su -
commands by themselves... they just don't work, even if you know the root password. This is likely because the root account is "locked" by default in Linux Mint (and other distros too). Instead, with Mint, you must use sudo su
or sudo su -
to get the same results. sudo su
has always worked fine for me when I want to use a root prompt, but you seem to think that you need the "-" for your problem to work correctly, and I've never found that to be necessary.chown
issue may be affecting that application. Gparted requires the root password to be given once, not twice. Is the disk you are trying to access encrypted?chmod
are also being questioned above. I'll re-read the whole thread later to see if I can offer any other advice, but others are more likely to guide you better.Just a quick comment on this... when you become root in the terminal, that does NOT make you root anywhere else... only in that terminal, and only while that terminal is open. So you are not root when you open up Disks, and that is why it still needs a password. But not sure why it wants the password the second time.This is what i wrote down for myself:
open Terminal
get root su rights sudo su -
open Disks - gnome-disk-utility 44.0
click on the little gearicon and select |-Check file System-|
it will ask you two times for a password - type the Passwort in
go back to the Terminal
now you can change the 'user' and the 'group'. chown -R user:group /path/dir
Okay, the quote above is Post #20, the last one on the previous page, and it seems that your original problems were solved with Fedora 38. That would have been a good time to mark your thread as "Solved." You can mark your own threads as Solved by editing the Title of the first post.Another Problem i have now,
i set up another Pc as a server to store all my data. It's on Fedora 38 as well. To find the Directories was not so much of a Problem.
But as i tried to past a File into the Folder i could not.
Storage_Zero works fine but Storage_One and Storage_Two not.
drwxrwxrwx. 1 server server 8192 Sep 8 15:26 Storage_Zero
drwxr-xr-x. 2 root root 32768 Jan 1 1970 Storage_One
drwxr-xr-x. 2 root root 32768 Jan 1 1970 Storage_Two
I figured out it has something to do with the Permission. But allways i try to
chmod a+rwx Storage_One
it says
chmod: changing permissions of 'Storage_One': Operation not permitted
So how can i change a permission when i don't have the permission to change it?
Pls, i need a hint in the right direction. I think i'm at the end of the interwebs.
THX
Rash
chmod
? This has nothing to do with the Disks program, so I would suggest just using the terminal to work with chmod
or chown
. You must be root (or use sudo) to use chown
, but a regular user can use chmod
on files that they own (but no one else's).One of the staff here (@KGIII or @wizardfromoz) may slice off this problem into a separate thread if they choose, but I'll just carry on for now.
Maybe I'm just being a little gunshy... it wasn't long ago that another new user created a runaway thread of 22 pages.From what I can see, the problems are similar - ie it's a new user coming to grips with Linux.
it wasn't long ago that another new user created a runaway thread of 22 pages.![]()