--s/l3CgOIzMHHjg/5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 19, 2004 at 01:20:45PM -0800, Jonathan Stone wrote:
> In message <20040319200945.GX17009@che.ojctech.com>David Young writes
> >On Fri, Mar 19, 2004 at 11:53:46AM -0800, Jonathan Stone wrote:
>=20
>=20
> >Is kcont in-tree?
>=20
> Not yet. Whilst on vacation, I addressed the comments from the last
> posting. Give me about another 12 hours to check the manpage, and
> (disasters aside) it should be in.
>=20
> If you use kcont, I'd be glad to help debug any issues that arise.
> The "sample app" I intended to commit was a was splice(2), but it
> turns out NetBSD's Unix-domain socket code has far, far too many ugly
> "curproc" dependencies for that to be feasible in the short term.

Is it just the Unix-domain socket code? If so, wouldn't it be reasonable=20
to include a sample splice(2) that just errors out if one side or the=20
other is a Unix-domain socket? Certainly as an lkm it'd be a good "sample=
=20
app."

Take care,

Bill

--s/l3CgOIzMHHjg/5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAW3ACWz+3JHUci9cRAihnAJ9U2Blv6DdkVUDAnoHe5AzCGlESZQCfQYf6
ecG0s05gC70l7lj8qkguc1E=
=yB29
-----END PGP SIGNATURE-----

--s/l3CgOIzMHHjg/5--