From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] FQA update
Date: Sat, 1 Apr 2023 21:52:13 +0100 [thread overview]
Message-ID: <AE4E042B-5EE9-418D-AFF3-742EAF5F0E83@quintile.net> (raw)
In-Reply-To: <ZCiTpOWtrshGpMSD@wopr>
another point of view:
there may be many better computers than the raspberry pi, they do work and have been a good choice for me (running plan9) for about 5 years now, and still are.
-Steve
> On 1 Apr 2023, at 9:29 pm, Kurt H Maier <khm@sciops.net> wrote:
>
> On Fri, Mar 31, 2023 at 02:50:44PM -0400, sl@stanleylieber.com wrote:
>>> The fact now the system is installing mainly on amd64 (in the case of
>>> virtualization) and on arm (in the case of RPi). Therefore, IMHO,
>>> there need to set accent on these architectures, and the rest ones are
>>> mention as options.
>>
>> well, maybe. if we arrive at some agreement on changing the "default"
>> architecture, fine; but to my knowledge nobody has established that
>> yet. 386 was always the starting point. i appreciate that owners of
>> amd64 systems often have no interest in looking back, but we do still
>> have a significant number of 386 users, and the amd64 port in fact
>> still builds code out of the 386 kernel. a significant number of drivers
>> are still disabled (by default)in the amd64 kernel.
>>
>> i am of course happy to revisit this if devs have some preference
>> to the contrary.
>
> In addition the raspberry pi is a trash computer and I'm not comfortable
> recommending them even implicitly by emphasising them in documentation.
> People should try really hard not to use them even when they ARE
> available, which is not any more.
>
> khm
next prev parent reply other threads:[~2023-04-01 20:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 5:37 Yury Chumak
2023-03-17 19:52 ` Tobias Heinicke
2023-03-18 3:37 ` sl
2023-03-29 3:32 ` sl
2023-03-29 11:09 ` Yury Chumak
2023-03-31 18:50 ` sl
2023-04-01 20:27 ` Kurt H Maier
2023-04-01 20:52 ` Steve Simon [this message]
2023-04-01 21:29 ` ori
2023-04-02 7:10 ` Kurt H Maier
2023-04-02 9:40 ` ooga
2023-04-02 11:29 ` Philip Silva
2023-04-02 14:49 ` Stanley Lieber
2023-04-02 17:54 ` Philip Silva
2023-04-02 18:03 ` Philip Silva
2023-04-02 19:21 ` hiro
2023-04-06 14:11 ` cinap_lenrek
2023-04-06 14:19 ` cinap_lenrek
2023-04-06 16:04 ` Stanley Lieber
2023-04-02 19:59 ` Kurt H Maier
2023-04-03 10:22 ` chris
2023-04-03 11:50 ` chris
2023-04-03 18:09 ` adventures in9
2023-04-03 19:13 ` Stanley Lieber
2023-04-03 21:44 ` sirjofri
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=AE4E042B-5EE9-418D-AFF3-742EAF5F0E83@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).