Seems to me that all you have to do is give an advice on what to read. That way, you're not telling people to read certain things, you're not forcing them to do anything. The ones that will learn everything from man pages and faqs can do that, the others can take a look at the advice.
You could 'certify' certain books. If there is such good material from Sybex and O'Reilly, why compete? Review those books, and specify wich one could be seen as the best for a newbie to unix/bsd, wich one is better to really check up on all the details, and so forth. In my opinion we should really start to get something done, now that we're starting to attract the media. I know there are translating teams (I'm in one of them :) ), how about starting a material-reviewing team too, and perhaps localise those too (not to sure on that, there is hardly any serious Dutch material on BSD for instance). When the list of topics Jeremy Reid is compiling is finished, a 'team' to design questions on those topics could be set up. Of course we shouldn't put the tests on the wiki :-) Well, that's enough spewing for now, Lucas >> The question of 'study materials' keeps cropping up, specifically around licensing of that material. >> As many of us have stated repeatedly, the problem with publishing BSD books >> is that you are competing with some of the better documentation in technology. >> George > Many > advanced BSD users can find out on their own data regarding specific > subjects, but most of the beginners don't know where to look or how to look. Also, nobody can know everything and this is the reason why even advanced users will benefit from that knowledge. > > Andrei _______________________________________________ BSDCert mailing list [email protected] http://lists.nycbug.org/mailman/listinfo/bsdcert
