I have an interesting problem. I have two systems and today I used slackpkg to update both my slackware64-current systems. One system has no problems. The other system seems to have some permission issues. For example when I execute lilo as root, I get "Fatal: rename /boot/map~ /boot/map: Permission denied" When I execute sudo lilo (as root) it works fine. rm also fails with permission denied as root and works as sudo.

Sure hoping someone has seen this before. Please let me know what additional info you need from me.

Thanks in advance

All files are owned by root:root

The last update I am on is "Wed Mar 29 20:56:21 UTC 2023"

I'm not seeing any issues running lilo. Just tested it. "rm" is working fine too.

I also use slackpkg to update my systems.

If a recall there was a prompt for configuration changes "*.new" files on I believe a pam related one in a recent update. I choose (P)rompt, then (O}verwrite since I have no customization.

I'm not using lilo, but I was logged in as root (via console) to upgrade some nvidia drivers, and no problems. (I'm patched to current on current.)

I suspect its not upgrade related, so let's for the moment not let that distort the issue. I must have done something during the process however and I don't know what. Could it be something with shadow or password? What would cause this type of behavior?

* login in as root, getting permission denied on files owned by root. mv and rm is one common command issue occurs with.
* use sudo rm or sudo mv and no problems

.

After login as root, what does command 'id' tell you? (Should be uid=0).

1 members found this post helpful.

Had this once. Logged in as root, tinkered with the system settings, it told me somewhere that permissions are not OK so "click this button to correct this".

root doesn't not need explicit permissions
So, his issue is not about that

>id
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),17(audio),502(library)

>sudo id
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),17(audio),502(library)

Did some experimenting and testing with different directories etc.

I had setup an alias for rm some years ago -- alias rm='trash-put -v'
I unaliased it and it started working ok.

For some reason that was causing some issues... not sure why. Have any ideas?
I'd like to keep the trashcan function, I do everything through the command line.

.

Well, did some more testing and put the aliases back in... I'm stumped. Everything is working now like there was never a problem... Darn gremlins....