svn commit: r364817 - head/libexec/rc/rc.d

[Kyle Evans]

On Thu, Aug 27, 2020 at 10:59 AM Andriy Gapon <avg at freebsd.org> wrote:
>
> On 2020-08-27 17:06, Kyle Evans wrote:
> > On Thu, Aug 27, 2020 at 9:05 AM Kyle Evans <kevans at freebsd.org> wrote:
> >>
> >> On Thu, Aug 27, 2020 at 9:03 AM Cy Schubert <Cy.Schubert at cschubert.com> wrote:
> >>>
> >>> What would you suggest in this case, where /etc/zfs/zpool.cache is newer
> >>> than /boot/zfs/zpool.cache?
> >>>
> >>> slippy$ lh /boot/zfs/zpool.cache /etc/zfs/zpool.cache
> >>> -rw-r--r--  1 root  wheel   4.6K Aug 25 07:19 /boot/zfs/zpool.cache
> >>> -rw-r--r--  1 root  wheel   4.7K Aug 27 06:20 /etc/zfs/zpool.cache
> >>> slippy$
> >>>
> >>> Something like, for I in $(ls -t /etc/zfs/zpool.cache
> >>> /boot/zfs/zpool.cache) with the break?
> >>>
> >>
> >> /etc/zfs/zpool.cache is the new location and should generally be
> >> favored if it exists, I reckon.
> >
> > I retract the above. :-) ls -t makes sense.
> >
>
> I actually was about to agree with your first suggestion.
>

I think it's the correct long-term solution, but it kind of depends on
what we're thinking now- if we expect one might test-boot a disk on an
older FreeBSD/ZFS that's still using /boot, there's a chance it will
contain the more recent data.