Harry Weaver
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
_______________________________________________
freebsd-...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
Basically an image made up of dots.
> I run FreeBSD and NetBSD, using GPT and no traditional BSD disklabels
> that would drive me crazy. I find OpenBSD not compatible on my
> system.
>
> LiveUSB OpenBSD from liveusb-openbsd.sourceforge.net can't read or
> recognize my GPT-partitioned hard drive, and didn't recognize my
> Realtek Ethernet chip, 8111E/8168, haven't fully tested with wi-fi
> since I copied necessary firmware using FreeBSD.
>
> I usually use Super Grub2 Disk, available on earlier versions of the
> System Rescue CD written to USB stick, but am trying to move over to
> UEFI boot, need to more deeply study what I can do at FreeBSD loader
> prompt or NetBSD boot prompt.
>
> What/where is the gptboot you might want to install? Is it in FreeBSD
> ports, base system, or somewhere else? I notice FreeBSD >= 12.x has
> efibootmgr in base system, not avaliable in NetBSD base system or
> pkgsrc.
>
> I notice /boot/gptboot in FreeBSD base system, that would not be a
> separate installation.
Apparently it handles booting as part of the base install, and
automatically passes off to the bootloader, but if you hit any key
within 3 seconds, apparently it defaults to interactive mode and you can
select any partition to boot from. So, if it recognises the partitions
of other installations, I thought that might be one way of doing it if
you had multi-installs.
Cheers!
Harry Weaver
>
> Tom
Those look correct here -- ascii-like debian logo -- even in console (vt
with terminus font), are you using non-UTF-8-capable MUA yet?
This will be in a small tower with 4 different drives, each with a
different OS on each one.
I am just wondering if there's a bootable partition on each one, is
there a boot-manager that will pick up each one and give me a choice as
to which one to boot?
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
Great!
Thanks for that.
Harry Weaver.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
Looks like there is still more than one 2-to-1 byte mangling
involved, possibly crossing encoding borders. If you have
further questions, ask Senior Lampampatilde-Ampamsuppez who
lives in Schlatildefracterstrasse, Berlin... ;-)
The original message declares UTF-8 correctly, and also _uses_
UFT-8 encoded symbols in the signature. The following drawing
should be visible:
⢀⣴⠾⠻⢶⣦
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋
⠈⠳⣄
If there is some back-and-forth nonsense ISO-8859-1 <-> UTF-8
and maybe some HTML guessing (some web mailers tend to do this
in order to "help"), useless multibyte sequences appear that
do no longer correspond to the originally used symbols.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
> On Mon, 16 Nov 2020 09:45:01 +0000, Thomas Mueller wrote:
> > > > > Harry Weaver
> > ⢀⣴⠾⠻⢶⣦⠀
> > ⣾â ⢠⠒⠀⣿⡠Debian - The universal operating system
> > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> > â ˆ
> > which is not what I'm running now.
>
> Looks like there is still more than one 2-to-1 byte mangling
> involved, possibly crossing encoding borders. ...
What you saw was misleading, and has nothing to do with why Thomas
Mueller didn't see the Debian thing.
His client likely just has broken or missing UTF-8 and/or MIME support.
There's no excuse for that in 2020.
> The original message declares UTF-8 correctly, and also _uses_
> UFT-8 encoded symbols in the signature. The following drawing
> should be visible:
>
> ⢀⣴⠾⠻⢶⣦
> ⣾⠁⢠⠒⠀⣿⡁
> ⢿⡄⠘⠷⠚⠋
> ⠈⠳⣄
That was visible to me in the post that you quoted from.
What happened was that Thomas Mueller pasted UTF-8 into a text/plain
body without an explicit character set. The relevant RFC says that this
should default to US-ASCII, which means that byte values above 7f are
undefined. This include all of the UTF-8 Braille.
My client, Claws Mail, identified the text as UTF-8 and displayed it as
such. UTF-8 can be identified very reliably is there are enough
multibyte characters.
Your client, Sylpheed, appears to have assumed the undefined bytes were
in ISO 8859-1, a common fallback. On replying, Sylpheed then converted
the quoted bogus text to UTF-8 which hopefully this reply preserves.
There may be a bit more to this, but any remaining weirdness is most
likely caused by Sylpheed. Note that some of the whitespace in the
quoted garbage above is from A0 bytes in the original UTF-8 being
treated as a "no break space".