[KLUG Programming] Pthreads problem
Peter Buxton
programming@kalamazoolinux.org
Mon, 5 Jan 2004 08:52:09 -0500
On Sat, Jan 03, 2004 at 06:38:24AM -0500, Robert G. Brown was only escaped
alone to tell thee:
> Hey, maybe they exist, but I'm certainly not in touch with 'em, and it
> doesn't really matter to me if they win the fight or not. That's one
> of the very nice things about this technology; one can take reasonable
> (and sometimes trivial) steps to protect oneself against changes
> others may introduce, and that actually increases the freedom everyone
> has.
Then respect mine. And that means freedom from harassment.
> I'm not on any soapbox to obsolete anything,
But you *are* on a soapbox.
> and any such characterization of what I've said is neither accurate or
> correct. I simply believe that there's a better way to write scripts
> that are going to be in production, where other values (like ease of
> maintenance) become important.
Really? What about this:
> It seems odd and perhaps counterproductive that you are making a case
> for LESS abstraction where it can really help. It is probably a really
> good idea to use sysctl in production against the day that echo into
> /proc is deprecated, I wouldn't want to convert and test all that only
> when the time comes.
"against the day that echo into /proc is deprecated". Hey, Bob, where
are all your modifiers? Why "when" not "if"? Did you use a bunch of
diacriticals in your modifiers that rendered them invisible in mutt?
> > Tracking new values and obsoleting old ones, and verifying
> > correct/incorrect/buggy values, is their bete noir.
>
> It may well be, as far as maintaining the integrity of kernel space
> is concerned, but how does the initiator of a setting find out that
> an error as been detected, or a setting rejected, with an interface
> like echo?
Nice strawman, Bob. You'll notice, should you take the time to reread my
post, that I said this fictional system management app SHOULD use
sysctl. Are my posts unclear?
> Maybe you only intend to use it for online hacking; perhaps it's time
> to get into the habit of using sysctl there, too...
Another thing, Bob. One shouldn't use other-directed language. You sound
critical when you don't frame your experiences entirely in self-directed
language, e.g.: "I do X to avoid Y." And one should realize that
third-person pronouns don't help either.
--
Sometimes, the best medical care you can give someone in
the field is laying down a good line of suppressive fire.