Umask and Special File Permissions - Linux Tutorial 23

[@codebreakthrough]

Full Playlist - kzbin.info/www/bejne/lZDMfIakhr2YldE Links www.redhat.com/sysadmin/suid-sgid-sticky-bit

[@hegjon]

You can specify with -d flag that you intended to get info about the folder and not its content, ls -ld files

[@danikoburrell-archie7385]

Helped out a lot! I'm currently in a linux for jobs course and this was extremely insightful!

[@everdrone97]

As always, great work and very helpful

[@KowboyUSA]

Very helpful video 👍👍

[@christiangeorge5313]

Thanks, man. This really helped me!

[@carmiwisemon740]

Was very helpful

[@peterchaima2699]

Thank you

[@ghostintheshelf8660]

Great series! Could anybody explain why on ~ 6:00 for file5 we had permissions like: - rw- rw- r - - and after umask 0424 it became: - -w - r - - - w - We removed 'r' permission on others, but where does this 'w' permission on others comes from? we didn't have it previously

[@david-hasselhoff7483]

Files start with permission 666, so rw-rw-rw-. Write the umask in binary and everytime you see a '1' the corresponding permission will get knocked out. For file5 he used the umask 0002 (binary 000000010). The only '1' here knocks out exactly that 'w' that is missing for file5. For file6 he used the umask 0424 (binary 100010100). Note that at the position where we had a '1' for umask 0002 we now have a '0'. Thus the 'w' remains.

[@santosjaguar2000]

thanks

[@Fabiandur]

I don't think suggesting a decimal converter to read the binary values is especially desirable :D maybe just tell the viewer to learn elementary binary