From owner-freebsd-questions@FreeBSD.ORG Thu Jan 19 17:03:28 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C5281065704 for ; Thu, 19 Jan 2012 17:03:28 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id C42F58FC0C for ; Thu, 19 Jan 2012 17:03:27 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa04 [127.0.0.1]) by ltcfislmsgpa04.fnfis.com (8.14.4/8.14.4) with SMTP id q0JGViaZ009392; Thu, 19 Jan 2012 11:03:24 -0600 Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa04.fnfis.com with ESMTP id 12eps0g471-16 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 19 Jan 2012 11:03:24 -0600 Received: from [10.0.0.104] (10.14.152.28) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 19 Jan 2012 11:03:15 -0600 MIME-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset="us-ascii" From: Devin Teske In-Reply-To: <20120119164628.GC21488@hemlock.hydra> Date: Thu, 19 Jan 2012 09:03:13 -0800 Content-Transfer-Encoding: quoted-printable Message-ID: <8C3EC4C9-2354-4791-A40C-F4CDC07E371E@fisglobal.com> References: <8397.74345881796$1326968162@news.gmane.org> <20120119164628.GC21488@hemlock.hydra> To: Chad Perrin X-Mailer: Apple Mail (2.1084) X-Originating-IP: [10.14.152.28] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7361, 1.0.211, 0.0.0000 definitions=2012-01-19_07:2012-01-19, 2012-01-19, 1970-01-01 signatures=0 Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 9 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 17:03:28 -0000 On Jan 19, 2012, at 8:46 AM, Chad Perrin wrote: > On Thu, Jan 19, 2012 at 10:41:37AM +0000, inquiz wrote: >> Eduardo Morras retena.com> writes: >>=20 >>> ...=20 >>> I think that a full/complete update of the old installer to add it=20 >>> support GEOM, ZFS, scripting and more newer features will consume=20 >>> more manpower and resources than create a new one from scratch, where= =20 >>> the devs aren't chained by old code, backwards compatibility, old=20 >>> restrictions and old point of views. This way, is easier correct=20 >>> bugs, new features, simplify the installation and even automate it to= =20 >>> this new installer than try to add them to the old one. >>>=20 >>> As always, i suppose that any ideas and help are welcome. >>> ... >>=20 >> If devs decided that there are good technical and other reasons to retire >> the old installer, then that's fair enough. >> But then the new installer has to be at least equal in features, functio= nality, >> and overall quality. >=20 > . . . or provide the ability to select the old installer at boot time, > perhaps. Let's not turn this into a false dilemma; I don't see why we > can't have our cake and eat it too for a while. >=20 Before sysinstall is simply "made available" as an option, it first needs t= o be taught how to handle a monolithic txz file because the structure of th= e system has changed. Also... sysinstall expects to boot into a RW filesystem, and I don't know y= et whether the architecture has changed in this respect. If bsdinstall does= n't boot into an MFS, then having the boot loader set vfs.root.mountfrom.op= tions to "rw" is of little effect (for example, if you're booting directly = into an ISO 9660 filesystem which can't be made writable -- unionfs aside). So, whatever prompt the user is given to choose between sysinstall and bsdi= nstall... said prompt best be pretty early in the game (if we're going to f= ork to two different operating environments: MFS versus ISO 9660). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.