2010-06-17 Joel Sherrill <joel.sherrill@oarcorp.com>

* Makefile.am, configure.ac, index.html.in, develenv/direct.t,
	posix_users/gen_size_report, started/nextstep.t,
	started_ada/buildada.t, user/conf.t, user/object.t: Remove ITRON API.
	* itron3.0/.cvsignore, itron3.0/Makefile.am, itron3.0/config.t,
	itron3.0/eventflags.t, itron3.0/fixedblock.t, itron3.0/gen_all,
	itron3.0/gen_section, itron3.0/gen_status_shell,
	itron3.0/interrupt.t, itron3.0/itron.texi, itron3.0/mailbox.t,
	itron3.0/memorypool.t, itron3.0/msgbuffer.t, itron3.0/network.t,
	itron3.0/preface.texi, itron3.0/rendezvous.t, itron3.0/semaphore.t,
	itron3.0/stamp-vti, itron3.0/status.t, itron3.0/task.t,
	itron3.0/tasksync.t, itron3.0/time.t, itron3.0/version.texi: Removed.

doc/started/nextstep.t

@@ -44,9 +44,6 @@ Classic RTEMS API based on the RTEID specification.
 @item @b{RTEMS POSIX API User's Guide} describes the 
 RTEMS POSIX API that is based on the POSIX 1003.1b API.
 
-@item @b{RTEMS ITRON 3.0 API User's Guide} describes
-the RTEMS implementation of the ITRON 3.0 API.
-
 @item @b{RTEMS Network Supplement} provides information
 on the network services provided by RTEMS.
 
@@ -103,7 +100,7 @@ initialization tasks or threads.  It is possible
 to configure an application to start with a 
 single thread that whose entry point is @code{main()}.
 
-Each API supported by RTEMS (Classic, POSIX, and ITRON)
+Each API supported by RTEMS (Internal, Classic, and POSIX)
 allows the user to configure a set of one or more tasks
 that are created and started automatically
 during RTEMS initialization.  The RTEMS Automatic
@@ -117,8 +114,6 @@ initialization task varies based up API.
 @item @code{Init} - single Classic API Initialization Task
 
 @item @code{POSIX_Init} - single POSIX API Initialization Thread
-
-@item @code{ITRON_Init} - single ITRON API Initialization Task
 @end itemize
 
 Regardless of the API used, when the initialization task executes,