From owner-freebsd-current Tue Jan 30 9: 1:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 7E1E637B67D; Tue, 30 Jan 2001 09:00:56 -0800 (PST) Received: from localhost.mzaki.nom (166.pool5.ipctokyo.att.ne.jp [165.76.43.166]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/06/00)) id CAA01666; Wed, 31 Jan 2001 02:00:54 +0900 (JST) Date: Wed, 31 Jan 2001 02:00:53 +0900 Message-ID: <86hf2hx9dm.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: phk@freebsd.org Cc: current@freebsd.org Subject: Re: vn, vnconfig and MFS death-warrant! In-Reply-To: In your message of "Tue, 30 Jan 2001 11:30:30 +0100" <29877.980850630@critter> References: <29877.980850630@critter> X-Mailer: Wanderlust/1.1.1 (Purple Rain) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 30 Jan 2001 11:30:30 +0100, Poul-Henning Kamp wrote: > March 1st I will remove the functionality from mount_mfs and > vnconfig, leaving only the message which will be an error obviously. > April 1st I will remove vn, vnconfig and mount_mfs entirely. I think we should postpone the complete removing for a year (on release of 5.2), to give people a migration sugar. System upgrading (4.x -> 5.x) will cause confusing situation, for example, living old 4.x vnconfig binary and new and splendid mdconfig. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message