public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: Gentoo x86 AT <x86@gentoo.org>,
	release@gentoo.org, Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-dev] Gentoo i486 support
Date: Wed, 22 Aug 2018 15:27:51 -0500	[thread overview]
Message-ID: <CAAD4mYgqnTsYkGoh+0oPyfJNndeSZ9PYA_iu-B3dnw9GgHq3vA@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_=5T+TihqVhGT-s+WPEmi+jSn4qgYwFatq7fGi7CZ4D5g@mail.gmail.com>

On Wed, Aug 22, 2018 at 8:08 AM, Rich Freeman <rich0@gentoo.org> wrote:
> 1.  Museum hardware.  People have systems that are running simply
> BECAUSE they are old, not because they are cost-effective/etc.  I'm
> not sure I'd even lump used hardware into this category any longer, as
> I'm sure there are plenty of i686+ used PCs at rock-bottom prices
> already out there, and maintaining pre-Y2K hardware is going to be
> fairly painful.  For this use case i386 as the baseline makes a LOT of
> sense.
>
> 2.  Non-museum hardware.  People have x86 hardware because it is the
> most cost-effective solution for a task, and not merely because it is
> old.  IMO for this use case i686 makes a lot more sense as a baseline.
> However, I'm honestly not sure in this day and age what these use
> cases even are, unless it is something you can buy for $10 at a flea
> market.  Even if you're talking about a container running one
> application that only needs 500kB of RAM, is there really that much
> benefit to not building it for amd64?
>

I don't want to get very offtopic, but:

Even newer embedded i586 and i686 hardware isn't cost effective
considering power consumption. When considering power it often does
not even make sense to run donated hardware ~5 years old.

I don't think this should be used to completely drop support for older
platforms but it is probably the best argument to use to convince
people to get rid of their old hardware.


> The other argument for i386 would be that in Gentoo nobody is stuck
> with the defaults.  So, a default that works more widely as an entry
> point makes a lot of sense, since anybody can set CFLAGs and do an
> emerge -e world to get the benefits.  Then again, if we're talking
> about older but not ancient hardware that is still quite a bit of
> build time.
>

This is definitely in the spirit of Gentoo, but I think the most
concrete reason to support older platforms is they are demonstrably
more secure and people may be using them for that reason.

Cheers,
    R0b0t1


  parent reply	other threads:[~2018-08-22 20:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 12:26 [gentoo-dev] Gentoo i486 support Ben Kohler
2018-08-22 13:08 ` Rich Freeman
2018-08-22 13:23   ` Mart Raudsepp
2018-08-22 14:22   ` Peter Stuge
2018-08-22 20:27   ` R0b0t1 [this message]
2018-08-22 20:39     ` Rich Freeman
2018-08-25 11:07   ` Andrew Savchenko
2018-08-22 13:21 ` James Le Cuirot
2018-08-22 14:30 ` Mike Gilbert
2018-08-22 15:27   ` Thomas Deutschmann
2018-08-22 19:20 ` Matt Turner
2018-08-22 19:27   ` M. J. Everitt
2018-08-22 20:19 ` Richard Yao
2018-08-24 13:19 ` Kent Fredric
2018-08-24 13:57   ` Mike Gilbert
2018-08-24 14:13     ` Rich Freeman
2018-08-24 14:40       ` Kent Fredric

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAD4mYgqnTsYkGoh+0oPyfJNndeSZ9PYA_iu-B3dnw9GgHq3vA@mail.gmail.com \
    --to=r030t1@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=release@gentoo.org \
    --cc=rich0@gentoo.org \
    --cc=x86@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox