Date: Mon, 09 May 2022 08:04:05 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: "Michael Schuster" <michaelsprivate@gmail.com>, "Wes Maag" <jwmaag@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: FreeBSD, boot environments and /dev Message-ID: <481e0739-bdc4-4ce6-a856-a80cf5294d03@www.fastmail.com> In-Reply-To: <CADqw_gKY8vUwxX5LzEkhVtv1VggZtPJ10Zt_M8-jbymT0miimg@mail.gmail.com> References: <CADqw_g%2BUa8oc-cPm6N3ah1Ey1v-nfNk881O2Vp9TquhBcjDj_g@mail.gmail.com> <CAHMcx4PKQzxOCo2GPa7gR544OK7GQrhfbwQ4A8BBQPCteQXKTA@mail.gmail.com> <CADqw_gKY8vUwxX5LzEkhVtv1VggZtPJ10Zt_M8-jbymT0miimg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 May 2022, at 06:25, Michael Schuster wrote:
> On Fri, May 6, 2022 at 12:15 AM Wes Maag <jwmaag@gmail.com> wrote:
>>
>>
>> On Thu, May 5, 2022 at 4:10 PM Michael Schuster <michaelsprivate@gmail.com> wrote:
>>> Hi all,
>>>
>>> while still working (slowly) on an answer to my own question on the
>>> right workflow to keep current up to date reliably with boot
>>> environments, I noticed that after creating and mounting a new BE,
>>> that new BE's /dev (eg /mnt/dev) is very sparsely populated:
This is expected; /dev would usually be empty until devfs is mounted.
Looking into the unmounted /dev via the last zfs snapshot of your
/ filesystem should also be empty:
$ ls -AFGhl /.zfs/snapshot/$(ls -rt /.zfs/snapshot/ | tail -1)/dev
total 0
If it's not I'd guess these are stray garbage from BE experiments
where /dev wasn't mounted and various scripts & tools tried to pipe
via /dev/{fd,zero,null,...}.
If you created a hypothetical "empty" BE from scratch, unpacked
src tarballs into it, it would also be empty.
A+
Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?481e0739-bdc4-4ce6-a856-a80cf5294d03>