Subject: Re: m_copy - doesn't copy if M_EXT is set.
To: Darren Reed <>
From: Thor Lancelot Simon <>
List: tech-net
Date: 10/04/1999 13:29:10
On Mon, Oct 04, 1999 at 07:46:53PM +1000, Darren Reed wrote:
> In some email I received from, sie wrote:
> > 
> > >So far I've received two replies from people who've added this behaviour
> > >in (yourself and one other) and I also require it.  Maybe there will be
> > >others in the future, maybe not, but surely if there's two or more uses
> > >for this, it has to be worth adding to the kernel ?
> > 
> > 	I'm happy to use new flag whenever it is made available, but 
> > 	I also fear another *BSD incompatibility...
> OpenBSD will pick it up, sooner or later (:-), and we can probably get
> it into FreeBSD as well...leaving BSDI, who seem to do their own thing
> anyway.

Of course, we've already been told what name Darwin is using for this -- I
suggest we follow their example and call it m_dup(), or at least provide
a compatibility macro.