Re: retrive data from mbuf chain

2008-02-15 Thread Biks N
Please ignore my previous post. I was having problem because I didn't allocate memory to my_data_copy. Also, the correct usage is: m_copydata( m, 0, m->m_pkthdr.len , (caddr_t) my_data_copy); thanks On Tue, Feb 12, 2008 at 12:05 PM, Biks N <[EMAIL PROTECTED]> wrote: > Hi, thanks to everyone

Re: x86: sigaltstack problems

2008-02-15 Thread Kostik Belousov
On Fri, Feb 15, 2008 at 09:40:09AM +0200, Sergei Trofimovich wrote: > On Thu, 14 Feb 2008 11:40:21 -0700 > Bert JW Regeer <[EMAIL PROTECTED]> wrote: > > > On Feb 14, 2008, at 08:46 , Sergei Trofimovich wrote: > > > > > Attached file causes segfaults on freebsd 4,5,6 > > > but keeps alive in linux

Re: x86: sigaltstack problems

2008-02-15 Thread Sergei Trofimovich
On Thu, 14 Feb 2008 11:40:21 -0700 Bert JW Regeer <[EMAIL PROTECTED]> wrote: > On Feb 14, 2008, at 08:46 , Sergei Trofimovich wrote: > > > Attached file causes segfaults on freebsd 4,5,6 > > but keeps alive in linux. > > > > IANIAML, so please CC me explicitly. > > > > Thanks! > > You did not at

Re: licensing question APSL

2008-02-15 Thread Dag-Erling Smørgrav
Robert Watson <[EMAIL PROTECTED]> writes: > I think it's a significant testament to the quality of the Solaris > parts we've been pulling in (ZFS, DTrace) that CDDL parts are now in > the base tree. They are carefully marked and isolated to make it easy > to build CDDL-free systems in the same way

Re: licensing question APSL

2008-02-15 Thread Dag-Erling Smørgrav
Brooks Davis <[EMAIL PROTECTED]> writes: > APSL is not generally accepted in the base. It may be acceptable in > certain circumstances, but strong technical justification is generally > required for inclusion. Which brings us to my reaction to the PR, which is "why do we even need this?" Stick i