On 07/12/2013 10:47 AM, Charles Steinkuehler wrote:
> Yes, and it should be noted that the number of problems due to
> documentation and support issues for the BeagleBone exploded after the
> Black was released due not only to the major changes to the hardware
> but also to the major structural changes on the software side caused
> by switching to the 3.8 kernel.
>
> IMHO, the new RTOS and unified build code represents a similar split
> for LinuxCNC, where a lot of existing documentation could be
> misleading or just plain wrong.  There should be a well marked
> location to find the current documentation, and a clear indication
> that anything *NOT* found in the official location(s) is potentially
> outdated and wrong.

Also a very important reason to put dates in documentation - I sometimes do a 
cnt-i in firefox in an 
attempt to find the date - but often it is misleading -  something spit out by 
php..

Clue lines like: "as of may 2012" or "as of kernel x.y.z" can be of great help 
down the road.


--------------------------------------------------------------------------------
Karl Schmidt                                  EMail [email protected]
Transtronics, Inc.                              WEB 
http://secure.transtronics.com
3209 West 9th Street                             Ph (785) 841-3089
Lawrence, KS 66049                              FAX (785) 841-0434

The lack of a middle class is a good indicator of how corrupt a government is.
kps
--------------------------------------------------------------------------------

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to