> 1) Last time I mentioned new ioctl's on tech-kern, I got flamed or
> silence.

That's kind of a bummer, eh?  It does seem like there are a lot of
folks out there who live to pick apart solutions to a problem without
proposing alternate solutions.  Perhaps there should be a set of rules
for that list to enforce serious counter-proposals for every "flame".
Anyway, enough about that...

> 2) How do you send these ioctl's? Someone's got to write a zstty-
> twiddling program?

That was my thought.  Those folks who use serial consoles that do send
breaks could run such a beast in /etc/rc or /etc/rc.local.

BTW, the reason that break is used is that it causes an interrupt
condition that is not dependant on any other processing, it should
be visible at any baud rate, and it conflicts with nothing that the
user might wish to be entering normally.  At least, that's why I
expect that we're using a break instead of, say, ^k to enter the
debugger.

-allen

-- 
 Allen Briggs - end killing - briggs@macbsd.com ** MacBSD == NetBSD/mac68k **
   Where does all my time go?  <a href="http://www.netbsd.org/">Guess.</a>