On Thu, Jun 02, 2016 at 07:56:46AM -0400, Nick Holland wrote: > Documentation is an art (though, honestly...jmc@ makes it almost a > science...it's amazing to watch, really). Include too much, the > important details "everyone needs to know" are lost in the noise of > "stuff most people/target audience already knows". Include too little, > you will baffle new users.
+1. I really like the man pages. I can look up man do-thing and find out whether the option I forgot was -e or -t. Or I can find out, basically what do-thing does. If I am still lost, the internet and books packages may be the best way to fill in the full details. man cvs is not going to give you an expert's understanding of cvs. the cvs-guide book might. > > OpenBSD has over 600 basic commands in the standard install (not > counting X). If you have to document basic Unix usage functionality in > each man page, the signal to noise ratio will drop to useless for users > on their second week of using Unix. So yes, a certain basic Unix > knowledge is expected. > I came to OpenBSD from Windows 2000, passing through several Linux distributions (which I did not like), until I encountered a mention of OpenBSD on some web page. I went to www.openbsd.org, read pages and that was that. Just what I felt was right for me. Learning Unix usage is hard, but it's so powerful. I would like some man pages longer. I would like some man pages shorter or broken up into several pieces. I bet other people agree, but I bet they aren't the same ones I would like changed. Oh well. Thanks for the great holy man pages scrolls. ;) Chris
