From owner-freebsd-arch@FreeBSD.ORG Wed Feb 23 06:51:19 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EF15106566B; Wed, 23 Feb 2011 06:51:19 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A605C8FC0A; Wed, 23 Feb 2011 06:51:18 +0000 (UTC) Received: by vws16 with SMTP id 16so2664160vws.13 for ; Tue, 22 Feb 2011 22:51:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=IcjbxkHN6u98R1sBhKZxVHPUkfOElh8tCZga2U4/Ik4=; b=J7REbfd7hqcm5Nq4JMFsAXvhC9UOnABw/fha4jXveoplEAW81y1AoC2p4kMK+o40XU 2Vg19z260cRXV/r4BTWzo4e2TIgA/N0f05BL78njvq01EUg7LlQCPQFU3Pfn+VnQPKJi JnSX0LCcBbWJFfZ5BCMC3L1O/y/LieD0z2yTU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RtitDscbEnE5PWKipd3l+WBmELkCoFj5sSGXrubWL56iCMYlqnz5ZnoE2DcTwrfTHx c4qW6caqKL7XPopDNjkH3SD1ooqF+XUy2cO2fb+dOphGmFxftrYY5usaDFygqTnkw9/l ckWTMg0ML9js3nHUavZ8OWFTXn2Hzujvcr63M= MIME-Version: 1.0 Received: by 10.52.164.36 with SMTP id yn4mr5436419vdb.307.1298442130093; Tue, 22 Feb 2011 22:22:10 -0800 (PST) Received: by 10.52.166.74 with HTTP; Tue, 22 Feb 2011 22:22:10 -0800 (PST) In-Reply-To: References: <4D35CFFB.3010302@freebsd.org> <201102211612.51233.josh@tcbug.org> <201102220103.20158.josh@tcbug.org> <20110222205741.GA34103@server.vk2pj.dyndns.org> <6A5ECC9D-9EF4-4331-9BB0-E14FE6087D53@vicor.com> Date: Wed, 23 Feb 2011 01:22:10 -0500 Message-ID: From: Mehmet Erol Sanliturk To: Garrett Cooper Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org, Devin Teske , freebsd-sysinstall@freebsd.org, freebsd-arch@freebsd.org Subject: Re: FreeBSD Installer Roadmap X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Feb 2011 06:51:19 -0000 On Tue, Feb 22, 2011 at 10:41 PM, Garrett Cooper wrote: > On Tue, Feb 22, 2011 at 7:23 PM, Devin Teske wrote: > > > > On Feb 22, 2011, at 12:57 PM, Peter Jeremy wrote: > > > >> On 2011-Feb-22 02:50:54 -0800, Devin Teske wrote: > >>> That's the operative word here ("supports"). Lord help us when that > >>> changes to "requires" (that is to say, if/when the FreeBSD kernel > >>> becomes legacy-free with respect to supporting fdisk/disklabel > >>> partitioned disks). > >> > >> When that does come, it will probably be driven by BIOS and hardware > >> vendors dropping support for MBR. Current disks are at the upper > >> limit of what MBR can be support (and that's after several revamps of > >> MBR). Since GPT already provides a superior feature set without MBR's > >> limits, the next step will be to just drop MBR support. And when it > >> does come, FreeBSD needs to be ready with an installer that can cope > >> with non-MBR disks. > > While I love a good discussion (and there have been a number of good > points for either side on here), should we agree to switch the default > over to bsdinstall, leave sysinstall in (lumps or no lumps), then over > the period of the next 2~3 major (that amounts to 4~6 years) releases, > and retire sysinstall to the happy hunting grounds? sysinstall didn't > take up that much space on the release media I thought, and it might > be doable to map both sets of media so that sysinstall can work in > harmony on bsdinstall's release media? > > Preparing custom releases to use the sysinstall init_path isn't that > bad, so it would at least give the legacy folks time to transition > over while us guinea pigs burn in the new wax :)... > > Sound good? > > Thanks! > -Garrett > Yes , very much . My suggestion is to include the item sysinstall in BSD-Install by Nathan Whitehorn as an option in installation start up menu . In that way , existing installation works will be upward compatible with bsdinstall . My another suggestion is to move installation startup menu part into /boot/install/ directory for each architecture and allow platform specific installers by using common parts from common directories . For example , in PC-based installations ( amd64 , i386 , ... ) PC-BSD pc-sysinstall will be usable from bsdinstall as an option at present . In that form , the initial installation menu will be seen in PC environment as follows : bsdinstall ( by Nathan Whitehorn ) pc-sysinstall ( by Kris Moore ) sysinstall ( by John Hubbard ) Thank you very much . Mehmet Erol Sanliturk