On Tue, Jun 4, 2024 at 5:18 PM Alan Somers wrote:
>
> CAUTION: This email originated from outside of the University of Guelph. Do
> not click links or open attachments unless you recognize the sender and know
> the content is safe. If in doubt, forward suspicious emails to
> ith...@uoguelph.ca.
On Tue, Jun 4, 2024 at 3:52 PM John Hixson wrote:
>
> On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote:
> > On 16/06/2022 15:56, Rick Macklem wrote:
> > > Miroslav Lachman <000.f...@quip.cz> wrote:
> > > > On 24/01/2022 16:13, Rick Macklem wrote:
> > > >
> > > [...]
> > > >
> > > >
>
> Thank you for the message. I'm glad someone has the courage to take the
> plunge. Smbfs is still very important to me. In a heterogeneous environment
> it is still the most common way to share data between systems.
> Are you planning the final version as a kernel module, or will the final
> ve
On 04/06/2024 23:52, John Hixson wrote:
On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote:
On 16/06/2022 15:56, Rick Macklem wrote:
Miroslav Lachman <000.f...@quip.cz> wrote:
On 24/01/2022 16:13, Rick Macklem wrote:
[...]
So, I think Mark and Yuri are correct and looking at
On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote:
> On 16/06/2022 15:56, Rick Macklem wrote:
> > Miroslav Lachman <000.f...@quip.cz> wrote:
> > > On 24/01/2022 16:13, Rick Macklem wrote:
> > >
> > [...]
> > >
> > > > So, I think Mark and Yuri are correct and looking at up to date
On 5/16/24 4:05 PM, Lorenzo Salvadore wrote:
On Thursday, May 16th, 2024 at 20:26, Konstantin Belousov
wrote:
gcc13 from ports
`# gcc ctors.c && ./a.out init 1 init 2 init 5 init 4 init 3 main fini 3 fini 4
fini 5 fini 2 fini 1`
The above order is not expected. I think clang's one is correct
Am Tue, 04 Jun 2024 09:36:38 +0200
Alexander Leidinger schrieb:
> Am 2024-06-03 21:02, schrieb FreeBSD User:
> > Hello,
> >
> > I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running
> > several jails. Jails are
> > attached to a bridge device (bridge1), the physical device on th
On Tue, Jun 4, 2024 at 8:17 AM Gerrit Kühn wrote:
> Am Tue, 28 May 2024 11:19:42 +0200
> schrieb Gerrit Kühn :
>
> > > Not sure if it will break your setup, but this already happened with
> > > 13.2 (I cant recall the exact release).
>
> > I have two machines with onboard NICs (Supermicro H12SSL-
Am Tue, 28 May 2024 11:19:42 +0200
schrieb Gerrit Kühn :
> > Not sure if it will break your setup, but this already happened with
> > 13.2 (I cant recall the exact release).
> I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards)
> running just fine. One is 13.3, the other is
Hi everyone, just to follow up.
I have found something interesting, at the moment I'm focusing on the
issue related to the creation and deletion of sub-interfaces that
trigger ALLOC/MASK errors and bricks the NIC ( not completely as the
other port keeps working, this card has 2x10G).
I have
Am 2024-06-03 21:02, schrieb FreeBSD User:
Hello,
I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running
several jails. Jails are
attached to a bridge device (bridge1), the physical device on that
bridge is igb1 (i350 based
NIC). The bridge is created via host's rc scripts, addi
11 matches
Mail list logo
