In message <[email protected]>, Stefan Esser 
wri
tes:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --yUCpJEhUDPo8OlbsS3xTv1HUJiJy3RHm3
> Content-Type: multipart/mixed; boundary="uL2uFaSH9IO96vdjjeafizosWGWwgD79v";
>  protected-headers="v1"
> From: Stefan Esser <[email protected]>
> To: [email protected], [email protected],
>  [email protected]
> Cc: Chris Rees <[email protected]>, Baptiste Daroussin <[email protected]>,
>  Rick Parrish <[email protected]>, Cy Schubert
>  <[email protected]>, Alastair Hogge <[email protected]>
> Message-ID: <[email protected]>
> Subject: Re: git: 77e1ccbee3ed - main - rc: implement parallel boot
> References: <[email protected]>
>  <[email protected]>
>  <[email protected]>
>  <[email protected]>
>  <[email protected]>
> In-Reply-To: <[email protected]>
>
> --uL2uFaSH9IO96vdjjeafizosWGWwgD79v
> Content-Type: text/plain; charset=windows-1252; format=flowed
> Content-Language: en-US
> Content-Transfer-Encoding: quoted-printable
>
> Am 08.03.21 um 10:44 schrieb Alastair Hogge:
> > On 2021-03-08 15:16, Cy Schubert wrote:
> >> In message <[email protected]>, Chris Rees=
>
> >> writes:
> >>> Incidentally, is the plan for this to go into 13 *and* 12, or just 13=
> ?
> >>> It's an exciting step!
> >>
> >> If this does go into 13 or 12, it should be tested in -CURRENT for lon=
> ger
> >> than three weeks. Probably six weeks.
> >=20
> > mountd on my NAS fails to load because unbound (via ports) is not yet
> > responding to any name queries:
>
> SDDM fails to successfully start an X session now, too.
>
> It repeatedly tries to start the X server without success.
> Only a "service sddm restart" terminates this loop.
>
> I do assume that the same applies to quite a number of services
> that are installed form ports/packages.
>
> While we can test parallel execution of rc scripts in base, this
> is not easily possible for the large number of optional services
> provided by ports/packages.
>
> I'll try to find the cause of the start-up failure for the SDDM
> case on my system. But even if I get it fixed on my system, it
> may still fail to start the X server on systems with a different
> set of ports ...
>
> Regards, STefan

Is this new breakage after 763db589328 or before the fixes to this?


-- 
Cheers,
Cy Schubert <[email protected]>
FreeBSD UNIX:  <[email protected]>   Web:  https://FreeBSD.org
NTP:           <[email protected]>    Web:  https://nwtime.org

        The need of the many outweighs the greed of the few.


_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/dev-commits-src-main
To unsubscribe, send any mail to "[email protected]"

Reply via email to