From owner-freebsd-hackers  Tue Aug 31  0: 4:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6C1181582A; Tue, 31 Aug 1999 00:04:23 -0700 (PDT)
	(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
	by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA34086;
	Tue, 31 Aug 1999 09:04:10 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <199908310704.JAA34086@gratis.grondar.za>
To: itojun@iijlab.net
Cc: core@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: KAME IPv6 and freebsd 
Date: Tue, 31 Aug 1999 09:04:09 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >I'll be very happy to work with you on this one.
> 
> 	Does it make sense to make src/crypto/sys for kernel code?
> 	(for IPsec we need crypto code *in kernel*).

I wonder...

There was a contrib/sys (where softupdates went), and that got moved
to sys/contrib.

Perhaps something similar could be invented for src/crypto? We'd need
to make the distibution machinery understand that, but I don't see
too much a problem there.

I have no strong feelings about src/crypto/sys or src/sys/crypto.

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message