The programs are userspace. The argument of 2.4.* <-> 2.6.* was given by a sysadmin, I do not know to which extent the sysadmin was competent.
However, he said it was the cause of not upgrading company RHEL-servers to 2.6.* kernel. On Mon, 23 Jan 2006 20:25:08 -0500 Lee Revell <[EMAIL PROTECTED]> wrote: > On Tue, 2006-01-24 at 03:15 +0200, Sergei Steshenko wrote: > > SYNOPSYS and Cadence VLSI-related tools are a few examples, though, > > as far as SYNOPSYS is concerned, only 2.4.* (and NOT 2.6.*) kernels > > are supported because the former are considered to have stable API. > > The API exported to userspace via system calls IS stable. It's only the > internal kernel module API that's not stable. > > Aren't these userspace programs? If so they do not need to worry about > the kernel version. From the userspace POV 2.6 is binary compatible > with 2.4. > > Lee > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
