Re: Recent TTYDEF_LFLAG default change
From: Andrey Chernov (ache_at_nagual.pp.ru)
Date: 11/03/04
- Previous message: Poul-Henning Kamp: "current/LINT: ehci.c problem"
- In reply to: Andrey Chernov: "Re: Recent TTYDEF_LFLAG default change"
- Next in thread: Mike Jakubik: "Re: Recent TTYDEF_LFLAG default change"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 3 Nov 2004 17:41:22 +0300 To: Poul-Henning Kamp <phk@phk.freebsd.dk>, current@freebsd.org
On Wed, Nov 03, 2004 at 02:26:15PM +0300, Andrey Chernov wrote:
> > Most of it would be bogus I think, software should record the current
> > state and restore that, not mangle it with defaults.
>
> Some tty/pty-emulators can (in spirit of screen). It is not ours, it is
> common BSD thing. Better to not make surprises and harden porter's job
> here, really, without a reason. Inside kernel you can do anything you want
> using TTYDEF_LFLAG_NOECHO.
More such things: getty and getty-likes (i.e. fax recievers or FIDO gates
combined with getty). BTW, what about our getty now? It uses TTYDEF_LFLAG.
Python tty module use TTYDEF_LFLAG too:
http://pydoc.org/1.5.2/tty.html
Moreover, it is few minutes results, I even don't try to search hard.
-- http://ache.pp.ru/ _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Poul-Henning Kamp: "current/LINT: ehci.c problem"
- In reply to: Andrey Chernov: "Re: Recent TTYDEF_LFLAG default change"
- Next in thread: Mike Jakubik: "Re: Recent TTYDEF_LFLAG default change"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]