On 07/22/14 11:37, Sebastian Martinez wrote: > my current jffnms is a 0.8.4 version on rhel 4.4 and the kernel is > > Linux nbsf000p5ap06 2.6.9-42.0.3.EL #1 SMP Mon Sep 25 17:22:04 EDT 2006 > ppc64 ppc64 ppc64 GNU/Linux > > and works fine
From your first post on kernel version: kernel Linux nbsf000p5ap06.nbsf.com.ar 2.6.32-431.17.1.el6.ppc64 #1 SMP Fri Apr 11 17:30:35 EDT 2014 ppc64 ppc64 ppc64 GNU/Linux Now you are saying : Linux nbsf000p5ap06 2.6.9-42.0.3.EL #1 SMP Mon Sep 25 17:22:04 EDT 2006 ppc64 ppc64 ppc64 GNU/Linux kernel version 2.6.32 is vintage 2010. run 'uname -r' on your system and report back. Really? Why do you think many dedicated folks work constantly on improving how the linux kernel works? Why do you think folks work on codes that comprise the operating system and tools on top of the linux kernel? <BUGS> 2.6.9 versions of the linux kernel are archane and deprecated. Why are you still on jffnms 8.4? 9.4 is stable and contains many bug fixes and enhancements. Read this vintage discussion from 2009: http://forum.codecall.net/topic/45462-buffer-underflow-with-fgets-and-popen/ popen might not fix the problem. Threads from around this time correspond to the old kernel found in your linux (commercial) distro. "Threads" and their implementation in the kernel and the operating systems and applications have changed quite a bit. caveat emptor, Later, James ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ jffnms-users mailing list jffnms-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jffnms-users
