From owner-freebsd-current@FreeBSD.ORG Mon Jun 2 10:44:20 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33A14392 for ; Mon, 2 Jun 2014 10:44:20 +0000 (UTC) Received: from forward8l.mail.yandex.net (forward8l.mail.yandex.net [IPv6:2a02:6b8:0:1819::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DEC9323F7 for ; Mon, 2 Jun 2014 10:44:19 +0000 (UTC) Received: from smtp19.mail.yandex.net (smtp19.mail.yandex.net [95.108.252.19]) by forward8l.mail.yandex.net (Yandex) with ESMTP id AF3851A411ED; Mon, 2 Jun 2014 14:44:15 +0400 (MSK) Received: from smtp19.mail.yandex.net (localhost [127.0.0.1]) by smtp19.mail.yandex.net (Yandex) with ESMTP id 71870BE01B9; Mon, 2 Jun 2014 14:44:15 +0400 (MSK) Received: from 84.201.166.192-vpn.dhcp.yndx.net (84.201.166.192-vpn.dhcp.yndx.net [84.201.166.192]) by smtp19.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id byUDm0GZR3-iEq0Y5fY; Mon, 2 Jun 2014 14:44:15 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: c0501b7f-5d8a-4074-a091-75d228951d88 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1401705855; bh=LC17HEsv+omQXpgCyPyuTB3ZsBJpgVmYJBqi6Ium0DU=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=Z+riVci1TWdikEMgBe4Y//3lJHL2yZ55DP55cC6X0xllSUKW5/Bi/XibIVN9d2FRI Emi4RIyoXDdIIWGPrc4dJ2/Os/15OOp3e2Mkl6LstbKspliBRs2qEM9LQix9yw5pUG 2/+CnmnndCTtZrWrH51WKtRy14SNW780V9T4L6bQ= Authentication-Results: smtp19.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <538C555F.2060009@yandex.ru> Date: Mon, 02 Jun 2014 14:43:43 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Adam McDougall , freebsd-current@freebsd.org Subject: Re: diskid documentation References: <20140601134147.GA99583@bewilderbeast.blackhelicopters.org> <1401632245.1113.8.camel@bruno> <538B9BDB.1000604@egr.msu.edu> In-Reply-To: <538B9BDB.1000604@egr.msu.edu> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 02 Jun 2014 10:44:20 -0000 On 02.06.2014 01:32, Adam McDougall wrote: > Also, I believe it is only in 10.0-RELEASE and higher. Even if your > kernel supports it, /dev/diskid will not exist if no hardware is found > with supported strings (tested in a VM just now). Probably, they just disappeared like all other labels, when you got access to disk not through the label. -- WBR, Andrey V. Elsukov