permissions
I am reacquainting myself with linux after many years away and having a harder time. I was always under the impression that when you loaded a distro that the name and password you entered made you the administrator, root, superuser, or whatever other name you want to use AND that these were all considered to be the same entity and if not why not. I am on my 2nd distro because that one and this one denied me editing smb.conf.The previous distro denied me ,while i was logged as SU to edit smb.conf because i was not the 'owner' of the file, root was the owner. This distro tells me that the file is read only after invoking su -i and while letting me modify the file denies me saving because it is read only. I am up to my eyeballs with this permissions nonsense
|
Quote:
|
Quote:
Time to take a deep breath and read up on it: https://duckduckgo.com/?q=linux+file...ions+explained |
Normal distro installs do not make you root at all, but that depends on the distro. Ubuntu gives the user sudo access and others force you to create a normal user and ask whether you want to enable root.
Don't get frustrated at permissions: normally you have to do nothing with permissions to use the system, as a desktop for example. In your example, su or sudo will work after configuration. Again, this depends on the distro. |
permissions
Quote:
|
Now that you have been advised that you can use sudo or edit as the root user, as well as needing to change the r/w attributes of the file, is there anything further blocking you?
|
Quote:
Permissions and privilege separation is exactly what makes Unix/Linux safe(r), and Windows horribly insecure. I use openSUSE...separate root and 'normal' user, so I *COULD* log in as root, but I don't. Extra steps to edit system config files? Sure...safety net in case I fat-finger something? Absolutely. You seem to be determined to say how bad this is, despite having many paths to easily accomplish what you're after, so I'm not sure what the purpose of your thread is. If using Linux is too 'hard' and has these 'bugs' you don't like, there's nothing keeping you using it. |
Quote:
Quote:
If that didn’t work for you, please share the exact commands you entered and the exact results you got. |
I just want to point out that su -i doesn't work anyway:
Code:
# su -i Also, when you use vim to edit smb.conf and smb.conf has read-only permissions, you get this when trying to save the file: Code:
E45: 'readonly' option is set (add ! to override) In short, it is not quite clear to me what exactly OP is doing to edit smb.conf. |
Oschallenged did not start declaring that there was a bug at all, they stated that it's been many years and they're having a hard time.
I'd recommend against distribution swapping due to these frustrations. Once again, there usually is a way to act as root, using the sudo command, or log in as root. Some distributions try to limit this as much as possible to protect the unwary. Further, I have found that certain files are made to be read-only to protect them the same way, but this attribute can be altered so that the files can really be edited. To check the ownership, group, and file permissions: Code:
$ ls -l <filename> For system files, I'd recommend leaving those as owned by root and not changing the group. If you really need to edit system files, this is possible, and is a thing which people still do, but you should examine the situation, make a backup of the original file, perform your edits using the root user and any needed chmod commands, and then test it out. If you didn't get it correct, you still have the original file to restore. If you have problems performing this, it is helpful to stop, record what you've done, where problems did occur and identify the distribution you are using. Then people can give more specific information to aid you. |
You could always setup a virtual machine if you want to change something system-related, but aren't sure about how to do it properly.
If I want to change something or do something and I'm worried about breaking my system; I'll setup a virtual machine, then create a snapshot/backup of it before I do anything. Unless I know beforehand I can still dig myself out of whatever hole I end up in if I end up breaking something. That way I don't care if I mess something up, because it's not my "real" system at stake. So just do that if it's something you're not sure about/still learning, that has the potential to break your system if you get it wrong. Using VM's are a great way to learn without risking your "real" system. |
All times are GMT -5. The time now is 01:53 PM. |