> "As a project."  You seem to be forgetting that this "project" would
> not be here if it were not for the user base that has thus far
> supported it.  Are you about ready to tell us all to go get fscked
> yet again?

Why would you think not?  This is right in line with what they did to
/etc/rc: it eases mechanized frobbing of boot stuff at the price of
contorting human frobbing of boot stuff.

> I wanna bitch about rc.d, but I _can't_ (apart from its slowness and
> ugly aesthetics).  The ability to kill a daemon without having to
> grep its pid is actually a nicety.

Um, greywolf, if you can now kill a daemon without having to grep out
its pid, you always could; conversely, if you couldn't, you can't now.
It's just a question of whether the grepping and killing are done (1)
by hand, (2) by a personal (or site-specific) script (or alias, or
shell function, or whatever), or (3) by an rc.d script.

(1) is slowest and most typing, but is hard to go very far wrong, since
it involves a real human in the loop.

(2) and (3) are comparable on speed and typing.  The differences mostly
have to do with upgrades: if you find the provided script does what you
want, (3) is probably better, because it's upgraded for you in an OS
upgrade...but if the provided script *doesn't* do quite what you want,
(3) is worse, because your local hacks to it will get torched by an OS
upgrade.

Since near as I can figure, NetBSD doesn't care about supporting people
who want to do local hacks to the boot scripts, (3) is probably best
for them.  But I'm surprised to see *you* apparently preferring it,
rather than (1) or (2).

> Angry?  Bitter?  Why, no.  Just because there's no consensus on this
> and it looks like we're about to get steamrolled again...

Surely it's no surprise that people who were willing to commit one
contentious thing without consensus appear ready to commit another
contentious thing without consensus....

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B