From owner-freebsd-current@FreeBSD.ORG  Sun Jan 25 09:40:20 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F1E33923;
 Sun, 25 Jan 2015 09:40:19 +0000 (UTC)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com
 [IPv6:2a00:1450:4010:c03::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8FD14DCD;
 Sun, 25 Jan 2015 09:40:19 +0000 (UTC)
Received: by mail-la0-f54.google.com with SMTP id hv19so3658646lab.13;
 Sun, 25 Jan 2015 01:40:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=1zAqamWUEPEHuUwJcRqdbIXh+ms6ngTcMzAZriaBlEo=;
 b=OVH47R2MKjGyWVlhH6D8Ua7WIYaKGhdsZgQ/eZzXR3IXupJbYCVX1WJzKLdXr/3j86
 e9j81cNph6EFyOQFpPxPu2U7FeHwlyH8sEu6njbb6uTt23f85Uyd3ZDaKz5rWJE3VI5E
 B/JWEXJXMr4cvYirJBscRHseKwju1RU5Hc0Eo8S0/4mPcKhluM1fIn9WyxNXzNcd50mm
 qbEwA0blhY6B2otqFAbf4iyEzMDLnCOMYe/OLLPLNizu7PN4bi2EKrthEIP1QlZhcAqr
 +TkenPC7OmZwoeS1W5It24nSzl4s5RVJ4eIlrFxf3vAZIB1dZfvGtKYKqa1ljvuR0Wzz
 Hz7w==
MIME-Version: 1.0
X-Received: by 10.112.198.233 with SMTP id jf9mr16196438lbc.9.1422178817636;
 Sun, 25 Jan 2015 01:40:17 -0800 (PST)
Received: by 10.25.30.80 with HTTP; Sun, 25 Jan 2015 01:40:17 -0800 (PST)
In-Reply-To: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com>
References: <54c4a9f2.T1F+E5l9r+DbUlmr%perryh@pluto.rain.com>
Date: Sun, 25 Jan 2015 10:40:17 +0100
Message-ID: <CAPS9+SthFOkpknHbAqYC8LdbUentOCzMsNkbtmo=MWb3UygjnQ@mail.gmail.com>
Subject: Re: What replaces DIOCGDINFO?
From: Andreas Nilsson <andrnils@gmail.com>
To: Perry Hutchison <perryh@pluto.rain.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: Current FreeBSD <freebsd-current@freebsd.org>, 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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jan 2015 09:40:20 -0000

http://lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.html
might have the answer for you.

Best regards
Andreas

On Sun, Jan 25, 2015 at 9:31 AM, Perry Hutchison <perryh@pluto.rain.com>
wrote:

> -r276737 removed 4 ioctls, including DIOCGDINFO, from <sys/disklabel.h>.
> 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.
> _______________________________________________
> 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"
>