I fiddled with things including going into the CMOS of the Aptiva and changing the serial port form IRQ3 to IRQ4.
Then I tried various combinations of data bits/parity/stop bits in Hyperterminal from Windoze.
In about an hour I started getting the usual /etc/issue file announcement and a login prompt.
I had been getting a few garbage characters before, so it could have been a sticky transistor in the serial port.
Anyhow, perhaps less impressive than Shakespeare but equally satisfying to get it working.
Charles was right about one thing -- although the boot-up verbage from Bering will say TTYS01 is a 16550A the actual device name is ttyS1.
On the issue of parameter order here is what worked (copied from directly from /etc/inittab via hyperterminal): T1:23:respawn:/sbin/getty -L 19200 ttyS2 vt100
and of course I permitted root to login on ttyS2 in /etc/securetty. One the serial port was moved to IRQ4, it became "TTYS02" during bootup.
Thanks everyone... This should close the episode for "Home Firewall 2004" until later when I will try IPsec vpns. Rick.
> Yes, I know you will say "what are you doing running Bering 1.2 on an Aptiva"? > The Aptiva 2176/C66 is a Pentium 1 66Mhz with 16Mb ram... > It is one the many otherwise useless machines I have at home. > > Bering 1.2 floppy is working fine otherwise, but I wanted to connect one of my PC hosts > in through the Aptiva's serial port. > When Bering boots I see the message "TTYS01 is a 16550A" > The line I use in etc/inittab is > T1:23:respawn:/sbin/getty/ -L ttyS01 19200 vt100 > > But, a few minutes after boot I get the message on the firewall console > INIT: id T1 spawning too fast: disabled for 5 minutes. > > Hyperterminal never says it is connected, but there is no reponse. > I have googled for IBM Aptiva 2176 C66 serial port and found some radio shack web page with the specs > Tried also using ttyS0 and ttyS1 since the aptiva supposedly has two serial ports (one might have been the modem) > But no luck with any of the ttyS01, S0 or S1 designations.
Instead of: T1:23:respawn:/sbin/getty/ -L ttyS01 19200 vt100
Try w/o the trailing slash and with the proper parameter order: T1:23:respawn:/sbin/getty -L 19200 ttyS0 vt100
For additional debugging, you can try running the init entry directly from the command line. If you're having 'respawning' problems, there's almost certainly something wrong with your command syntax, which is causing an immediate abort. When run directly from the command prompt, you'll typically get a helpful error message that's lost when running from init.
Note that Bering uses getty from tinylogin, rather than the gnu getty, so there might be some differences in how it operates.
-- Charles Steinkuehler [EMAIL PROTECTED]
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
