On Tue, Feb 4, 2025, 9:59 PM Cy Schubert <cy.schub...@cschubert.com> wrote:

> In message <202502050047.5150lqqp032...@gitrepo.freebsd.org>, Warner Losh
> write
> s:
> > The branch main has been updated by imp:
> >
> > URL:
> https://cgit.FreeBSD.org/src/commit/?id=2d17f44a5ae6e948c3a93cac30b8315d
> > 127ba900
> >
> > commit 2d17f44a5ae6e948c3a93cac30b8315d127ba900
> > Author:     Warner Losh <i...@freebsd.org>
> > AuthorDate: 2025-02-05 00:36:18 +0000
> > Commit:     Warner Losh <i...@freebsd.org>
> > CommitDate: 2025-02-05 00:47:21 +0000
> >
> >     rc.d: Add hastd as a prereq for devd
> >
> >     Setuping up CARP and HAST described in:
> >
> https://www.freebsd.org/doc/en/books/handbook/disks-hast.html
> >     doesn't work at boot time because devd start before hastd.
> >
> >     PR: 199733
> >     Submitted-by: hs_f...@on-sky.net (no name given)
> > ---
> >  libexec/rc/rc.d/devd | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libexec/rc/rc.d/devd b/libexec/rc/rc.d/devd
> > index 98f2068c2075..524fb045dfab 100755
> > --- a/libexec/rc/rc.d/devd
> > +++ b/libexec/rc/rc.d/devd
> > @@ -3,7 +3,7 @@
> >  #
> >
> >  # PROVIDE: devd
> > -# REQUIRE: netif ldconfig
> > +# REQUIRE: netif ldconfig hastd
> >  # BEFORE: NETWORKING mountcritremote
> >  # KEYWORD: nojail shutdown
> >
> >
>
> This causes boot to hang requiring a ctrl-C to continue the boot.
>
> The reason for this is I, probably like many others, don't use hastd. And
> especially not on laptops.
>
> Maybe put # BEFOFE: devd in the hastd rc script. This way if
> hastd_enable="NO" or not specified in rc.conf there would be no hang
> during
> reboot.
>
> I've reverted this in my local "prod" tree. Life is good again.
>

Ok. It worked for me. I gotta figure out why, but in the mean time I'll
revert.

Warner

-- 
> Cheers,
> Cy Schubert <cy.schub...@cschubert.com>
> FreeBSD UNIX:  <c...@freebsd.org>   Web:  https://FreeBSD.org
> NTP:           <c...@nwtime.org>    Web:  https://nwtime.org
>
>                         e^(i*pi)+1=0
>
>
>
>

Reply via email to