Date: Sat, 19 Feb 2011 08:44:42 +0000 From: Bruce Cran <bruce@cran.org.uk> To: freebsd-sysinstall@freebsd.org Cc: freebsd-current@freebsd.org, Devin Teske <dteske@vicor.com>, Nathan Whitehorn <nwhitehorn@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: FreeBSD Installer Roadmap Message-ID: <201102190844.43267.bruce@cran.org.uk> In-Reply-To: <61079648-D76C-4699-AC4D-F6EBE64ABFFC@vicor.com> References: <4D35CFFB.3010302@freebsd.org> <4D5E945F.60106@freebsd.org> <61079648-D76C-4699-AC4D-F6EBE64ABFFC@vicor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 19 February 2011 03:04:39 Devin Teske wrote: > There are many reasons for this, and none of them are selfish (although it > remains possible to drum-up some selfish reason, all of the reasons behind > our motivation are in-fact unselfish). Truth-be-told, I welcome the > replacement of sysinstall but am very wary that ANY replacement will be > able to exactly replicate the hardware compatibility that sysinstall > currently enjoys. I do indeed envision a great celebration as FreeBSD-9 > bucks sysinstall but also at the same time have nightmares of receiving > waves of calls from people having trouble (for example) "installing > FreeBSD-9 on their AMD K6 based system, circa long-long-ago in a universe > far-far-away." (yes, we do have data centers running that very equipment > with uptime in the 1,000's of days). I think bsdinstall as it currently is is simple enough that there shouldn't be any compatibility issues: it uses gpart for partitioning, runs tools like tzsetup to configure settings etc. so there's far less to go wrong than sysinstall's custom code which for example could crash on the "probing devices" screen. -- Bruce Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102190844.43267.bruce>