Re: mcedit

Alexander,

> >$ sudo -s
> >Password:
> ># whoami
> >root
> ># echo $HOME
> >/Users/armin
>
> Then the cause of your problems are clear: Some of mc's config
> file(s) can only be properly read when you are root.
> That means these config files have the wrong owner or the wrong permissions.
> Solution: use "chown" and "chmod" as root to properly own your config files.
> (chown -R armin folder_with_config_files and chmod -R 777
> folder_with_config_files)


To clarify it a little bit more, if root owns files in /Users/Admin, depending on the permissions, then back in the Admin account, a new mc instance possibly cannot read or alter them anymore. It might even happen by just saving configs as root into /Users/Admin although normally user and permissions would not change when the file was already there first. But an app could save configs with full authority attributes, as security measure. We just don't know what system call mc on Mac is doing.

But to my understanding, the problem occured when mc was running as 'root' ? But root should be able to read and change any file, of any user. Wasn't that the whole point for Ben to start mc as root, in the first instance ?

Now all that's probably why you suggest give (back?) ownership of all files to the admin user and additionally chmod 777 which means, everyone can read and modify.  (In that case, it does not matter anymore who owns that file right ?)
Well if there are no security concerns (and there shouldn't really on a single user machine) then it's anyway not wrong to do this. But it might not solve the problem, and if it does, it could be necessary to repeat it every time you shutdown the root mc. (Maybe make mc an alias with a fucntion doing all that).

But i repeat, we would really need the error message text to understand what actually happened.

-- 
mc mailing list
[email protected]
https://lists.midnight-commander.org/mailman/listinfo/mc