Re: Selection of roadmap for i386 platform End-of-Life (EOL)

Loganaden Velvindron <[email protected]>
Newsgroups gmane.os.dragonfly-bsd.kernel
Message-ID <CAOp4FwTcmF0LDgAgdhwf2+3vUnMop3t77b+a8YzN0ozXLo=Tkg@mail.gmail.com>
No NX-bit on i386.

Long live x64.




On Thu, Apr 18, 2013 at 6:01 AM, Justin Sherrill
<[email protected]>wrote:

> On Wed, Apr 17, 2013 at 7:15 AM, John Marino <[email protected]>
> wrote:
>
> > 1) Agreement on the EOL date (or Release if it's pegged to a release)
>
> I'd rather peg to a release; I'd assume we'd want to truncate i386 at
> the time of a release, instead of somewhere between two releases.
> Since release dates can be a little floaty, that's easier to manage.
>
> > 2) A declaration of which road map will be used (method #1 or #2)
>
> I don't know what the usage ratio of i386-only machines is at this
> point; I'd feel more confident if I knew the impact, but there's no
> way to find that out.
>
> #2 (Or Sam's #3) appeals to me just because I've wanted something that
> could be called a long-term support release for a while.  A
> disadvantage of x86_64 is no linuxlator support, but keeping i386
> around isn't going to solve that problem.
>



-- 
This message is strictly personal and the opinions expressed do not
represent those of my employers, either past or present.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.