How to use the umask command: 2-Minute Linux Tips

The video tutorial explains the UMASK command, which sets default file permissions. It highlights that UMASK acts as a mask, meaning settings are the opposite of what might be expected. For instance, setting UMASK to 777 results in no permissions for files. Conversely, setting it to 000 grants read and write permissions but not execute. The tutorial also notes that UMASK changes do not affect existing files and that the current UMASK can be checked by typing 'umask'. Additionally, it discusses the relationship between UMASK and chmod, particularly the sticky bit.

What happens when you set the umask to 777?

• Files have read-only permissions

• Files have no permissions

• Files have execute-only permissions

• Files have full permissions

Which permissions are never set by default, regardless of umask settings?

• Read permissions

• Write permissions

• All permissions

• Execute permissions

If you set your umask to 000, what permissions will new files have?

• Execute permissions only

• Read and write for everyone, no execute

• Full permissions for everyone

• No permissions at all

How can you check the current umask setting?

• By checking the file properties

• By logging into your account and typing 'umask'

• By using the ls command

• By using the chmod command

What is the typical umask setting and what does the first digit represent?

• 0000, and the first digit sets execute permissions

• 0777, and the first digit sets read permissions

• 0002, and the first digit is irrelevant

• 0022, and the first digit sets write permissions