Comment by jart
4 years ago
> Of course the problem is that it needs some cooperation between libc and the kernel.
You may have missed that our new pledge() impl is hosted in the Cosmopolitan Libc repository. So we've got cooperation. Therefore it'd help to clarify when you say this project won't get us there, that you're only speaking for glibc. pledge.com works fine with everything else like Musl and Cosmo Libc. It even works with glibc most of the time. One can't reasonably expect cosmo to need to support glibc before being able to support itself. We've learned today that folks want this. So the Glibc dev team should be doing more to help us. What I fear is that they're focused on different things.
Like i said: it needs cooperation with both kernel and libc.
You have libc, which does mean it's in sync with dynamically compiled binaries against your libc, with the other drawbacks I mentioned too.
And you need kernel maintainer cooperation too to "bring pledge to Linux".