Thanks Matt, no more spam :)
From: kmacy...@gmail.com [kmacy...@gmail.com] on behalf of K. Macy
[km...@freebsd.org]
Sent: Saturday, May 26, 2018 11:47 PM
To: O. Hartmann
Cc: Pieper, Jeffrey E; freebsd-current ?[freebsd-current@freebsd.org]?
Subject: Re: ifa
Quoting Chris H (from Tue, 22 May 2018
09:59:04 -0700):
On Tue, 22 May 2018 10:12:22 +0200 "Alexander Leidinger"
said
Hi,
I've updated 2 machines to r333966 and I see a change in the
behavior in the network area on one of the systems.
To begin with, the "original" behavior was no
On 05/22, Slawa Olhovchenkov wrote:
> > It has been a while since I tried Karl's patch the last time, and I
> > stopped because it didn't apply to -current anymore at some point.
> > Will what is provided right now in the patch work on -current?
>
> I am mean yes, after s/vm_cnt.v_free_count/vm_
On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote:
> On 05/22, Slawa Olhovchenkov wrote:
> > > It has been a while since I tried Karl's patch the last time, and I
> > > stopped because it didn't apply to -current anymore at some point.
> > > Will what is provided right now in the
Hi all!
Recently I was trying to fix UTMP logging support in Samba, which supposed
to add login entries for all authenticated Samba sessions, writing down
user, session ID and remote host into the UTMP database(s). It used to work
with Samba 3.x and FreeBSD 6/7, but got broken since then, apparent
Hi
I use meta mode and ccache for compile.
I had WITHOUT_RESCUE= in /etc/src.conf.
Then I renamed (thatis practically removed) /etc/src.conf, and removed the
KERNCONF=mykernel from make.conf to compile GENERIC.
After this I found the error described.
N.B. I went back to my original setup (s
