On Fri, Feb 04, 2000 at 05:53:25PM +0000, [EMAIL PROTECTED] wrote:
> Message-Id: 1468_kb2shu
> From: kb2shu@kb2shu.#sca.ca.usa.noam
> To: [EMAIL PROTECTED]
>
>
> Maybe some of this *rubbish* will help you:
>
> # AUTOMATIC CONFIGURATION
> #
> # Uncomment the appropriate lines below to enable auto-configuration
> # of a particular board. Or comment them out to disable them....
> #
> # NOTE! Although the automatic configuration is enabled by default,
> # I strongly suggest that you comment out this section and use the
> # manual configuration section instead. It's more work to set up, but
> # it's more reliable.
> #
> ###############################################################
>
> # Do AUTOMATIC_IRQ probing
> #
> AUTO_IRQ=auto_irq
>
> # These are the standard COM1 through COM4 devices
> #
> # If you have an internal modeme with a Rockwell Chipset, add a "skip_test"
> # to the /dev/cua3 line below. (It's not added by default because it will
> # screw up people with 8514 displays).
> #
> ${SETSERIAL} /dev/cua0 ${AUTO_IRQ} skip_test autoconfig ${STD_FLAGS}
> ${SETSERIAL} /dev/cua1 ${AUTO_IRQ} skip_test autoconfig ${STD_FLAGS}
> ${SETSERIAL} /dev/cua2 ${AUTO_IRQ} skip_test autoconfig ${STD_FLAGS}
> ${SETSERIAL} /dev/cua3 ${AUTO_IRQ} autoconfig ${STD_FLAGS}
[rest of obsolete rc.script snipped]
Now the script that comes with setserial 2.15:
#
# /etc/rc.serial
# Initializes the serial ports on your system
#
# chkconfig: 2345 50 75
# description: This initializes the settings of the serial port
#
# Distributed with setserial version 2.15
#
# XXXX note: as of 2.15, the autosave feature doesn't work if you are
# using the multiport feature; it doesn't save the multiport configuration
# (for now). Autosave also doesn't work for the hayes devices.
#Will fix later...
#
#
SETSERIAL=/bin/setserial
RCLOCKFILE=/var/lock/subsys/serial
ALLDEVS="/dev/ttyS?"
if /bin/ls /dev/ttyS?? >& /dev/null ; then
ALLDEVS="$ALLDEVS /dev/ttyS??"
fi
[.... rest snipped ....]
See?
Tomi has already mentioned Documantation/Changes.
And another one (FAQ from mgetty+sendfax):
> From: "Theodore Y. Ts'o" <[EMAIL PROTECTED]>
>
> /dev/ttySxx devices are fully POSIX-compliant TTY devices. If you are
> only going to be using one set of tty devices, you should be using
> /dev/ttySxx.
[...]
> While this will allow for simple lockouts between a user using a modem
> for callout and a getty listening on the line for logins, it doesn't
> work if you need to arbitrate between multiple programs wanting to do
> dialout --- for example, users wanting to do dialout and UUCP.
>
> I originally implemented the cuaXX/ttySXX lockout mechanism back before
> FSSTND established a standard convention for the use of tty lock files.
> Now that it's there, people should use the tty lock files and not try
> using /dev/cuaXX. The only reason why /dev/cuaXX hasn't disappeared yet
> is for backwards compatibility reasons.
> - Ted
Please note that Ted is the author & maintainer of setserial.
Ok, I noted some /dev/cua occurrences in the setserial manpage, I'll send
Ted a note about that.
BTW. I've 14 serial ports running in my system, 2 onboard, 4 on a dumb
ISA card and 8 on a fourport compativle card. I've reprogrammed the
address decoding PAL-Chip on the dump card to use other base addresses.
One port runs a 4800 Baud Baycom style modem.
I think I know what I'm doing :-)
Thorsten
--
| Thorsten Kranzkowski Internet: [EMAIL PROTECTED] |
| Mobile: ++49 161 7210230 Snail: Niemannsweg 30, 49201 Dissen, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, [EMAIL PROTECTED] [44.130.8.19] |
