See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389#c42
for an example of loss of control of a system via the extensive
OOM activity that resulted.
The problem has been observed on both amd64 and aarch64: the
original report was for amd64 and my activity was for aarch64.
The original repo
On Sat, Nov 2, 2024, 1:06 PM void wrote:
> On Sat, Nov 02, 2024 at 10:42:16AM -0600, Warner Losh wrote:
> >OK. This is because the text-only boot loader only supports cons25-level
> of
> >character set (which is ASCII + upper page IBMPC)
> >rather than Unicode. There's 0 chance that unicode suppo
On Sat, Nov 02, 2024 at 10:42:16AM -0600, Warner Losh wrote:
OK. This is because the text-only boot loader only supports cons25-level of
character set (which is ASCII + upper page IBMPC)
rather than Unicode. There's 0 chance that unicode support will be added to
that boot loader (you need the gra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The first BETA build of the 14.2-RELEASE release cycle is now available.
Installation images are available for:
o 14.2-BETA1 amd64 GENERIC
o 14.2-BETA1 i386 GENERIC
o 14.2-BETA1 powerpc GENERIC
o 14.2-BETA1 powerpc64 GENERIC64
o 14.2-BETA1 powerpc6
OK. This is because the text-only boot loader only supports cons25-level of
character set (which is ASCII + upper page IBMPC)
rather than Unicode. There's 0 chance that unicode support will be added to
that boot loader (you need the graphics based
one), so I used graphics vs not to know when to use
