weird chown option that's only available in man page.. what on earth is chown root /u ? is /u is an option/ flag to chown command?
I came across chown cli option from man page: "chown root /u" . I can't understand the explaination and can't find any related info in internet.
According to my search so far, i can't locate any chown command come with "/u" option.. What on earth is that ? Code:
|
/u is not an option but an [example] directory or file to work on.
|
One thing I know for certain is that many man pages aren't exactly understandable to most people. Is one of the frustrations many have, myself included when were are told "go read the man pages". That being said in this case I'm amazed they didn't put something like chown root /path or something. U is kind of random out of nowhere. If you are already familiar with the command line then you understand it immediately. But to a person who is just learning it doesn't make much sense, especially if they come from a Windows background where cmd options are passed that way.
|
Look at:
Code:
chown --help |
And if it helps you:
Code:
man -t chown | ps2pdf - chown1.pdf |
|
:eek: what are these ?:eek: lol You just gave me more HOMEWORK to do.. it is a link to chain linked to another.. That's why it takes a lot of time for me to learn something.. because from trying to install slax iso onto usb, i have to learn how to convert 9660iso into hybrid iso, and to learn to convert, i want to understand loop device... and from there i landed on chown.. .and from chown /u i am diverted to roff2text and ps2pdf all these things (that i have never heard before).. .. no end.. rabbit hole.. lol .. but thanks for letting me know there is such cli on my system...
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
I have read thru your how to read man page article.. I must admit, it is very infomatic.. but for certain part that i don't understand; it is hard for me to imagine what you said.. If you include some photo or example, it would be much easier for people like me who rather learn by example. Anyway, Thanks for your effort. |
One of the first things one needs to learn how to do in any new environment is how to read the documentation. Since I started coding back in the 70s I’ve had to learn at least eight or nine documentation systems (anyone remember Burroughs railroad diagrams…in 3-ring binders?)
As has been said, *nix man pages are one of the most challenging, probably because they are written by several (thousands?) different people/groups. hazel’s guide is excellent! |
Quote:
This was an example (man chown). There is no common and general way. As it was written: Quote:
|
Quote:
Code:
How man pages are organised |
Many of the man pages give examples on how to use the command. Most expect the user to have a basic understanding of the command line and how to read the usage part at the top (the synopsis).
For example, with chown I see this. Code:
NAME Thus the example "chown root /u" is really easy to understand. In english it means change ownership of /u to the user root. Almost all basic commands are command --> option --> file and if you can remember that you will not be caught by surprise by the examples. Also, remember that examples are examples and not to be taken literally. |
All times are GMT -5. The time now is 12:36 AM. |