From owner-freebsd-hackers Tue Aug 31 2:58:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 276EC150ED for ; Tue, 31 Aug 1999 02:58:31 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA00510; Tue, 31 Aug 1999 02:58:03 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: "Jordan K. Hubbard" , itojun@iijlab.net, Mark Murray , hackers@FreeBSD.ORG Subject: Re: KAME IPv6 and freebsd In-reply-to: Your message of "Tue, 31 Aug 1999 10:36:29 +0200." <28187.936088589@critter.freebsd.dk> Date: Tue, 31 Aug 1999 02:58:02 -0700 Message-ID: <506.936093482@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. That's a point. I was thinking primarily of the "segregate the crypto" issue, but you're right that this would also put us back to the "bad old days" where sys/ was broken across multiple directories. Hmph. I guess common sense wins over ITAR in this case. :) - Jordan > In message <10335.936082907@localhost>, "Jordan K. Hubbard" writes: > >> Does it make sense to make src/crypto/sys for kernel code? > >> (for IPsec we need crypto code *in kernel*). > > > >I'd say it makes a lot of sense. > > Yes, but shouldn't it be src/sys/crypto if we want to have > "kern-developer" still have a sensible meaning ? (and for > all the other reasons which made us move src/contrib/sys to > src/sys/contrib) > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message