|
2009-12-22
, 23:39
|
Posts: 200 |
Thanked: 15 times |
Joined on Dec 2009
@ São Paulo - Brasil
|
#12
|
|
2009-12-28
, 09:26
|
Posts: 200 |
Thanked: 15 times |
Joined on Dec 2009
@ São Paulo - Brasil
|
#13
|
|
2009-12-28
, 09:30
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#14
|
|
2009-12-28
, 09:33
|
Posts: 200 |
Thanked: 15 times |
Joined on Dec 2009
@ São Paulo - Brasil
|
#15
|
|
2009-12-28
, 09:40
|
|
Posts: 552 |
Thanked: 183 times |
Joined on Oct 2009
@ Not decided
|
#16
|
|
2009-12-28
, 09:41
|
Posts: 200 |
Thanked: 15 times |
Joined on Dec 2009
@ São Paulo - Brasil
|
#17
|
|
2009-12-28
, 23:41
|
Posts: 529 |
Thanked: 46 times |
Joined on Sep 2007
|
#18
|
|
2009-12-29
, 00:06
|
Posts: 200 |
Thanked: 15 times |
Joined on Dec 2009
@ São Paulo - Brasil
|
#19
|
|
2009-12-29
, 00:08
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#20
|
into manual supported by working examples,
as man pages are great as help on syntax, semantics.
But there is a problem how to build working example, script, code
from a raw man page.
Visited many Linux/ Unix support web forums
and the same questions are asked million times, over and over again,
so it looks like
Unix/Linux man pages
are not intuitive for ppl like we.
And exactly.
Unix/Linux man pages were written by top Unix/Linux developers.
So what is easy for a Unix guru is not exactly easy
for beginners like us.