IT/Software/Command Line: Difference between revisions
Jump to navigation
Jump to search
Access restrictions were established for this page. If you see this message, you have no access to this page.
Walttheboss (talk | contribs) |
Walttheboss (talk | contribs) |
||
Line 10: | Line 10: | ||
There are many ways to do this. Half of them may be more clever. | There are many ways to do this. Half of them may be more clever. | ||
<code>sudo chown | <code>sudo chown walt:walt /path/to/filename</code> | ||
This will make the file filename belong to the user walt and the group walt. Usually we change the group and user at the same time. | |||
OR | OR | ||
Line 19: | Line 21: | ||
===Changing Permissions=== | ===Changing Permissions=== | ||
This is very similar except we use chmod instead of chown | |||
<br /> | |||
==More modifiers== | ==More modifiers== | ||
__FORCETOC__ |
Revision as of 13:43, 14 February 2020
Welcome to the dark world where most IT people live
- This is a gui free world
- If you don't know what a gui is please quietly close the page and go buy a slurpee
- If you don't know what a slurpee is we feel sorry for you.
Basic Commands
Changing Ownership
There are many ways to do this. Half of them may be more clever.
sudo chown walt:walt /path/to/filename
This will make the file filename belong to the user walt and the group walt. Usually we change the group and user at the same time.
OR
sudo chown 777 /path/to/directory/
Adding the -R flag after the chown will recusre into directories and files.
Changing Permissions
This is very similar except we use chmod instead of chown