[I built a FreeBSD head -r340288 context and tried ports head
-r484783 and the problem repeated.]
On 2018-Dec-22, at 12:55, Mark Millard wrote:
> [I found my E-mail records reporting successful builds using
> qemu-user-static from ports head -r484783 under FreeBSD
> head -r340287.]
>
> On
On Thursday, 20 December 2018 18:28:45 MST Kirk McKusick wrote:
> Thanks Rebecca for the report and Mark for the analysis of the problem.
> This should be fixed in -r342290.
Thanks! That did fix it.
--
Rebecca
___
freebsd-current@freebsd.org mailing
In message <865zvkpphn@next.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rg
rav?= w
rites:
> Cy Schubert writes:
> > I know our code is full of workarounds and theirs probably too. The
> > question is should we? IMO no.
>
> Unfortunately, the world is imperfect and does not care about your
>
On Sun, Dec 23, 2018 at 12:27 AM Stefan Esser wrote:
> Am 23.12.18 um 02:39 schrieb Montgomery-Smith, Stephen:
> > On 12/21/18 10:03 PM, Julian H. Stacey wrote:
> >>> The port Makefile that I have prepared is attached below for reference.
> >>> Regards, STefan
> >>
> >> Thanks Stefan,
> >> I
Yuri Pankov writes:
> There's apparently a bug in VMware Workstation NAT implementation,
> [...] The patch itself is attached.
Could you please open a differential and add me as reviewer?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
> Prior to the last update of dns/bind912, this router/firewall
> appliance was running more than a month without having such trouble,
> even the ISP is randomly changing the IPv4/IPv6 addresses spread
> over the day.
>
> What is wrong?
I am not sure what is wrong, but it seems like a bug in
Cy Schubert writes:
> Hmmm. I guess Red Hat Enterprise Linux must be a toy OS then.
I don't speak for them, but I assure you that both their code and ours
are full of workarounds for bugs in third-party software and hardware,
and it is ridiculous to claim otherwise.
> No. We do like Red Hat
On 12/21/18 10:03 PM, Julian H. Stacey wrote:
>> The port Makefile that I have prepared is attached below for reference.
>> Regards, STefan
>
> Thanks Stefan,
> I took current /usr/ports/misc/ctm/
> & converted Stephen's & my diffs to be automatic ports patches:
>
Cy Schubert writes:
> I know our code is full of workarounds and theirs probably too. The
> question is should we? IMO no.
Unfortunately, the world is imperfect and does not care about your
opinion. 90% of the hardware we run on deviates from the spec in some
way or another and requires
In message <86pntszlae@next.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rg
rav?= w
rites:
> Cy Schubert writes:
> > Hmmm. I guess Red Hat Enterprise Linux must be a toy OS then.
>
> I don't speak for them, but I assure you that both their code and ours
> are full of workarounds for bugs in
Cy Schubert writes:
> Add it to ssh_config or sshd_config if one must but have VMware fix
> their bugs. Putting workarounds in our O/S to work around a bug in some
> other vendor's virtualization is something I don't support.
It's something we do *all the time*. Otherwise we'd just be a toy
In message <861s681ypd@next.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rg
rav?= w
rites:
> Cy Schubert writes:
> > Add it to ssh_config or sshd_config if one must but have VMware fix
> > their bugs. Putting workarounds in our O/S to work around a bug in some
> > other vendor's virtualization is
Am 23.12.18 um 02:39 schrieb Montgomery-Smith, Stephen:
> On 12/21/18 10:03 PM, Julian H. Stacey wrote:
>>> The port Makefile that I have prepared is attached below for reference.
>>> Regards, STefan
>>
>> Thanks Stefan,
>> I took current /usr/ports/misc/ctm/
>> & converted Stephen's & my diffs to
In message <82004750-097a-47e5-9981-86b4b7a5f...@gmail.com>, Enji
Cooper writes
:
> > On Dec 22, 2018, at 1:03 PM, Cy Schubert =
> wrote:
>
> =E2=80=A6
>
> > Regarding the Red Hat bugzilla bug, looks like they're doing the right
> > thing by reaching out to VMware. This should be our position as
14 matches
Mail list logo
