Re: [osol-code] creating a kernel thread

2007-09-12 Thread Garrett D'Amore
Paul Durrant wrote: > On 04/09/07, Joachim Worringen <[EMAIL PROTECTED]> wrote: > >> I'm porting a driver from Linux to (Open)Solaris. The driver uses its own >> threads, which under Linux are created with a simple kernel_thread() call. I >> don't see such a call under Solaris. A solution coul

[osol-code] code review request.... mostly Makefiles and packaging... but also dmfe code changes

2007-09-12 Thread Garrett D'Amore
This was originally supposed to be just a code review for porting dmfe to x86, but there were some other outstanding dmfe bugs. Then when I got into packaging, it got ugly, and I discovered some other problems... particularly related to the use of a few /etc/ files in the packaging system. I'

[osol-code] Fwd: [foss.in] FOSS.IN/2007 Project Days sessions

2007-09-12 Thread S h i v
Hi All, FOSS.in (http://foss.in) is a premier annual foss event that happens in India. The event format this year includes project days(mini-conf to get more developers/contributors) & conference days(various talks/sessions). It is with pleasure that I bring it to notice that a proposal to host "

Re: [osol-code] rm and cp return non zero value

2007-09-12 Thread Casper . Dik
>If the return code is not -1 then the errno is not reliable. > >Look in /usr/include/sys/wait.h, specifically at the WEXITSTATUS() and >friends macros. The return code is in the format of a stat returned from > a call to wait functions. > >return value of 1, when put through the WEXITSTATUS ma

Re: [osol-code] rm and cp return non zero value

2007-09-12 Thread Paul Winder
If the return code is not -1 then the errno is not reliable. Look in /usr/include/sys/wait.h, specifically at the WEXITSTATUS() and friends macros. The return code is in the format of a stat returned from a call to wait functions. return value of 1, when put through the WEXITSTATUS macro give