On Tue, Sep 16, 2025 at 1:28 PM Rob Landley <r...@landley.net> wrote: > > On 9/16/25 10:25, enh wrote: > > On Tue, Sep 16, 2025 at 11:04 AM Lawrence Velázquez <v...@larryv.me> wrote: > >> > >> On Tue, Sep 16, 2025, at 1:23 AM, Collin Funk wrote: > >>> If there is a discussion on the POSIX bug tracker to make it a > >>> requirement, we can revisit it then, and likely voice objections there. > >> > >> I think your input would hold some weight, as the suggestion was > >> largely driven by one individual who tends to view the standard as > >> prescriptive rather than descriptive. The initial proposal was > >> rather more radical. > > > > yeah, there's been a lot of that kind of thing with POSIX lately, > > which seems quite a radical departure from its historical > > standardization of existing practice. > > > > this one was https://www.austingroupbugs.net/view.php?id=251 for > > anyone curious... > > A way that iphone or Windows or Amazon Fire could generate filenames > Linux or stock Android can't handle couldn't _possibly_ be abused as a > proprietary advantage by a large corporation. Yeah, that one was thought > through.
eh, android already has trouble because java uses utf16 and the linux kernel uses arbitrary byte sequences, so you easily get into situations where what's on disk can't be represented above libc. > Rob
