Hi All,
I use self-made base packages for an ARM board. The kernel I use
is IMX6 one. While pkg update I get this:
---
[271/302] Upgrading FreeBSD-kernel-imx6-debug from 12.0.s20170718113533
to 12.0.s20170719070514...
[271/302] Extracting FreeBSD-kernel-imx6-debug-12.0.s20170719070514:
100%
kl
Hi!
Me and Ilya Arkhipov were investigating the cause of this bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215572
In short, when FreeBSD ports options dialog is interrupted by Ctrl+C,
there's chance of sporadic terminal corruption. They are not always
reproducible and seem to be depend
Do you receive packets from 192.168.2.0/24 and 192.168.3.0/24 on igb1.2
and igb1.3 respectively?
Do you really need NAT? As far as I can see, you're looking for basic
static inter-VLAN routing.
Could you check the communication between 2.0/24 and 3.0/24 with
unloaded ipfw module (just to exclude
In message <20170718205700.GA2131@hades.panopticon>, Dmitry Marakasov writes:
>In short, when FreeBSD ports options dialog is interrupted by Ctrl+C,
>there's chance of sporadic terminal corruption. They are not always
>reproducible and seem to be dependent on a machine, shell, terminal,
On Wed, 19 Jul 2017 at 7:37 pm, Boris Samorodov wrote:
> Hi All,
>
> I use self-made base packages for an ARM board. The kernel I use
> is IMX6 one. While pkg update I get this:
> ---
> [271/302] Upgrading FreeBSD-kernel-imx6-debug from 12.0.s20170718113533
> to 12.0.s20170719070514...
> [271/302
Hi Dmitry
Thanks for the detailed report.
Will take a look
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215572
> Now to fix this, I suggest that instead of killing itself, make should
> signal all its childs carefully and wait() on them, only then die
> itself.
>
> Now after a quick
