Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
actually match reality. In particular, _SC_GETPW_R_SIZE_MAX and
_SC_GETGR_R_SIZE_MAX were causing us problems with programs such
as libglib, since they were always returning -1, which is a bit
smaller than the actual passwd and group max buffer sizes.
-Erik
|
|
|
|
Fixed some minor issues plus (as I recall) one SUSv3 errno case.
|
|
Attached is a patch for a bug I found in libc/termios/ttyname.c.
Essentially the length of the buffer is calculated incorrectly in a
strncpy call and then the null terminator is placed on the byte after
the buffer.
This probably cause some very strange behavior on my system (it ended up
setting malloc's heapsize to zero) but may be innocuous on other systems.
|
|
when looking for a device match, and instead keep looking till
we find the correct device.
|
|
uniquely identify a file, contrary to SuSv3, so we cannot be quite so
precise as to require an exact match. Settle for something less...
Grumble...
-Erik
|
|
-Erik
|
|
-Erik
|
|
Stefan Soucek <ssoucek@coactive.com>
|
|
|
|
This required we use _LIBC instead of __LIBC__ to be consistent with glibc.
This had some sideffects in sys/syscalls.h. While fixing things, I made
everything use __set_errno() for (eventual) thread support.
-Erik
|
|
|
|
-Erik
|
|
|