summaryrefslogtreecommitdiffstats
path: root/sys/ia64
diff options
context:
space:
mode:
authored <ed@FreeBSD.org>2012-03-21 08:38:42 +0000
committered <ed@FreeBSD.org>2012-03-21 08:38:42 +0000
commit619ab2327e380438e75ad0910f2849aa0ab4d504 (patch)
treedbf94bdfd2e622ff5f7c7a8c7f9faae61cc3bfd5 /sys/ia64
parent77afb41a4e2f8e398cca6791a95a7a8f21cb57e7 (diff)
downloadFreeBSD-src-619ab2327e380438e75ad0910f2849aa0ab4d504.zip
FreeBSD-src-619ab2327e380438e75ad0910f2849aa0ab4d504.tar.gz
Remove pty(4) from our kernel configurations.
As of FreeBSD 8, this driver should not be used. Applications that use posix_openpt(2) and openpty(3) use the pts(4) that is built into the kernel unconditionally. If it turns out high profile depend on the pty(4) module anyway, I'd rather get those fixed. So please report any issues to me. The pty(4) module is still available as a kernel module of course, so a simple `kldload pty' can be used to run old-style pseudo-terminals.
Diffstat (limited to 'sys/ia64')
-rw-r--r--sys/ia64/conf/GENERIC1
-rw-r--r--sys/ia64/conf/SKI1
2 files changed, 0 insertions, 2 deletions
diff --git a/sys/ia64/conf/GENERIC b/sys/ia64/conf/GENERIC
index 2a88215..e22450b 100644
--- a/sys/ia64/conf/GENERIC
+++ b/sys/ia64/conf/GENERIC
@@ -201,7 +201,6 @@ device faith # IPv6-to-IPv4 relaying (translation)
device gif # IPv6 and IPv4 tunneling
device loop # Network loopback
device md # Memory "disks"
-device pty # BSD-style compatibility pseudo ttys
device puc # Multi I/O cards and multi-channel UARTs
device random # Entropy device
device tun # Packet tunnel.
diff --git a/sys/ia64/conf/SKI b/sys/ia64/conf/SKI
index 001c710..ef1ca03 100644
--- a/sys/ia64/conf/SKI
+++ b/sys/ia64/conf/SKI
@@ -53,7 +53,6 @@ device pci # PCI bus support
device ether # Ethernet support
device loop # Network loopback
device md # Memory "disks"
-device pty # BSD-style compatibility pseudo ttys
device random # Entropy device
device tun # Packet tunnel.
OpenPOWER on IntegriCloud