From: Finn Thain <fthain@telegraphics.com.au>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Gerhard Pircher <gerhard_pircher@gmx.net>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Sparc kernel list <sparclinux@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Old platforms never die, was Re: Old platforms: bring out your dead
Date: Wed, 13 Jan 2021 11:12:06 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.23.453.2101131035500.6@nippy.intranet> (raw)
In-Reply-To: <cb5a2e11-d423-96ec-3d43-3568a109e37f@physik.fu-berlin.de>
On Tue, 12 Jan 2021, John Paul Adrian Glaubitz wrote:
>
> There has to be a healthy balance between hobbyist and commercial use.
>
Yes, both of those, and everything in-between, including for-profit
businesses that serve mostly hobbyists. Also start-up companies that may
never be commercially viable (which is most of them).
And don't forget government and non-government organisations,
not-for-profit organisations, charities, etc.
> I understand that from a commercial point of view, it doesn't make much
> sense to run Linux on a 30-year-old computer.
It ain't necessarily so. I would be surprised if there are no Linux VMs
running on old corporate mainframes right now. But the age of the hardware
is largely irrelevant.
If you're a museum interested in cultural artifacts from decades past, or
if you're a business doing data recovery, you're going to need to operate
those platforms.
Once removed from mainline Linux, a port becomes basically frozen, and may
not be compatible with future emulators, which are a moving target. I say
that because last year I fixed bugs in Linux/m68k that made it incomatible
with recent QEMU releases (it was only compatible with old QEMU releases).
next prev parent reply other threads:[~2021-01-13 0:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK8P3a2VW8T+yYUG1pn1yR-5eU4jJXe1+M_ot6DAvfr2KyXCzQ@mail.gmail.com>
2021-01-10 17:35 ` Old platforms: bring out your dead John Paul Adrian Glaubitz
2021-01-10 21:46 ` Sam Ravnborg
2021-01-11 8:05 ` John Paul Adrian Glaubitz
2021-01-11 14:55 ` chase rayfield
2021-01-12 0:26 ` Rob Landley
2021-01-12 0:50 ` chase rayfield
2021-01-12 14:37 ` John Paul Adrian Glaubitz
2021-01-11 18:09 ` Rob Landley
2021-01-11 15:04 ` Gerhard Pircher
2021-01-12 14:44 ` John Paul Adrian Glaubitz
2021-01-12 22:46 ` Linus Walleij
2021-01-13 8:09 ` Rob Landley
2021-01-13 8:21 ` Geert Uytterhoeven
2021-01-13 13:25 ` Rob Landley
2021-01-13 12:02 ` Andy Shevchenko
2021-01-13 8:15 ` Geert Uytterhoeven
2021-01-13 10:39 ` Arnd Bergmann
2021-01-14 3:54 ` New platforms: bring out your dead, was " Finn Thain
2021-01-14 9:41 ` John Paul Adrian Glaubitz
2021-01-14 9:48 ` Geert Uytterhoeven
2021-01-14 21:21 ` Arnd Bergmann
2021-01-14 22:54 ` Undesirable code, was Re: Old platforms etc Finn Thain
2021-01-14 23:09 ` Old platforms: bring out your dead Max Filippov
2021-01-15 8:31 ` Arnd Bergmann
2021-01-13 0:12 ` Finn Thain [this message]
2021-01-16 6:54 ` Old platforms never die, was " Rob Landley
2021-01-16 23:22 ` Finn Thain
2021-01-13 11:47 ` Andy Shevchenko
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=alpine.LNX.2.23.453.2101131035500.6@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=arnd@arndb.de \
--cc=gerhard_pircher@gmx.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=sparclinux@vger.kernel.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