Date: Sun, 15 Dec 2019 23:16:32 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Gleb Popov <arrowd@freebsd.org>, freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: Scripting bsdinstall Message-ID: <83e5831b-2d70-0cee-fd6b-13f8eaf42d9f@grosbein.net> In-Reply-To: <CALH631=S0d9kmYRNrG5PVg9rqUF80Ko_Z5DsP=9dGKQKodW5Hg@mail.gmail.com> References: <CALH631=S0d9kmYRNrG5PVg9rqUF80Ko_Z5DsP=9dGKQKodW5Hg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
15.12.2019 16:52, Gleb Popov wrote: > - Same question goes for target drive. In most cases it is ada0, but how do > I dynamically find it out? We have sysctl kern.disks. An example for system with four-slots card-reader, two SATA disks connected using CAM-enabled controlled and one Blu-Ray R/W drive: $ sysctl kern.disks kern.disks: ada1 da3 da2 da1 da0 ada0 cd0 Bootable USB flash could be /dev/da4 here, so better use GEOM_LABEL names (UFS labels etc.) or ZFS pool/fs names. Also, for non-CAM disk controller like mfi(4) disk names can be /dev/mfidX (RAID volumes), or something like /dev/vtbdX for virtio-enabled VM guest.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83e5831b-2d70-0cee-fd6b-13f8eaf42d9f>