On Fri, Jan 06, 2006 at 11:34:06PM +0800, Dion van der Grijp wrote:
> Not everyone who uses NetBSD and notices a problem has a ready
> solution at hand, or the necessary (NetBSD) experience to provide one.
> And not fixing an identified problem does not render the feedback any
> less useful or important.

Will all this complaining, I still don't know what the exact problem
is with screenblank. Is there a PR describing it? I searched the PR
database for "screenblank" and only came up with port-next68k/23182,
which only says that it "doesn't actually work." (Might be that
there's no support in the next68k port for the ioctl that turns the
display off, in which case that's a port-specific kernel problem, not
a screenblank problem). Even if you're not going to fix the problem
yourself, there's no excuse for not submitting a PR describing what
the problem is.

FWIW, I use screenblank on the i386 port, and it works fine for my
purposes. It doesn't run X, and doesn't have a mouse, but the screen
blanks after a certain amount of time, and unblanks when I press a
key, which is all I ask for.
-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 30 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++