Post by KenboYeah, I've used QNX since the late 80s. I remember they opened up a
good amount of their code for awhile, but they never opened the kernel
source.
No, they opened the kernel source:
http://www.qnx.com/news/pr_2471_1.html
Just as a fer-instance, here's services/system/ker/:
_main.c kerext_misc.c nano_sync.c
aps/ kerext_page.c nano_syspage.c
arm/ kerext_process.c nano_thread.c
asmoff.c kerext_query.c nano_timer.c
cpu_debug.c kerext_reboot.c nano_trace.c
dbg_rec.c kerext_stack.c nano_vector.c
emm_init_mem.c kerext_trace.c nano_xfer.c
emm_mmap.c kermacros.h nano_xfer_check.c
emm_munmap.c kerproto.h nano_xfer_cpy.c
emm_pmem_add.c kertrace.h nano_xfer_len.c
emm_vaddr_to_memobj.c kexterns.c nano_xfer_msg.c
externs.h kgetopt.c nano_xfer_pulse.c
idle.c kmain.c ppc/
init_nto.c kprintf.c sh/
init_objects.c ktest.c shutdown_nto.c
ker_bad.c mdriver.c smm_aspace.c
ker_call_table.c miniproc_image.c smm_configure.c
ker_channel.c miniproc_start.c smm_debuginfo.c
ker_clock.c mips/ smm_dup.c
ker_connect.c module_list.S smm_fault.c
ker_fastmsg.c* nano_alloc.c smm_madvise.c
ker_interrupt.c nano_asyncmsg.c smm_map_xfer.c
ker_message.c nano_clock.c smm_mapinfo.c
ker_net.c nano_conf.c smm_mcreate.c
ker_nop.c nano_connect.c smm_mdestroy.c
ker_ring0.c nano_cred.c smm_memobj_phys.c
ker_sched.c nano_debug.c smm_mlock.c
ker_signal.c nano_event.c smm_mprotect.c
ker_sync.c nano_fp_emu.c smm_msync.c
ker_sys.c nano_interrupt.c smm_munlock.c
ker_thread.c nano_kerdebug.c smm_resize.c
ker_timer.c nano_lookup.c smm_swapper.c
ker_trace.c nano_memphys.c smm_vaddrinfo.c
kerargs.h nano_message.c smm_validate.c
kerext_bind.c nano_misc.c smp_flush_tlb.c
kerext_cache.c nano_object.c smp_get_cpunum.c
kerext_cpumode.c nano_pulse.c smp_send_ipi.c
kerext_cred.c nano_query.c walk_asinfo.c
kerext_debug.c nano_sched.c x86/
kerext_idle.c nano_signal.c xray/
kerext_limits.c nano_smp_interrupt.c
kerext_mempart.c nano_specret.c
Perhaps you and I don't agree on what the words "kernel source" mean?
(This came right off their then-public CVS repo.)
Andy