Date: Tue, 15 Nov 2005 20:01:52 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: stable@freebsd.org, David Wolfskill <david@bunrab.catwhisker.org> Subject: Re: Swapfile problem in 6? Message-ID: <20051116040152.GE79020@funkthat.com> In-Reply-To: <20051116033539.GA57529@xor.obsecurity.org> References: <20051115103821.GJ39882@cirb503493.alcatel.com.au> <20051116020933.72951.qmail@web36209.mail.mud.yahoo.com> <20051116031835.GS69015@bunrab.catwhisker.org> <20051116033539.GA57529@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote this message on Tue, Nov 15, 2005 at 22:35 -0500:
> > > What is this "serial BREAK"?
> > > How do I "send a serial BREAK" at the serial
> > > console? Is this some magic key combination?
> >
> > I'm probably saying something about my age by doing this.... :-}
> >
> > A "BREAK" (in serial communications) is an absence of start or stop
> > bits for more than a character's worth of bits, is handled as a
> > "framing error," and is distinct from any character.
>
> If your serial program has trouble sending a break, you can use the
> ALT_BREAK_TO_DEBUGGER config option which instead listens for a
> sequence of ascii input:
>
> #define KEY_CR 13 /* CR '\r' */
> #define KEY_TILDE 126 /* ~ */
> #define KEY_CRTLB 2 /* ^B */
ALT_BREAK_TO_DEBUGGER has an advantage over break is that some terminal
servers and computers when you turn them off (or power is disconnected)
will send a BREAK down the line, which can cause your machine to stop
when you didn't want to..
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051116040152.GE79020>