From owner-freebsd-current Tue Jan 30 9: 1:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id B70A737B65D for ; Tue, 30 Jan 2001 09:01:00 -0800 (PST) Received: (qmail 77757 invoked from network); 30 Jan 2001 17:00:59 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 30 Jan 2001 17:00:59 -0000 From: "Patrick Bihan-Faou" To: "Poul-Henning Kamp" Cc: Subject: RE: vn, vnconfig and MFS death-warrant! Date: Tue, 30 Jan 2001 12:02:20 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <32187.980873109@critter> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > >Could these modifications be ported to -STABLE to ease up the transition > >from -STABLE to -CURRENT ? I don't know if this is tied deeply on other > >changes in -CURRENT, but if it is not I'd like to use the new facility. > > I think I would rather leave -stable out of this for now. There are > too many deployed production systems I think. Just to make my intentions clear, I am not asking to remove vn/vnconfig(8)/mfs from -STABLE, I was just asking for the inclusion of md/mdconfig in -STABLE so that people (at least me :) ) can get ready for the day 5.0 will becomes -STABLE... My other problem is that I use vn's heavily and I find that some of their limitations are really annoying. While I could hack the relevent code to make myself happy, I think that there is little value in me doing that when it is obvious that they are going away in the not so distant future (5.0). Anyway, this is not a big deal. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message