On Tue, 19 Sep 2023 21:48:57 +
Klemens Nanni wrote:
> distrib/powerpc64/ramdisk builds and fits; I did not have a free disk
> (partition) to run-test, but completing the config should be fine.
I moved my /usr/xobj filesystem to a softraid CONCAT. The old bsd.rd
failed to mount it, the new
ypldap currently packs all the user and group lines into contiguous blocks
of memory so it can move from one entry to the next by pointer arithmetic.
This doesn't make much sense because the entries are also in red black trees
(that's how it looks up the entry in the first place) and RB_NEXT() is
Steffen Nurpmeso wrote in
<20230920214009.w5mrf%stef...@sdaoden.eu>:
|Ingo Schwarze wrote in
| :
| ...
||I just checked - even though i'm using the higer-level mutt(1) MUA
||most of the time and even though the shell i'm starting mutt(1) from
||has LC_CTYPE=C.UTF-8 set on that particular
Ingo Schwarze wrote in
:
...
|I just checked - even though i'm using the higer-level mutt(1) MUA
|most of the time and even though the shell i'm starting mutt(1) from
|has LC_CTYPE=C.UTF-8 set on that particular machine, the last sixteen
|mails i sent all contained the explicit header
|
|
Hi, Ingo
• Ingo Schwarze [2023-09-20 13:55]:
Hi Kirill,
Kirill Miazine wrote on Wed, Sep 20, 2023 at 12:52:52PM +0200:
you may not even need -m, and instead inspect LC_CTYPE environment
variable and add appropriate headers for UTF-8. according to locale(1),
LC_CTYPE may be set to indicate
On Wed, Sep 20, 2023 at 07:44:12PM +0200, Walter Alejandro Iglesias wrote:
> And this new idea simplifies all to this:
In case anyone else is worried. Crystal Kolipe already pointed me out
that a better UTF-8 checking is needed, I know, I'll get to that
tomorrow.
On Wed, Sep 20, 2023 at 06:13:10PM +0200, Walter Alejandro Iglesias wrote:
> Now I was investigating exactly that :-) (like Mutt also does): to make
> mail(1) automatically set the appropiate MIME headers when it detects
> any utf8 characters in the body text. So, you don't like this idea?
>
Errata patches for npppd have been released for OpenBSD 7.2 and 7.3.
Binary updates for the amd64, arm64 and i386 platform are available
via the syspatch utility. Source code patches can be found on the
respective errata page:
https://www.openbsd.org/errata72.html
On Wed, Sep 20, 2023 at 05:30:08PM +0200, Ingo Schwarze wrote:
> Hi,
>
> i checked the following points:
>
> * Even though RFC 2049 section 2 bullet point 1 only *requires*
>MIME-conformant MUAs to always write the header "MIME-Version:
>1.0" - and mail(1) is most certainly not
Hi,
i checked the following points:
* Even though RFC 2049 section 2 bullet point 1 only *requires*
MIME-conformant MUAs to always write the header "MIME-Version:
1.0" - and mail(1) is most certainly not MIME-conformant - RFC 2049
section 2 bullet point 8 explicitly *recommends* that
On Wed, Sep 20, 2023 at 03:02:27PM +0200, Matthieu Herrb wrote:
> On Wed, Sep 20, 2023 at 08:08:23AM +0200, Otto Moerbeek wrote:
> >
> > The other, a write after free that crashed the X server when running
> > picard was diagnosed by me. This one was a bit nasty, as it required
> >
On Wed, Sep 20, 2023 at 08:08:23AM +0200, Otto Moerbeek wrote:
>
> The other, a write after free that crashed the X server when running
> picard was diagnosed by me. This one was a bit nasty, as it required
> instrumenting malloc to print some extra info to find the root cause.
>
> The bug is
Hi Kirill,
Kirill Miazine wrote on Wed, Sep 20, 2023 at 12:52:52PM +0200:
> you may not even need -m, and instead inspect LC_CTYPE environment
> variable and add appropriate headers for UTF-8. according to locale(1),
> LC_CTYPE may be set to indicate UTF-8:
>
> If the value of LC_CTYPE ends
On Wed, Sep 20, 2023 at 10:30:31AM +, Klemens Nanni wrote:
> Except for mandoc(1) and other manuals where "utf8" is a literal keyword,
> our manuals consistently use upper-case UTF-8 for what is an abbreviation,
> so this should do as wlel.
>
> > .It Fl n
> > Inhibits reading
> > .Pa
• Walter Alejandro Iglesias [2023-09-20 12:21]:
Hi Ingo,
I did what you suggested me, I investigated a bit and you were right in
that the MIME-Version header was necessary. This new set of patches
add the following headers (hardcoded as you suggested me):
MIME-Version: 1.0
Content-Type:
Hi Ingo,
I did what you suggested me, I investigated a bit and you were right in
that the MIME-Version header was necessary. This new set of patches
add the following headers (hardcoded as you suggested me):
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
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
17 matches
Mail list logo
