Subject: Re: m_copy - doesn't copy if M_EXT is set.
To: None <tech-net@netbsd.org>
From: Justin C. Walker <justin@apple.com>
List: tech-net
Date: 10/04/1999 13:14:33
> From: Ignatios Souvatzis <is@jocelyn.rhein.de>
> Date: 1999-10-04 13:02:36 -0700
> To: "Justin C. Walker" <justin@apple.com>
> Subject: Re: m_copy - doesn't copy if M_EXT is set.
> Cc: Darren Reed <darrenr@reed.wattle.id.au>, tech-net@netbsd.org
> In-reply-to: <199910040023.RAA00642@walker3.apple.com>; from Justin C. 
> Walkeron Sun, Oct 03, 1999 at 05:23:24PM -0700
> X-Mailer: Mutt 0.95.6i
>
> On Sun, Oct 03, 1999 at 05:23:24PM -0700, Justin C. Walker wrote:
> > > From: Darren Reed <darrenr@reed.wattle.id.au>
> > > Date: 1999-10-03 06:38:03 -0700

[snip]

> >    You're correct about the behavior of m_copy()/m_copym(), but not   
> > about it's having changed.  This is old behavior.
>
> >From before 4.4BSD, even, I think. Does anybody have a 4.3BSD  
book handy?

It's in the 4.3 BSD book, and I'm pretty sure it's been that way  
since clusters were introduced.  The idea was to avoid a lot of  
copying.  It just has that one nasty little side-effect (it doesn't  
really produce a copy).

Regards,

Justin

--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics       |
Manager, CoreOS Networking            | When crypto is outlawed,
Apple Computer, Inc.                  | Only outlaws will have crypto.
2 Infinite Loop                       |
Cupertino, CA 95014                   |
*-------------------------------------*-------------------------------*