This message was in the clear, although I see it was: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
so I wondered if a non 7-bit char had sneaked in there that caused TB to switch to base64 for the troublesome message. I couldn't see one by eyeballing it though.
tin interpreted the original with no problems. I'd guess the Fido Usenet gateway doesn't handle base64 messages correctly.
Theo
[snip]
I'm 77+, and now I've forgotten why I mentioned that :-(
Oh yes - I am currently using Ubuntu on a RPi4B+ 8Gb SSD, and I had no problems installing a Server, then a Ubuntu Desktop, and it works perfectly :-)
The Pi build of PiOS _IS_ basically Debian - with (AFAIK) all the packages available that are available in Debian - which is pretty much all major open sources software and lots and lots of minor OS software as well. Just because it isn't installed in the base OS doesn't mean it can't installed use apt aptitude or ap-get or the various GUI front ends.
I'd be interested in any software in the standard RedHat respositories that isn't available in the Debian Repo's.
The advantage of using the PiOS is that it is built to work on the Pi's.
32bit PiOS works across all versions of Pi's. If an installation of PiOS isn't working on a Pi, then either the Pi is broken (it happens I had one that wouldn't boot - got it replaced) or you messed up the software post installation. I keep a fairly upto date PiOSlite SD card to test new PI's, before trying it with anything else.In that case put PiOS on it - install the extra packages you need, uninstall those you don't. And go to the RPI forums for support.In my opinion there fairly good at supporting PiOS uses.
[PiOS lite is PiOS with no graphical stuff but everything you need load what ever you want. It's probably a decent start for a headless server.]64-bit...
Release 22.10(Kinetic Kudo) 64-bit Kernal Linux 5.19.0-1009-raspi aarch64 MATE 41.26.0
I also had a trouble free installation experience of Ubunbtu 20.04 LTS server on a Pi4 8 GB on a SDcard
I forgot to mention it is
64-bit00000070 74 69 6e 67 20 63 6c 61 6e 67 20 6f 6e 20 74 68 |ting clang on th| 00000080 65 20 50 69 34 20 3f 0d 0a 3e 20 0d 0a 3e 20 44 |e Pi4 ?..> ..> D| 00000090 6f 65 73 0d 0a 3e 20 20 c2 a0 c2 a0 c2 a0 c2 a0 |oes..> ........| ^^^^^^^^^^^^^^^^^^^^^^^ 000000a0 61 70 74 20 6c 69 73 74 20 63 6c 61 6e 67 0d 0a |apt list clang..|
These are the Unicode NO-BREAK-SPACE character, replacing the tab in Brian’s post.
My spam filter drops base64-encoded messages since they are usually binaries.
[snip]
Well spotted!
---druck
Have something to add? Share your thoughts — no account required.
Ask the community — no account required