From owner-freebsd-current Mon Mar 13 2:40:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id CEEA837BA1A; Mon, 13 Mar 2000 02:37:03 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id MAA09348; Mon, 13 Mar 2000 12:36:54 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003131036.MAA09348@zibbi.mikom.csir.co.za> Subject: Re: latest 4.0 snapshot breaks tcpdump In-Reply-To: from Kris Kennaway at "Mar 13, 2000 01:46:59 am" To: kris@hub.FreeBSD.ORG (Kris Kennaway) Date: Mon, 13 Mar 2000 12:36:54 +0200 (SAT) Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > IMO (and I suggested this the other day), we should make the crypto > > > collection mandatory, and have sysinstall ask a question about whether to > > > point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is > > > > I'm still waiting for your diffs which do this. :) > > Well yeah, that's fun to say, but my days have been literally completely > full with getting other things ready for 4.0, without trying to figure out > sysinstall on top of it all. All I can do is warn you to expect bug > reports about this once people start upgrading to 4.0. Can't it be handled the same way init, ppp and a few others are? The binary shipped in the bin distribution is compiled/linked without crypto, but then a version compiled/linked with it is included in the crypto distribution. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message