mergemaster still having issues

2019-05-17 Thread Pete Wright
hello - i am still having issues with mergemaster when building/installing current on my end as per this thread: https://lists.freebsd.org/pipermail/freebsd-current/2019-May/073403.html my source contains the fix that I think we committed to address the original issue, are there any other steps

Re: mergemaster still having issues

2019-05-17 Thread David Wolfskill
On Fri, May 17, 2019 at 10:46:57AM -0700, Pete Wright wrote: > hello - i am still having issues with mergemaster when > building/installing current on my end as per this thread: > https://lists.freebsd.org/pipermail/freebsd-current/2019-May/073403.html > > my source contains the fix that I think

Re: mergemaster still having issues

2019-05-17 Thread Pete Wright
On 5/17/19 10:51 AM, David Wolfskill wrote: On Fri, May 17, 2019 at 10:46:57AM -0700, Pete Wright wrote: hello - i am still having issues with mergemaster when building/installing current on my end as per this thread: https://lists.freebsd.org/pipermail/freebsd-current/2019-May/073403.html m

Re: mergemaster still having issues

2019-05-17 Thread David Wolfskill
On Fri, May 17, 2019 at 10:55:18AM -0700, Pete Wright wrote: > ... > > E.g.: > > pushd usr.bin/mergemaster && make install; popd > > > > Then re-start the userland installation (e.g., "mergemaster -p ...") and > > proceed with the rest of the install as usual. > > Ah OK, i think missed that i

Re: FreeBSD Core Team Response to Controversial Social Media Posts

2019-05-17 Thread v
Igor et al, Instead of debating definitions of hate speech, free speech, and trying to discover intent, I suggest we focus on right relationships. https://www.youtube.com/watch?v=A14THPoc4-4 Vester On Fri, May 17, 2019, at 12:08 AM, Igor Mozolevsky wrote: > On Sun, 12 May 2019 at 18:28, Igor

panic booting with if_tap_load="YES" in loader.conf

2019-05-17 Thread Rebecca Cran
I just updated from r346856 to r347950 and ran into a new panic, caused by having if_tap_load="YES" in /boot/loader.conf - because it's already built-in to the kernel: module if_tuntap already present! kernel trap 12 with interrupts disabled The backtrace is: vpanic() panic() trap_fatal()

panic booting with if_tap_load="YES" in loader.conf

2019-05-17 Thread Rebecca Cran
I just updated from r346856 to r347950 and ran into a new panic, caused by having if_tap_load="YES" in /boot/loader.conf - because it's already built-in to the kernel: module if_tuntap already present! kernel trap 12 with interrupts disabled The backtrace is: vpanic() panic() trap_fatal()

Re: panic booting with if_tap_load="YES" in loader.conf

2019-05-17 Thread Mark Johnston
On Fri, May 17, 2019 at 10:18:57PM -0600, Rebecca Cran wrote: > I just updated from r346856 to r347950 and ran into a new panic, caused > by having if_tap_load="YES" in /boot/loader.conf - because it's already > built-in to the kernel: I think this patch should fix the panic, but I only compile-te