Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #210194

Re: Does 32-bit x86 support (aka [multilib] ) have a future with Debian after Buster

Show all headers | View raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 21/6/19 11:44 pm, Felix Miata wrote:
> Andrew McGlashan composed on 2019-06-21 20:03 (UTC+1000):
> 
>> Most, if not all 32 bit arch machines are probably going to
>> consume far more energy than newer machines of far greater
>> capability.  That is, it probably doesn't make any financial
>> sense to continue running an old 32 bit machine.
> 
> Retiring a working old PC requires an investment of not just money,
> but also time, and possibly retraining. The old PC is a sunk cost,
> and its user(s) may have no need for greater capability. Periodic
> energy cost is probably trivial by comparison, so even if a new PC
> uses a third or less energy than the old, the investment could take
> more than a PC's lifetime to recover, assuming the required funding
> of the cost was even available to make. e.g. $6.00/month for energy
> to continue vs. $2.00 after investment nets only $48/year. A cheap
> replacement, $500, would take more than 10 years to be paid for at
> that rate, not counting anything for the time value of the money
> invested, which could easily more than double the required time to
> recover. IOW, it doesn't make any sense on a purely financial basis
> to replace a working PC.

Sure, it doesn't make sense for every case, but there are often other
factors; in time one of those factors will be lack of support for
i386, even if it isn't Debian itself.

And there are other reasons, power usage is but one; sometimes just
the risk of an older box dying and having no replacement is a more
important consideration.

Cheers
A.
-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCXQznPwAKCRCoFmvLt+/i
+9a7AQDFcJg2omkpeEFr5bfeiaOSy0Jw7z8Z0zBqrWm3aHoZjgEAyey1qq5wOHSK
skAcVTi0DeqGqgGUPPmGOoL345kFuaU=
=68ey
-----END PGP SIGNATURE-----

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Does 32-bit x86 support (aka [multilib] ) have a future with Debian  after Buster? Matthew Crews <mailinglists@mattcrews.com> - 2019-06-18 23:40 +0200
  Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster? Richard Hector <richard@walnut.gen.nz> - 2019-06-20 00:40 +0200
  Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Lazar Tadić <lazar.tadic34@gmail.com> - 2019-06-20 00:50 +0200
    Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Matthew Crews <mailinglists@mattcrews.com> - 2019-06-20 01:10 +0200
      Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Reco <recoverym4n@enotuniq.net> - 2019-06-20 08:30 +0200
        Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2019-06-21 12:10 +0200
          Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Matthew Crews <mailinglists@mattcrews.com> - 2019-06-21 13:50 +0200
          Re: Does 32-bit x86 support (aka [multilib] ) have a future with Debian after Buster Dekks Herton <dekkzz78@gmail.com> - 2019-06-21 15:20 +0200
          Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Felix Miata <mrmazda@earthlink.net> - 2019-06-21 15:50 +0200
            Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster <tomas@tuxteam.de> - 2019-06-21 16:10 +0200
            Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2019-06-21 16:20 +0200
              Re: Does 32-bit x86 support (aka [multilib] ) have a future with  Debian after Buster Felix Miata <mrmazda@earthlink.net> - 2019-06-21 16:40 +0200

csiph-web