FreeBSD 12-Current Community and Developers,
Regarding Issue #8; I too am having issues. I removed Firefox because it was
randomly closing. And upon reinstall, I was receiving the python rust build
error.
What is the proper syntax for a build with the "--format=ustar" ?
I apologize if I am participating incorrectly. As I am new to the community and
unix.
Best Regards,
Brandon Kastning
AKA. StreetDancer (IRC & Forums)
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
Subject: freebsd-current Digest, Vol 711, Issue 2
Local Time: June 6, 2017 5:00 AM
UTC Time: June 6, 2017 12:00 PM
From: freebsd-current-requ...@freebsd.org
To: freebsd-current@freebsd.org
Send freebsd-current mailing list submissions to
freebsd-current@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freebsd.org/mailman/listinfo/freebsd-current
or, via email, send a message with subject or body 'help' to
freebsd-current-requ...@freebsd.org
You can reach the person managing the list at
freebsd-current-ow...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-current digest..."
Today's Topics:
1. Re: old syslog (jail) and new kernel = 100% CPU (Bryan Drewery)
2. Re: old syslog (jail) and new kernel = 100% CPU
(Ngie Cooper (yaneurabeya))
3. Re: Time to increase MAXPHYS? (Kenneth D. Merry)
4. Boot CURRENT without efi (Andy Neustadter)
5. Re: Boot CURRENT without efi (Allan Jude)
6. Re: Time to increase MAXPHYS? (Edward Tomasz Napiera?a)
7. Re: Boot CURRENT without efi (Toomas Soome)
8. Re: firefox/ rust failed to install on FreeBSD 12-CURRENT
(Jean-S?bastien P?dron)
--
Message: 1
Date: Mon, 5 Jun 2017 08:20:47 -0700
From: Bryan Drewery <bdrew...@freebsd.org>
To: Alexander Leidinger <alexan...@leidinger.net>
Cc: curr...@freebsd.org
Subject: Re: old syslog (jail) and new kernel = 100% CPU
Message-ID: <b0be1be3-4aa7-a768-6102-3c776f053...@freebsd.org>
Content-Type: text/plain; charset="utf-8"
On 6/5/2017 2:34 AM, Alexander Leidinger wrote:
>
> Quoting Bryan Drewery <br...@shatow.net> (from Sun, 4 Jun 2017 14:38:07
> -0700):
>
>> On 6/4/17 5:09 AM, Alexander Leidinger wrote:
>>> Hi,
>>>
>>> new kernel (surely r318877 and later) and old syslog in a jail = NOK.
>>>
>>
>> What branch and revision is the syslogd? From my understanding the bug
>> exists in a head version of syslogd only, maybe MFC'd to stable/11, but
>> not released. If it was MFC'd we need to fix it before the 11.1 release.
>
> This was a syslogd from head for sure.
>
> So the issue was that for an intermediate period of time a bug was in
> syslogd in head which was causing this, and if I would have upgraded a
> system were the jail would have been head from before the or after the
> bug, then I wouldn't have noticed it?
>
Yes, that's my understanding. So it's ultimately a non-issue for
releases since it is just a temporary issue on head.
--
Regards,
Bryan Drewery
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freebsd.org/pipermail/freebsd-current/attachments/20170605/6435eaef/attachment-0001.sig>
--
Message: 2
Date: Mon, 5 Jun 2017 08:53:50 -0700
From: "Ngie Cooper (yaneurabeya)" <yaneurab...@gmail.com>
To: Bryan Drewery <bdrew...@freebsd.org>
Cc: Alexander Leidinger <alexan...@leidinger.net>, curr...@freebsd.org
Subject: Re: old syslog (jail) and new kernel = 100% CPU
Message-ID: <55114361-9212-49ae-a3ff-7691cadb2...@gmail.com>
Content-Type: text/plain; charset="utf-8"
> On Jun 5, 2017, at 08:20, Bryan Drewery <bdrew...@freebsd.org> wrote:
>
> On 6/5/2017 2:34 AM, Alexander Leidinger wrote:
>>
>> Quoting Bryan Drewery <br...@shatow.net> (from Sun, 4 Jun 2017 14:38:07
>> -0700):
>>
>>> On 6/4/17 5:09 AM, Alexander Leidinger wrote:
>>>> Hi,
>>>>
>>>> new kernel (surely r318877 and later) and old syslog in a jail = NOK.
>>>>
>>>
>>> What branch and revision is the syslogd? From my understanding the bug
>>> exists in a head version of syslogd only, maybe MFC'd to stable/11, but
>>> not released. If it was MFC'd we need to fix it before the 11.1 release.
>>
>> This was a syslogd from head for sure.
>>
>> So the issue was that for an intermediate period of time a bug was in
>> syslogd in head which was causing this, and if I would have upgraded a
>> system were the jail would have been head from before
