[KLUG Programming] Pthreads problem

[Adam Williams]

> I forgot this in my reply to Adam's post:
> > > If you think echo and /proc are the sources of that, I suggest
> > > you're
> > > high.  Cathedral v. bazaar: changes in AIX pass through committees
> > > which ensure that important commercial apps won't have to change too
> > > quickly.
> > Well, then in this case the Cathedral wins hands down; 'cause those
> > priests got game.
> So, because "IBM ensures AIX changes very slowly", "echo is bad." 

Er, no.  It was derived from a sub-thread that management of a Linux
system is currently in very much a state of flux.  We were talking about
APIs/Abstratction and "all that jazz".  Since AIX funnels everything
through a set of commands (nfso, no, blah blah...) the underlying
operation system can change radically (it has in the past, from 4.2.x ->
5L especially) and management of the system continues more or less
unaltered (one can't of course abstract and future-proof completely, not
without a palantir anyway, and not even IBM has that technology).

Admittedly sysctl is a sad and far cry from "real" tuning tools like
nfso, no, blah blah... but it helps a little.  Maybe it is like buying
flood insurance while living in a desert; but I never rule anything out
given my penchant for calamity.