Chmod Shorts
Description: Setting 777 permissions to a file or directory means that it will be readable, writable and executable by all users and may pose a huge security risk. For example, if you recursively change the permissions of all files and subdirectories under the /var/www directory to 777, any user on the system will be able to create, delete or modify files in that directory. If you experience permission issues with your web server, instead of recursively setting the permission to 777, change the file’s ownership to the user running the application and set the file’s permissions to 644 and directory’s permissions to 755. File ownership can be changed using the chown command and permissions with the chmod command.
Description: The hardest error message to accept in the terminal. This minimalist, philosophical design perfectly captures the feeling of trying to execute life and getting blocked at every turn. Featuring the command chmod +x life.sh and its execution ./life.sh, the system delivers the cold, cruel reality: > permission denied. With crisp green prompt symbols and stark red error text, this graphic is the ultimate dark-humor statement piece for Linux sysadmins, developers, programmers, and anyone having a tough day in the command line.
Description: whoami command is used both in Unix Operating System and as well as in Windows Operating System. It is basically the concatenation of the strings “who”,”am”,”i” as whoami. It displays the username of the current user when this command is invoked. It is similar as running the id command with the options -un.
Description: whoami command is used both in Unix Operating System and as well as in Windows Operating System. It is basically the concatenation of the strings “who”,”am”,”i” as whoami. It displays the username of the current user when this command is invoked. It is similar as running the id command with the options -un.
