Editing 149: Sandwich
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
| β | On both {{w|Windows}} and {{w|UNIX}} computer systems, users can be assigned all kinds of rights, for example rights to access certain directories and files, or to execute certain commands. The ''{{w|sudo}}'' command (pronounced "sue | + | On both {{w|Windows}} and {{w|UNIX}} computer systems, users can be assigned all kinds of rights, for example rights to access certain directories and files, or to execute certain commands. The ''{{w|sudo}}'' command (pronounced "sue due" or "pseudo") lets certain (authorized) UNIX users override these policies by executing the command (everything after the word "sudo" on the command line) as the root user. Root (sometimes called the superuser) has complete system powers, exempt from all access controls; it is similar to a Windows administrator, however even the powers of a Windows administrator is limited - the ''system32'' folder, for example, cannot be deleted because it is a critical part of the operating system, while there is no such restriction on UNIX - if a root user feels like (or accidentally) deletes a vital file, they are free to do so. As a result, common advice is to not use sudo unless the command in question absolutely requires it - indeed, most commands do not require such privileges. |
One very common activity for UNIX administrators is to install or configure software using the UNIX ''{{w|Make (software)|make}}'' command, e.g. <code>% '''make install'''</code>. Often this command requires administrative permissions in order to complete successfully, which in practice means the "<code>make ''this''</code>" command will fail unless it is typed as "<code>sudo make ''this''</code>" instead. However as mentioned before since most commands work just fine without sudo, along with general discouragement from using it willy-nilly, it is fairly common for people who use or administer UNIX systems to attempt a straight up <code>% make install</code> and have it fail. They then need to repeat the command with "sudo," whereupon the computer responds obediently, and everything works smoothly. | One very common activity for UNIX administrators is to install or configure software using the UNIX ''{{w|Make (software)|make}}'' command, e.g. <code>% '''make install'''</code>. Often this command requires administrative permissions in order to complete successfully, which in practice means the "<code>make ''this''</code>" command will fail unless it is typed as "<code>sudo make ''this''</code>" instead. However as mentioned before since most commands work just fine without sudo, along with general discouragement from using it willy-nilly, it is fairly common for people who use or administer UNIX systems to attempt a straight up <code>% make install</code> and have it fail. They then need to repeat the command with "sudo," whereupon the computer responds obediently, and everything works smoothly. | ||
