Date: Mon, 5 Sep 2005 02:07:20 +0200 From: Emanuel Strobl <Emanuel.strobl@gmx.net> To: freebsd-questions@freebsd.org, Grant Peel <gpeel@thenetnow.com> Subject: Re: Terminals Message-ID: <200509050207.32548@harrymail> In-Reply-To: <005401c5b191$79c9a6c0$6601a8c0@GRANT> References: <005401c5b191$79c9a6c0$6601a8c0@GRANT>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3432149.qqPrqqYTi5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Sonntag, 4. September 2005 22:44 CEST schrieb Grant Peel: > Hi all, > I have serveral servers in a cage in Toronto, but I live 120 miles away. > Every once in a while, I will crash a box, or lock myself out of one of > them (mostly just the dev box now!). Anyways, is it possible to > daisychain the machines together using COM1 and COM2 so that no matter > what, one can always get to a console? Or am I just wishing here... Of course you can. Just edit /boot/device.hints on one machine so that it=20 uses sio1 (com2) as console: =2D-- /boot/device.hints Thu Aug 18 05:55:08 2005 +++ /tmp/device.hints Mon Sep 5 01:55:36 2005 @@ -36,10 +36,10 @@ hint.sio.0.port=3D"0x3F8" =2Dhint.sio.0.flags=3D"0x10" hint.sio.0.irq=3D"4" hint.sio.1.at=3D"isa" hint.sio.1.port=3D"0x2F8" +hint.sio.1.flags=3D"0x10" hint.sio.1.irq=3D"3" The tell the btx (on both machines) to use the serial device (with flag=20 0x10) for console: echo "-h" >> /boot.config loader will recognice the serial console and use that, if not also set in=20 loader.conf: console=3D"comconsole" Now you can go into single user mode on one machine and cu/tip from the=20 other one. (regarding speed see BOOT_COMCONSOLE_SPEED=3D in make.conf, in=20 =2Dcurrent btx can be runtime configured) Also edit /etc/ttys to open a login on the system console in multiuser=20 mode, for example: =2D-- /builder/usr/src/etc/etc.i386/ttys Fri Oct 24 17:44:08 2003 +++ /builder/usr/src/tools/FlashBSD/examples/net4501conf/etc/ttys Thu= =20 Apr 21 03:35:09 2005 @@ -30,21 +30,21 @@ # # If console is marked "insecure", then init will ask for the root=20 password # when going to single-user mode. =2Dconsole none unknown off secure +console none unknown off insecure # =2Dttyv0 "/usr/libexec/getty Pc" cons25 on secure +ttyv0 "/usr/libexec/getty Pc" cons25 off secure # Virtual terminals =2Dttyv1 "/usr/libexec/getty Pc" cons25 on secure =2Dttyv2 "/usr/libexec/getty Pc" cons25 on secure =2Dttyv3 "/usr/libexec/getty Pc" cons25 on secure =2Dttyv4 "/usr/libexec/getty Pc" cons25 on secure =2Dttyv5 "/usr/libexec/getty Pc" cons25 on secure =2Dttyv6 "/usr/libexec/getty Pc" cons25 on secure =2Dttyv7 "/usr/libexec/getty Pc" cons25 on secure +ttyv1 "/usr/libexec/getty Pc" cons25 off secure +ttyv2 "/usr/libexec/getty Pc" cons25 off secure +ttyv3 "/usr/libexec/getty Pc" cons25 off secure +ttyv4 "/usr/libexec/getty Pc" cons25 off secure +ttyv5 "/usr/libexec/getty Pc" cons25 off secure +ttyv6 "/usr/libexec/getty Pc" cons25 off secure +ttyv7 "/usr/libexec/getty Pc" cons25 off secure ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. =2Dttyd0 "/usr/libexec/getty std.9600" dialup off secure +ttyd0 "/usr/libexec/getty std.115200" unknown on secure ttyd1 "/usr/libexec/getty std.9600" dialup off secure ttyd2 "/usr/libexec/getty std.9600" dialup off secure ttyd3 "/usr/libexec/getty std.9600" dialup off secure Have fun, =2DHarry --nextPart3432149.qqPrqqYTi5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDG4xEBylq0S4AzzwRAgdcAJ0fhIAHngiKOlR+bFDAQyTomYHINACfco+v H0ajmK5oU6kCnY2TfAms8J4= =DWSn -----END PGP SIGNATURE----- --nextPart3432149.qqPrqqYTi5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200509050207.32548>