Kyle Evans 1b50b999f9 tty: implement TIOCNOTTY ... Generally, it's preferred that an application fork/setsid if it doesn't want to keep its controlling TTY, but it could be that a debugger is trying to steal it instead -- so it would hook in, drop the controlling TTY, then do some magic to set things up again. In this case, TIOCNOTTY is quite handy and still respected by at least OpenBSD, NetBSD, and Linux as far as I can tell. I've dropped the note about obsoletion, as I intend to support TIOCNOTTY as long as it doesn't impose a major burden. Reviewed by: bcr (manpages), kib Differential Revision: https://reviews.freebsd.org/D22572		2019-11-30 20:10:50 +00:00
..
devfs.h	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
devfs_devs.c	devfs: introduce a per-dev lock to protect ->si_devsw	2019-11-30 16:46:19 +00:00
devfs_dir.c	r326394 is calling malloc with M_WAITOK under a lock, revert for now	2017-11-30 14:06:54 +00:00
devfs_int.h	devfs: introduce a per-dev lock to protect ->si_devsw	2019-11-30 16:46:19 +00:00
devfs_rule.c	sys/fs: further adoption of SPDX licensing ID tags.	2017-11-27 15:15:37 +00:00
devfs_vfsops.c	devfs: use MNTK_NOMSYNC	2019-10-13 15:41:47 +00:00
devfs_vnops.c	tty: implement TIOCNOTTY	2019-11-30 20:10:50 +00:00