From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14442 invoked from network); 1 May 2001 21:25:00 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 May 2001 21:25:00 -0000 Received: (qmail 26031 invoked by alias); 1 May 2001 21:24:55 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14191 Received: (qmail 26004 invoked from network); 1 May 2001 21:24:53 -0000 Date: Tue, 1 May 2001 23:23:57 +0200 From: Thomas =?iso-8859-1?Q?K=F6hler?= To: zsh-workers@sunsite.dk Subject: Re: zsh on serial line? Message-ID: <20010501232357.A2264@picard.franken.de> Mail-Followup-To: Thomas =?iso-8859-1?Q?K=F6hler?= , zsh-workers@sunsite.dk References: <20010501114831.A16624@picard.franken.de> <1010501170648.ZM7145@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <1010501170648.ZM7145@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Tue, May 01, 2001 at 05:06:47PM +0000 X-Operating-System: Linux picard 2.2.17 X-Editor: http://www.vim.org/ X-IRC: tirc; Nick: jeanluc X-URL: http://jeanluc-picard.de/ --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 01, 2001 at 05:06:47PM +0000, Bart Schaefer wrote: >=20 > On May 1, 11:48am, Thomas wrote: > } Subject: zsh on serial line? > } > } I have a digital VT510 which I connected to my PC's second serial port, > } /dev/ttyS1, and on the linux box, I started "mgetty -r /dev/ttyS1". > }[...] > } [snipped lots of syscalls] > } readlink("/proc/self/fd/0", "/dev/ttyS1", 4095) =3D 10 > } open("/dev/ttyS1", O_RDWR|O_NOCTTY|0x8000 > }=20 > } Uhm. It stops when trying to open /dev/ttyS1 - what is it waiting for? >=20 > It must be this code in init.c: >=20 > /* Make sure the tty is opened read/write. */ > if (isatty(0)) { > zsfree(ttystrname); > if ((ttystrname =3D ztrdup(ttyname(0)))) { > SHTTY =3D movefd(open(ttystrname, O_RDWR | O_NOCTTY)); >=20 > The kernel probably thinks that ttyS1 is a modem line and is imposing the > "two-device / kernel-locking scheme" mentioned under the -b option in the > mgetty manual page. Good point. > } How can I change that? >=20 > Try using "setserial ^session_lockout ^pgrp_lockout" on the line, but I've > never actually done that so I don't know if it will make any difference. Well, setserial doesn't like "^pgrp_lockout", but "^session_lockout" seems to help in that I can interrupt the zsh using ^C - but that ends the zsh session which is not exactly what I want :) Uhm... the trick is not even that complicated: Just use /sbin/getty instead of /sbin/mgetty - voila, all works like a charm :-) Now guess why it's called m(odem)getty and not vtgetty :) Thanks, Thomas --=20 Thomas K=F6hler Email: jean-luc@picard.franken.de | LCARS - Linux <>< WWW: http://jeanluc-picard.de | for Computers IRC: jeanluc | on All Real PGP public key available from Homepage! | Starships --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE67ylsTEYXWMJlHuYRAikUAJ4spjIggTr7uxaQ5ftNYnthpOYaHwCgmJX/ vtdtoF54ZVmCbj8nXbavT6k= =3S8b -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--