From nobody Thu Jun 22 00:21:36 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QmgzQ41hJz4gKDp for ; Thu, 22 Jun 2023 00:21:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QmgzP5B5Qz3nN4 for ; Thu, 22 Jun 2023 00:21:53 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b="O9Id/K0u"; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::b36 as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-bd5f59fb71dso6601405276.3 for ; Wed, 21 Jun 2023 17:21:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687393312; x=1689985312; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Nar8WVib48RRcN6ku/GlVUrqBIbFO27uY+72lTdoVSw=; b=O9Id/K0uKKaqodfXDptGgqNoVvFRqky7mgOdoFVkxz+QOzOWXTDvP6Se3egmLzC4gY 4cU0/osbnpZApJRjEj5NIOsvS4mRiONBjNcCMfGu76vR3FPmXjqdL4aDcqKt0lidYKtF V+91qWaT4ElX1G/liHUur0gqLGEdvZpoOLNZ3D4M9V/3aN8vcPWgB1wfWH2xH7Aq6Zfd w1cHrdK1NJOHHuntxJ/quDfuzQp3Op//Bi+AzCKetbk3pfb8qRjfiNSM2wder3ez7v3o eJB3sxWde4ooiqAEr1cz+/l3E95Ohr23Gq7RuqXU+pfqGC0XD0JIy+9ZdXq3RAZu7LTK 43Xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687393312; x=1689985312; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Nar8WVib48RRcN6ku/GlVUrqBIbFO27uY+72lTdoVSw=; b=QGNrwlZuYzwBuFkGUfIbmJyl8yg9CEQAyaX4wzIHuJu+Q1eEIVXYmw/5C4XhskZAvn JxF+SU91qOAvio7Eflx3iJvD/mD2waBra3KDNEcYG1jEkqWomghWQJ8ovg2agiY8GPIS DDzBLQELBKUzSdBVSXm/HrGUY4zsLdUZwbZ6VT6jF97UCN0yQDVgl2Mtn+lSmTW3w7bY Mq0fwbfsWQJ42yX+8GFyZzxUrszocROZyDig97xajDTUYqLg0N8wOUg+YTex0bXIU03f 0vi2fkp/u6R6MtULfVHFl1KJVLPD910Lgi+t+grChHa0mDBSlHuc21w2ACuXdgr///h+ fQiQ== X-Gm-Message-State: AC+VfDwEDIKQ0AWtnUyCw1MtkICT9WqmpfyOWF2JUMT4KG6CAQgcDbwe Hz9dc4YLD2RocjmMGWRIrhM3dBclh2YRlgexqH2A0KTbsA8= X-Google-Smtp-Source: ACHHUZ7jtKL26TsGCf633mk2riFb3Zksmu1sGzAi5YDgSiL/nSZKR2Fkl/OaoVPcKXnt9wS2Wa4fuhsX3tHYLIBLc2w= X-Received: by 2002:a25:2144:0:b0:bc7:1ca2:5488 with SMTP id h65-20020a252144000000b00bc71ca25488mr13485822ybh.19.1687393312424; Wed, 21 Jun 2023 17:21:52 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: Kevin Oberman Date: Wed, 21 Jun 2023 17:21:36 -0700 Message-ID: Subject: Where did the nvd devices go? To: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000fbc66e05feacdea0" X-Spamd-Result: default: False [-0.30 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_SPAM_MEDIUM(0.63)[0.632]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; NEURAL_HAM_LONG(-0.23)[-0.234]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b36:from]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QmgzP5B5Qz3nN4 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --000000000000fbc66e05feacdea0 Content-Type: text/plain; charset="UTF-8" Well, they are still around, but not functional. They are symlinks to nda devices, but the symlinks don't work well. I have no idea when the symlink of nvd to nda happened, but after updating my system to main-n263630-ab3e6234ab6e, at least geom related commands no longer function using nvd0p?. I hit this when trying to use gpart and geli. gpart claims "gpart: No such geom: /dev/nvd0." geli responds (after entering a passphrase) "geli: Provider not found: "/dev/nvd0p7"My previous system version was main-n262908-c16e08e5f324. Was this intentional? If so, why was this change made? If not, could it be fixed? Since I usually use geli with the /dev/gpt devices, I didn't notice it right away, but it could certainly surprise many users. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000fbc66e05feacdea0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Well, they are still around, but not functional.= They are symlinks to nda devices, but the symlinks don't work well.

I have no idea when the symlink of nvd to = nda happened, but after updating my system to main-n263630-ab3e6234ab6e, at= least geom related commands no longer function using nvd0p?. I hit this wh= en trying to use gpart and geli. gpart claims "gpart: No such geom: /d= ev/nvd0." geli responds (after entering a passphrase) "geli: Prov= ider not found: "/dev/nvd0p7"My previous system version was main-= n262908-c16e08e5f324.

Was this intention= al? If so, why was this change made?=C2=A0 If not, could it be fixed? Since= I usually use geli with the /dev/gpt devices, I didn't notice it right= away, but it could certainly=C2=A0 surprise many users.
--
Kevin Oberman, Part = time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000fbc66e05feacdea0--