wicked witch of the unix on Nostr: honestly unless i missed something, i really don't get the lack of PATH_MAX in hurd ...
honestly unless i missed something, i really don't get the lack of PATH_MAX in hurd
like, sure, the idea makes some sense, there's no inherent limit to a file path, any limit can be worked around by dirfds and relative paths, but the point of PATH_MAX is not a absolute limit, but a relative one!
a limit applied to syscalls because you really don't want to accept any arbitrary length in a input string and hang there parsing a 5 gigabyte string from a malicious program or smth
so either gnu hurd would have it's translation server hang on gigantic paths, or it has a PATH_MAX but pretends it doesn't
Published at
2026-06-19 19:36:37 UTCEvent JSON
{
"id": "26c681dd1ffd26794f49ad34aec51b4cd67ac003615c2b34b2c06c5ece9a652f",
"pubkey": "4ebc018b65a1b352f90f937be79b5c338651f1528960889fa64caa94be982f8a",
"created_at": 1781897797,
"kind": 1,
"tags": [
[
"proxy",
"https://social.vlhl.dev/objects/28aa7da6-d440-458f-956f-34cc9a470ac4",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "honestly unless i missed something, i really don't get the lack of PATH_MAX in hurd\n\nlike, sure, the idea makes some sense, there's no inherent limit to a file path, any limit can be worked around by dirfds and relative paths, but the point of PATH_MAX is not a absolute limit, but a relative one!\n\na limit applied to syscalls because you really don't want to accept any arbitrary length in a input string and hang there parsing a 5 gigabyte string from a malicious program or smth\n\nso either gnu hurd would have it's translation server hang on gigantic paths, or it has a PATH_MAX but pretends it doesn't",
"sig": "5404298d009a8f61b65ecd968be0d0cffde9000030db88b6779eebeb9d0e3681a4e25a89aa440a5380d24bbe02f535ba55caad24d34b0e8f5ec4cd632b26f032"
}