On 9/14/25 23:04, Collin Funk wrote:
Hi,I mentioned this a few times in passing on other lists, but forgot to bring it up here. POSIX.1-2024 added the following change to many programs, using 'touch' as an example [1]: Austin Group Defect 251 is applied, encouraging implementations to disallow the creation of filenames containing any bytes that have the encoded value of a <newline> character. With the FUTURE DIRECTIONS having the following text: If this utility is directed to create a new directory entry that contains any bytes that have the encoded value of a <newline> character, implementations are encouraged to treat this as an error. A future version of this standard may require implementations to treat this as an error.
I'll document another deviation from posix in toybox then. Linux explicitly allows any characters in filenames except / and NUL:
https://yarchive.net/comp/linux/utf8.html
My personal opinion is that that we shouldn't restrict a user from creating a file with a name that their operating system and file system support.
Remember when posix yanked tar and replaced it with pax, and everybody completely ignored it?
Rob
