Try, buy, sell, and manage certified enterprise software for container-based environments. It doesn’t trust mere users to do anything except “run as Administrator” for certain programs.īut I rant again, forgive me. Red Hat Customer Portal - Access to 24x7 support and knowledge. In my opinion,Windows itself is faulty, from Windows 2.0 to Windows 11, I’ve seen them all. I’d like to learn more about them for Samba (there’s a Samba instruction in smb.conf that asks “inherit acls”? And I always say no because of my faulty knowledge of Windows. I don’t know much about Windows “acl”'s, except that they are supposed to be infuriating. Maybe you knew that already, I’m just learning about it. It also comes at the end of the permissions as depicted customarily in Unix/Linux. I’ve seen maps that look something like "-Ttdrwxrwxrwx, where the capital T is the one that means “store this on the swap device”. The sticky bit that means “store this on the swap device” might be the bit before the proposed “sticky bit”, but again, I’m not sure enough to try it myself. It might be 001755, where the “0” preceeding the “1” might be the "sticky bit. Setting the permissions to “0777” will either have no effect or remove the “directory bit”. I’m not quite sure how that works, but those bits are in binary, rather than octal. That can not fail to work unless the “sticky bit” has been applied to the directory, which you caneasily tell by ls’ing them directory and get something like drwdr-xr-xt (note the “t” at the end of the permissions, it means that the file can be removed by resetting the directory. For the root ownership I assume you switched to root before doing your “chown”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |