[PATCH] simplify ulimit implementation

Pino Toscano toscano.pino@tiscali.it
Tue Jan 15 18:17:00 GMT 2013


Hi,

Alle lunedì 19 novembre 2012, Roland McGrath ha scritto:
> I don't think losing __UL_GETMAXBRK is really a problem.  The reason
> for removing it was not specific to Linux, just to the
> implementation being in a shared library.  It could be implemented
> in a shared library, at the cost of a GOT reloc for _etext to get
> the main executable's value (or conversely, perhaps some grovelling
> in dynamic linker data structures for the shared case).  But given
> that the current implementation usable on the Hurd will yield
> utterly useless values, the case for having it at all is
> inordinately weak.

OK.

Attached there are the two patches of the ulimit reorganization, as you 
suggested in a previous email:
1) move the linux implementation as posix (including limits.h)
2) remove the bsd implementation

Thanks,
-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-ulimit-1.diff
Type: text/x-patch
Size: 5454 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20130115/d703225f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-ulimit-2.diff
Type: text/x-patch
Size: 3005 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20130115/d703225f/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20130115/d703225f/attachment.sig>


More information about the Libc-alpha mailing list