On Thu, Feb 20, 2025 at 10:27:28AM +0100, Alexander Leidinger wrote:
> Hi,
>
> I get this backtrace:
> ---snip---
> [102] panic: invalid local group size 16 and count 16
> [102] cpuid = 17
> [102] time = 1740041984
> [102] KDB: stack backtrace:
> [102] db_trace_self_wrapper() at db_trace_self_wrap
On Fri, Feb 21, 2025 at 05:06:16AM -0800, Rick Macklem wrote:
R> Agreed. Unfortunatey, the return values for getaddrinfo(3) do not clearly
R> differentiate between them. I think Gleb's case returns EAI_FAIL, which is
also
R> returned for other failures. I think EAI_NONAME is returned for the case
On Thu, Feb 20, 2025 at 04:28:06PM -0800, Steve Rikli wrote:
S> In that area, I'll note FreeBSD rc.d has a "NETWORKING" dependency for
S> PROVIDE and REQUIRE, and it's included in scripts like nfsclient,
S> mountcritremote et al. However there seems to be no similar dependency
S> for something like
Am 2025-02-20 10:27, schrieb Alexander Leidinger:
Hi,
I get this backtrace:
---snip---
[102] panic: invalid local group size 16 and count 16
[102] cpuid = 17
[102] time = 1740041984
[102] KDB: stack backtrace:
[102] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe07453a5b80
On 2/20/25 12:03, David Chisnall wrote:
No, that’s always been the case in C++. It comes from the rule that two
allocations must have unique addresses. If a structure could have size zero,
an array of these structures would have size zero and the two elements in the
array would have the sa
The problem is one of sequencing. A brute-force solution is not to start rtadvd
until you get the prefix from upstream, then dynamically generate rtadvd.conf
and start rtadvd. Ugly, but functional.
On Fri, Feb 21, 2025 at 07:52:33AM +0100, A FreeBSD User wrote:
> Hello,
>
> Linux (especially Op
On Fri, Feb 21, 2025 at 12:13 AM Toomas Soome wrote:
>
>
>
> On 21. Feb 2025, at 04:39, Rick Macklem wrote:
>
> On Thu, Feb 20, 2025 at 4:28 PM Steve Rikli wrote:
>
>
> On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
>
>
> The subject line basically describes the problem glebius@
>
Hi,
> On 21 Feb 2025, at 06:52, A FreeBSD User wrote:
>
> Hello,
>
> Linux (especially OpenWRT we use) knows about a concept named "IPv6 tokenized
> interface
> identifier". The concept is self explanatory, a interface/router obtains a
> propagated prefix
> and the concept allows the explicit
> On 21. Feb 2025, at 04:39, Rick Macklem wrote:
>
> On Thu, Feb 20, 2025 at 4:28 PM Steve Rikli wrote:
>>
>> On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
>>>
>>> The subject line basically describes the problem glebius@
>>> ran into. When doing an NFS mount in /etc/fstab,
