From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] FQA update
Date: Fri, 31 Mar 2023 14:50:44 -0400 [thread overview]
Message-ID: <0B825421E44F1C59271E3F6E7F150095@gaff.inri.net> (raw)
In-Reply-To: <CAOe=0dcWzTP41wHp3SeWmch4uP13ifG1RnXsz0DOHo2bVFGijw@mail.gmail.com>
> 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.
> Found some typo in link code in section '8.4.9.1 - Tinc'
this is fixed now.
thanks!
sl
next prev parent reply other threads:[~2023-03-31 18: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 [this message]
2023-04-01 20:27 ` Kurt H Maier
2023-04-01 20:52 ` Steve Simon
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=0B825421E44F1C59271E3F6E7F150095@gaff.inri.net \
--to=sl@stanleylieber.com \
--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).