It doesn't, as far as I can tell. That implementation comes from OpenBSD's
who.
Is the utmp file guaranteed to be machine endian? This patch seems to imply
that.
*environ = NULL;
The linux manpage suggests 'environ = NULL'. Is BSD different in that regard?
I would like to see sbase compile
On Thu, Jul 18, 2013 at 11:31 AM, Galos, David
galos...@students.rowan.edu wrote:
It doesn't, as far as I can tell. That implementation comes from OpenBSD's
who.
Is the utmp file guaranteed to be machine endian?
OpenBSD assumes it is. And on Linux, man 5 utmp claims: The file
format is
I have applied this patch. OpenBSD users rejoice, you
too can finally experience sbase!
On Fri, Jul 12, 2013 at 5:36 PM, Galos, David
galos...@students.rowan.edu wrote:
OpenBSD doesn't have utmpx.h or clearenv.
Does it also not have getutent?
It doesn't, as far as I can tell. That implementation comes from OpenBSD's who.
OpenBSD doesn't have utmpx.h or clearenv. Also, the dependency
$(BIN): util.a seems to shadow the implicit build rule in BSD make,
resulting in nothing past util.a getting built. The patch includes a
rather stupid workaround for this. (Less stupid solutions welcome ---
it'd be simple to specify
OpenBSD doesn't have utmpx.h or clearenv.
Does it also not have getutent? Replacing clearenv with
environ=NULL is fine, though.
it'd be simple to specify with a .for, but then it'd be
BSD-make--specific, and I don't feel like figuring out cross-platform
makefiles.)
Good, we want nothing to do
