On Tue, Sep 04, 2007 at 03:22:45PM -0400, Juan Manuel Palacios wrote:
[...]
> I go as far as remapping some of my bind keys, but the other day I
> had some trouble scrolling up and down a screen buffer ;-)
I believe Terminal.app on OS X grabs the PgUp/PgDn keys, or at least
my experience was that I needed to combine them with a meta-key of
some sort to pass them through my SSH session to the screen instance
on my shell server last time I used it (hyper-apple-cokebottle?).
> In searching the net I've seen that all I'd need to try to start a
> connection is the serial device as a command line argument, but
> how would I go about setting up the various connection parameters
> I might need (baud rate, parity, data width, etc.)? Something
> through stty?
Taken from the manpage for Gnu Screen 4.00.03jw4 (FAU) 2-May-06:
> If a tty (character special device) name (e.g. "/dev/ttya") is
> specified as the first parameter, then the window is directly
> connected to this device. This window type is similar to "screen
> cu -l /dev/ttya". Read and write access is required on the device
> node, an exclusive open is attempted on the node to mark the
> connection line as busy. An optional parameter is allowed
> consisting of a comma separated list of flags in the notation used
> by stty(1):
>
> <baud_rate>
> Usually 300, 1200, 9600 or 19200. This affects transmission as
> well as receive speed.
>
> cs8 or cs7
> Specify the transmission of eight (or seven) bits per byte.
>
> ixon or -ixon
> Enables (or disables) software flow-control (CTRL-S/CTRL-Q) for
> sending data.
>
> istrip or -istrip
> Clear (or keep) the eight bit in each received byte.
>
> You may want to specify as many of these options as applicable.
> Unspecified options cause the terminal driver to make up the
> parameter values of the connection. These values are system
> dependent and may be in defaults or values saved from a previous
> connection.
>
> For tty windows, the info command shows some of the modem control
> lines in the status line. These may include 'RTS', 'CTS', 'DTR',
> 'DSR', 'CD' and more. This depends on the available ioctl()'s and
> system header files as well as the on the physical capabilities of
> the serial board. Signals that are logical low (inactive) have
> their name preceded by an exclamation mark (!), otherwise the
> signal is logical high (active). Signals not supported by the
> hardware but available to the ioctl() interface are usually shown
> low.
>
> When the CLOCAL status bit is true, the whole set of modem signals
> is placed inside curly braces ({ and }). When the CRTSCTS or
> TIOCSOFTCAR bit is set, the signals 'CTS' or 'CD' are shown in
> parenthesis, respectively.
>
> For tty windows, the command break causes the Data transmission
> line (TxD) to go low for a specified period of time. This is
> expected to be interpreted as break signal on the other side. No
> data is sent and no modem control line is changed when a break is
> issued.
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP([EMAIL PROTECTED]); IRC([EMAIL PROTECTED]); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER([EMAIL PROTECTED]);
MUD([EMAIL PROTECTED]:6669); WWW(http://fungi.yuggoth.org/); }
_______________________________________________
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech
