>>If so, then *that*, is, as they say, a fair cop.  Let me say that
>>Itojun is being very, very proactive about fixing the breakage; but
>>its still closing the stable door after the horse has, uh, broken.
>
>As long as no *release* version has this problem, I'm not entirely offended.
>This may sound crazy, especially given that my Mom's laptop runs -current
>as of Tuesday or so, but I generally *expect* -current to include code that
>needs more testing, or partially-completed work.

exactly.  current comes with the caveat that it's not even guaranteed
to compile (http://www.netbsd.org/Releases/current.html)

   NetBSD-current is a daily snapshot of the NetBSD development source
   tree. Because it is ``work in progress,'' it may not be particularly
   well tested, and it may not even compile.

i think that sort of *implies* that it might not work exactly right
from day to day.

>I think we're all spoiled; we spend a few years using -current and get used
>to it being more stable than the major releases of some systems, and we forget
>that it *is* an experimental tree.

um...so we're too good?  ;-)

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."