From owner-freebsd-current@FreeBSD.ORG Fri Oct 14 13:37:43 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3636B106566B for ; Fri, 14 Oct 2011 13:37:43 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from mail.xcllnt.net (mail.xcllnt.net [70.36.220.4]) by mx1.freebsd.org (Postfix) with ESMTP id 03C518FC16 for ; Fri, 14 Oct 2011 13:37:42 +0000 (UTC) Received: from [172.23.7.198] (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mail.xcllnt.net (8.14.5/8.14.5) with ESMTP id p9EDbYMi034125 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Oct 2011 06:37:41 -0700 (PDT) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=windows-1252 From: Marcel Moolenaar In-Reply-To: <4E97E9E5.2020908@FreeBSD.org> Date: Fri, 14 Oct 2011 06:37:29 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4E580B14.7090208@FreeBSD.org> <1A828073-1D5F-4850-9379-4AB62CF3DAE3@xcllnt.net> <4E5B4BFB.9040907@FreeBSD.org> <4E5BF43A.5050306@FreeBSD.org> <4E5CB502.5020508@FreeBSD.org> <4E97E9E5.2020908@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1244.3) Cc: FreeBSD-Current Current Subject: Re: possible mountroot regression X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2011 13:37:43 -0000 On Oct 14, 2011, at 12:51 AM, Andriy Gapon wrote: > on 30/08/2011 13:01 Andriy Gapon said the following: >>=20 >> So, just to re-iterate, I think that this is indeed a regression and = the one >> that could be particularly unhelpful for a new release - the time = when people >> are much more likely to end up at the mountroot prompt during an = installation of >> a new system or an upgrade. >=20 > Marcel, >=20 > is there any chance that this regression can be fixed before the = release? Probably, yes. How do you want to fix this? You haven't really expressed what you would like to see, other than mentioning that you think it's a regression from before. Arguably, the previous behaviour had a lot to be desired for so since you're worried about the user experience, thinking this through is important. > If not, then maybe it would be proper to pull the change that = introduced it out > of the release branch (r214006) ? Don't be ridiculous. --=20 Marcel Moolenaar marcel@xcllnt.net