Hello everyone,
Years ago I made a suggestion here about this, now that I am a little
less ignorant in C I dared with the patches below, they add a '-e'
option to mail(1) to pass a Content-Transfer-Encoding on the command
line. First you convert the text in "message.txt" to quoted-printable
or ba
deroff chokes when given lines > 2048 bytes, and produces non-deterministic
output on little endian archs.
Reproducer:
$ jot -s '' -b blah 513 > /tmp/blah
$ for i in 1 2 3 4 ; do deroff /tmp/blah | md5 ; done
2d8f4eebd61ed2a07101419169fc9997
ae19be78a09e6b371787003bf76f5937
82b4bcea8510605bea2723
On Tue, Sep 19, 2023 at 09:48:25AM -0300, Crystal Kolipe wrote:
> deroff chokes when given lines > 2048 bytes, and produces non-deterministic
> output on little endian archs.
>
> Reproducer:
>
> $ jot -s '' -b blah 513 > /tmp/blah
> $ for i in 1 2 3 4 ; do deroff /tmp/blah | md5 ; done
> 2d8f4eeb
I'd forgotten that adding a "charset" specification to the Content-Type
header is also needed. In the *new* set of patches below, besides I
corrected some other errors, I added a '-y' option to specify utf-8
character set:
$ mail -s Hello -e quoted-printable -y "text/plain;charset=utf-8" \
Hi Walter,
i did not look closely at the patch yet, and i did not dig for standards
documents, which one should almost certainly do before committing such
a patch unless one knows all the relevant standards by heart (which i
do not), so i'm not saying this must be done differently, but instead
i a
On Tue, Sep 19, 2023 at 05:48:01PM +0200, Ingo Schwarze wrote:
> Hi Walter,
>
> i did not look closely at the patch yet, and i did not dig for standards
> documents, which one should almost certainly do before committing such
> a patch unless one knows all the relevant standards by heart (which i
Ingo, that's a bit cynical.
As long as the process is slow, step by step, adding one or two manuals at
a time, and focusing on being ACCURATE, then it will be good.
It would be wrong to add inaccurate pages. A lack of documentation is slightly
better than inaccurate documentation.
So if you re
--- Original Message ---
On Tuesday, September 19th, 2023 at 7:03 PM, Theo de Raadt
wrote:
>
>
> Ingo, that's a bit cynical.
>
>
> As long as the process is slow, step by step, adding one or two manuals at
> a time, and focusing on being ACCURATE, then it will be good.
>
> It w
powerpc64 already has bio(4) and bioctl(8) like macppc, but lacks
softriad(4), which looks like an oversight.
Neither architecture has boot support, but they still ought to be able
to access softraid volumes during install/upgrade.
distrib/powerpc64/ramdisk builds and fits; I did not have a free
On Sun, Sep 03, 2023 at 09:21:18AM +0200, Otto Moerbeek wrote:
> Hello,
>
> I'm seeing some reports of "write after free" reported by malloc by
> peolpe running current. Malloc has become more strict since begining
> of June. Let me explain:
>
> Small allocations share a page. e.g. a 4k page wi
10 matches
Mail list logo
