Date: Tue, 22 Feb 2011 19:41:05 -0800 From: Garrett Cooper <gcooper@FreeBSD.org> To: Devin Teske <dteske@vicor.com> Cc: freebsd-current@freebsd.org, freebsd-sysinstall@freebsd.org, freebsd-arch@freebsd.org Subject: Re: FreeBSD Installer Roadmap Message-ID: <AANLkTi=VeTkHhwTO%2BTxvAphk=N3U5UE%2BS_t=ihPb=2t1@mail.gmail.com> In-Reply-To: <6A5ECC9D-9EF4-4331-9BB0-E14FE6087D53@vicor.com> References: <4D35CFFB.3010302@freebsd.org> <201102211612.51233.josh@tcbug.org> <EA1368DF-9728-4492-B1FC-5F7C2B521DE7@vicor.com> <201102220103.20158.josh@tcbug.org> <D51E46BA-8902-4C42-A785-7EBF9F7A9B44@vicor.com> <20110222205741.GA34103@server.vk2pj.dyndns.org> <6A5ECC9D-9EF4-4331-9BB0-E14FE6087D53@vicor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 22, 2011 at 7:23 PM, Devin Teske <dteske@vicor.com> wrote:
>
> On Feb 22, 2011, at 12:57 PM, Peter Jeremy wrote:
>
>> On 2011-Feb-22 02:50:54 -0800, Devin Teske <dteske@vicor.com> 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. =A0Current disks are at the upper
>> limit of what MBR can be support (and that's after several revamps of
>> MBR). =A0Since GPT already provides a superior feature set without MBR's
>> limits, the next step will be to just drop MBR support. =A0And 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=VeTkHhwTO%2BTxvAphk=N3U5UE%2BS_t=ihPb=2t1>