On Tue, 2017-10-17 at 21:26 +, Rick Macklem wrote:
> Mateusz Guzik wrote:
> [lots of stuff snipped]
> >
> > I proposed registration of per-process callbacks, not filtering.
> > The code would just walk the list/table/whatever and call everything on
> > it - they asked for it.
> Yep, this would
Mateusz Guzik wrote:
[lots of stuff snipped]
> I proposed registration of per-process callbacks, not filtering.
> The code would just walk the list/table/whatever and call everything on
> it - they asked for it.
Yep, this would work for the NFSv4 client.
Way back when, all I did in OpenBSD was add
I had no problems last night. It associated with one of my netgear APs. I used
/etc/wpa_supplicant.conf.
I am running head and all my ports are built on head (most poudeiere and a few
by hand).
---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.
Cy Schubert
or
---
On Tue, Oct 17, 2017 at 9:57 AM, David Wolfskill
wrote:
> On Tue, Oct 17, 2017 at 12:51:23PM -0400, Allan Jude wrote:
> >
> > > Question: Should one expect a wpa_supplicant-2.6_2 executable built
> > > under FreeBSD stable/11 (amd64) to work on the same hardware, but
> > > running head?
> >
On Tue, Oct 17, 2017 at 12:51:23PM -0400, Allan Jude wrote:
>
> > Question: Should one expect a wpa_supplicant-2.6_2 executable built
> > under FreeBSD stable/11 (amd64) to work on the same hardware, but
> > running head?
>
> Did you run the version from ports, or did you run the base /etc/r
On 2017-10-17 08:58, David Wolfskill wrote:
> On Mon, Oct 16, 2017 at 11:27:00PM -0700, Cy Schubert wrote:
>> In message , Franco
>> Fichtne
>> r writes:
>> ...
>>> wpa_supplicant 2.6_2
>>>
>>> No apparent issues with the ports, preliminary connectivity
>>> checks work as expected. Started a
The FreeBSD-12.0-CURRENT-amd64-20171012-r324542.vmdk image displays
many checksum failed messages when booted. (see attachment).
I think this started about 20170925.
I have VirtualBox VM's running 10.4-STABLE, 11.1-STABLE and 12.0-
CURRENT.
Only the 12.0-CURRENT image exhibits this behavior.
Th
===> sys/boot/efi/boot1 (all)
cc -target x86_64-unknown-freebsd12.0 --
sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2
-pipe -ffreestanding -Wformat -mno-mmx -mno-sse -mno-avx -msoft-
float -fshort-wchar -mno-red-zone -mno-aes -march=nehalem -
DLOADER_UFS_SUPPORT -DLOADER_DISK_SU
On Tue, 2017-10-17 at 00:08 +, Rick Macklem wrote:
> [stuff snipped]
> >
> > >
> > > >
> > > >
> > > pfind* does not do any filtering.
> > >
> Hmm, well I have no idea why the jailed mounts get looping in here then.
>
> >
> > >
> > > The real question though is why are you calling it in
In message <20171017125829.ga35...@albert.catwhisker.org>, David Wolfskill
writ
es:
>
>
> --azLHFNyN32YCQGCU
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Mon, Oct 16, 2017 at 11:27:00PM -0700, Cy Schubert wrote:
On Mon, Oct 16, 2017 at 11:27:00PM -0700, Cy Schubert wrote:
> In message , Franco
> Fichtne
> r writes:
> ...
> > wpa_supplicant 2.6_2
> >
> > No apparent issues with the ports, preliminary connectivity
> > checks work as expected. Started a public CFT over at OPNsense
> > to gather more f
11 matches
Mail list logo