From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 09:10:54 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43CFCBB9; Sun, 25 Jan 2015 09:10:54 +0000 (UTC) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 248A2A59; Sun, 25 Jan 2015 09:10:54 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id t0P9AiXW014415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 25 Jan 2015 01:10:44 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id t0P9AiY9014414; Sun, 25 Jan 2015 01:10:44 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA00489; Sun, 25 Jan 15 00:31:48 PST Date: Sun, 25 Jan 2015 00:31:46 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: freebsd-current@freebsd.org Subject: What replaces DIOCGDINFO? Message-Id: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: imp@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 09:10:54 -0000 -r276737 removed 4 ioctls, including DIOCGDINFO, from . The commit log entry says only "Remove old ioctl use and support, once and for all." What are users of that mechanism supposed to use instead? A grep in UPDATING for either DIOCGDINFO or ioctl came up empty. BTW I ran into this because it breaks a port I maintain. I do not run CURRENT, and thus have not been reading current@ -- but a quick perusal of the current month's archives did not turn up anything obviously pertinent.