On Wed, 13 Dec 2017 10:34:02 +0800
blubee blubeeme wrote:
> On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard wrote:
>
> > blubee blubeeme gurenchan at gmail.com wrote on
> > Tue Dec 12 15:58:19 UTC 2017 :
> >
> > > On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme > > >wrote:
> > > > I am seeing
On 2017-Dec-12, at 6:34 PM, blubee blubeeme wrote:
> On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard wrote:
>> blubee blubeeme gurenchan at gmail.com wrote on
>> Tue Dec 12 15:58:19 UTC 2017 :
>>
>> > On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme > > >wrote:
>> > > I am seeing tons of these m
On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard wrote:
> blubee blubeeme gurenchan at gmail.com wrote on
> Tue Dec 12 15:58:19 UTC 2017 :
>
> > On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme > >wrote:
> > > I am seeing tons of these messages while running tail -f
> /var/log/messages
> > > ==
On 2017-Dec-12, at 3:19 PM, Mark Millard wrote:
> On 2017-Dec-12, at 2:02 PM, Andreas Schwarz wrote:
>
>> On 12.12.17, Mark Millard wrote:
>>
>>> I initially jumped from -r326192 to -r326726 and
>>> ended up with a rpi2 that would normally hang
>>> somewhere around release APs being displayed.
On Tue, 12 Dec 2017 20:58:26 -0500 "Shawn Webb"
said
On Tue, Dec 12, 2017 at 05:57:29PM -0800, Chris H wrote:
> Hi all,
> I just fired off a fresh build on a new 12-CURRENT install. But forgot
> to add WITHOUT_OPENSSL to src.conf(5), as I had intended to. :-(
> Anyway, I'd like to remove OpenS
On Tue, Dec 12, 2017 at 05:57:29PM -0800, Chris H wrote:
> Hi all,
> I just fired off a fresh build on a new 12-CURRENT install. But forgot
> to add WITHOUT_OPENSSL to src.conf(5), as I had intended to. :-(
> Anyway, I'd like to remove OpenSSL from base. Any recommendations on the
> best approach,
Hi all,
I just fired off a fresh build on a new 12-CURRENT install. But forgot
to add WITHOUT_OPENSSL to src.conf(5), as I had intended to. :-(
Anyway, I'd like to remove OpenSSL from base. Any recommendations on the
best approach, and best alternatives?
Thanks!
--Chris
___
[Just adding back traces. ffs_mount
use of uma_zcreate is involved in the
kernel thread, as is uma_reclaim_worker's
use of uma_reclaim_locked in the uma
thread.]
On 2017-Dec-12, at 4:20 PM, Mark Millard wrote:
> On 2017-Dec-12, at 3:19 PM, Mark Millard wrote:
>
>> On 2017-Dec-12, at 2:02 PM, A
On 12.12.17, Mark Millard wrote:
> On 2017-Dec-12, at 2:02 PM, Andreas Schwarz wrote:
>> JFYI, the latest kernel (and world) running at one of my
>> RPI2-B is r326631, without any issues.
>
> Interesting. (By the way: My context
> is with a V1.1 Cortex-A7 based rpi2,
> not V1.2 and Cortex-A53.)
On Tue, Dec 12, 2017 at 12:40 PM, Alan Somers wrote:
> On Tue, Dec 12, 2017 at 1:39 PM, Chris H wrote:
>
>> On Tue, 12 Dec 2017 12:27:37 -0800 "Kevin Oberman"
>> said
>>
>> On Tue, Dec 12, 2017 at 12:02 PM, Chris H wrote:
>>>
>>> > On Tue, 12 Dec 2017 10:15:10 -0800
>>> said
>>> >
>>> > On Tu
On Tue, Dec 12, 2017 at 2:55 PM, Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> Hum, just noticed this. 25k hours power on, 2M load cycles, this is
> very hard on a hard drive. Your drive is going into power save mode
> and unloading the heads. Infact at a rate of 81 times per
On Tue, 12 Dec 2017 13:56:56 -0800 said
On Tue, 12 Dec 2017 14:33:10 -0700 "Warner Losh" said
> On Tue, Dec 12, 2017 at 2:28 PM, Chris H wrote:
>
> > On Tue, 12 Dec 2017 11:37:33 -0800 said
> >
> > Hello all,
> >> I just blew away a old RELENG_11, to start working with current. I
> >> mus
> Am Tue, 12 Dec 2017 10:52:27 -0800 (PST)
> "Rodney W. Grimes" schrieb:
>
>
> Thank you for answering that fast!
>
> > > Hello,
> > >
> > > running CURRENT (recent r326769), I realised that smartmond sends out
> > > some console
> > > messages when booting the box:
> > >
> > > [...]
> > > D
On 12.12.17, Mark Millard wrote:
> I initially jumped from -r326192 to -r326726 and
> ended up with a rpi2 that would normally hang
> somewhere around release APs being displayed.
> (I have had a couple of completed boots but many
> dozens of hung-up attempts.) Both a debug kernel
> and a non-debu
> Hello,
>
> running CURRENT (recent r326769), I realised that smartmond sends out some
> console
> messages when booting the box:
>
> [...]
> Dec 12 14:14:33 <3.2> box1 smartd[68426]: Device: /dev/ada6, 1 Currently
> unreadable
> (pending) sectors Dec 12 14:14:33 <3.2> box1 smartd[68426]: Devi
On 2017-Dec-12, at 2:02 PM, Andreas Schwarz wrote:
> On 12.12.17, Mark Millard wrote:
>
>> I initially jumped from -r326192 to -r326726 and
>> ended up with a rpi2 that would normally hang
>> somewhere around release APs being displayed.
>> (I have had a couple of completed boots but many
>> doz
There are a couple of ways you can address this. You'll need to offline the
vdev first. If you've done a smartcrl -t long and if the test failed, smartcrl
-a will tell you which block it had an issue with. You can use dd, ddrescue or
dd_rescue to dd the block over itself. The drive may rewrite t
Am Tue, 12 Dec 2017 10:52:27 -0800 (PST)
"Rodney W. Grimes" schrieb:
Thank you for answering that fast!
> > Hello,
> >
> > running CURRENT (recent r326769), I realised that smartmond sends out some
> > console
> > messages when booting the box:
> >
> > [...]
> > Dec 12 14:14:33 <3.2> box1 sm
blubee blubeeme gurenchan at gmail.com wrote on
Tue Dec 12 15:58:19 UTC 2017 :
> On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme >wrote:
> > I am seeing tons of these messages while running tail -f /var/log/messages
> >
> > Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(25):
On Tue, 12 Dec 2017 14:33:10 -0700 "Warner Losh" said
On Tue, Dec 12, 2017 at 2:28 PM, Chris H wrote:
> On Tue, 12 Dec 2017 11:37:33 -0800 said
>
> Hello all,
>> I just blew away a old RELENG_11, to start working with current. I
>> must admit I had several disappointments regarding the insta
On Tue, Dec 12, 2017 at 2:28 PM, Chris H wrote:
> On Tue, 12 Dec 2017 11:37:33 -0800 said
>
> Hello all,
>> I just blew away a old RELENG_11, to start working with current. I
>> must admit I had several disappointments regarding the installer.
>> But that's for another topic, and another time.
>
On Tue, 12 Dec 2017 11:37:33 -0800 said
Hello all,
I just blew away a old RELENG_11, to start working with current. I
must admit I had several disappointments regarding the installer.
But that's for another topic, and another time.
To the point;
I completed the install. The only event(s) that m
On Tue, Dec 12, 2017 at 1:39 PM, Chris H wrote:
> On Tue, 12 Dec 2017 12:27:37 -0800 "Kevin Oberman"
> said
>
> On Tue, Dec 12, 2017 at 12:02 PM, Chris H wrote:
>>
>> > On Tue, 12 Dec 2017 10:15:10 -0800
>> said
>> >
>> > On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
>> >> > Sho
On Wed, Dec 06, 2017 at 10:35:37AM -0500, Thomas Laus wrote:
> Group:
>
> I updated my amd64 computer today to r326622 and copied the
> /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The
> BTX loader stopped and could not load. This rendered my system
> 'un-bootable'. I copie
On Tue, 12 Dec 2017 12:27:37 -0800 "Kevin Oberman" said
On Tue, Dec 12, 2017 at 12:02 PM, Chris H wrote:
> On Tue, 12 Dec 2017 10:15:10 -0800 said
>
> On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
>> > Should man(1)'s default pager change to "less -s"? Vote and flame at
>> th
On Tue, Dec 12, 2017 at 12:02 PM, Chris H wrote:
> On Tue, 12 Dec 2017 10:15:10 -0800 said
>
> On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
>> > Should man(1)'s default pager change to "less -s"? Vote and flame at
>> the
>> > Phabricator link below.
>> > > https://reviews.freebs
On Tue, 12 Dec 2017 10:15:10 -0800 said
On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
> Should man(1)'s default pager change to "less -s"? Vote and flame at the
> Phabricator link below.
>
> https://reviews.freebsd.org/V7
>
Does not work.
Unhandled Exception ("AphrontMalfor
Hello all,
I just blew away a old RELENG_11, to start working with current. I
must admit I had several disappointments regarding the installer.
But that's for another topic, and another time.
To the point;
I completed the install. The only event(s) that might be notable
during the install. Was ear
Ordinary human decency.
On Tue, Dec 12, 2017 at 11:06 AM, Cy Schubert wrote:
> What about those of us who want multiple accounts?
>
> Just kidding but you get my point.
>
> What's to stop someone from having more than one vote?
>
> ---
> Sent using a tiny phone keyboard.
> Apologies for any typos
The vote isn't secret; if you vote as both c...@freebsd.org and c...@github.com
it'll be obvious.
On Tue, Dec 12, 2017 at 12:06 PM, Cy Schubert
wrote:
> What about those of us who want multiple accounts?
>
> Just kidding but you get my point.
>
> What's to stop someone from having more than one
What about those of us who want multiple accounts?
Just kidding but you get my point.
What's to stop someone from having more than one vote?
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
Th
On Tue, Dec 12, 2017 at 10:41:49AM -0800, Conrad Meyer wrote:
> On Tue, Dec 12, 2017 at 10:27 AM, Steve Kargl
> wrote:
> > There isn't a question. I'm pointing out your poll apparently
> > is limited to a select few individuals that use FreeBSD.
>
> The select few individuals being "literally an
On Tue, Dec 12, 2017 at 10:21 AM, O. Hartmann
wrote:
>
> Question: is it possible to simply pull the faulty disk (implies I know
> exactly which one
> to pull!) and then prepare and add the replacement HDD and let the system
> do its job
> resilvering the pool?
>
​zpool offline
Do that first.
On Tue, Dec 12, 2017 at 10:27 AM, Steve Kargl
wrote:
> There isn't a question. I'm pointing out your poll apparently
> is limited to a select few individuals that use FreeBSD.
The select few individuals being "literally anyone that wants to
participate?" https://reviews.freebsd.org/auth/registe
On Tue, Dec 12, 2017 at 11:27 AM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Tue, Dec 12, 2017 at 11:19:21AM -0700, Alan Somers wrote:
> > On Tue, Dec 12, 2017 at 11:15 AM, Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > > On Tue, Dec 12, 2017 at 11:03:54AM -0
On Tue, Dec 12, 2017 at 11:21 AM, O. Hartmann
wrote:
> Hello,
>
> running CURRENT (recent r326769), I realised that smartmond sends out some
> console
> messages when booting the box:
>
> [...]
> Dec 12 14:14:33 <3.2> box1 smartd[68426]: Device: /dev/ada6, 1 Currently
> unreadable
> (pending) sec
On Tue, Dec 12, 2017 at 11:19:21AM -0700, Alan Somers wrote:
> On Tue, Dec 12, 2017 at 11:15 AM, Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
> > > Should man(1)'s default pager change to "less -s"? Vote and flame at
Hello,
running CURRENT (recent r326769), I realised that smartmond sends out some
console
messages when booting the box:
[...]
Dec 12 14:14:33 <3.2> box1 smartd[68426]: Device: /dev/ada6, 1 Currently
unreadable
(pending) sectors Dec 12 14:14:33 <3.2> box1 smartd[68426]: Device: /dev/ada6, 1
Off
On Tue, Dec 12, 2017 at 11:15 AM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
> > Should man(1)'s default pager change to "less -s"? Vote and flame at the
> > Phabricator link below.
> >
> > https://reviews.freebsd.org/V7
On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote:
> Should man(1)'s default pager change to "less -s"? Vote and flame at the
> Phabricator link below.
>
> https://reviews.freebsd.org/V7
>
Does not work.
Unhandled Exception ("AphrontMalformedRequestException")
Your browser did not su
Should man(1)'s default pager change to "less -s"? Vote and flame at the
Phabricator link below.
https://reviews.freebsd.org/V7
-Alan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
On Wed, Dec 6, 2017 at 3:53 PM, Alan Somers wrote:
> On Wed, Dec 6, 2017 at 3:35 PM, Jamie Landeg-Jones
> wrote:
>
>> Alan Somers wrote:
>>
>> > How about just setting MANPAGER=less in your environment?
>>
>> Because some of us prefer "more"?
>>
>> And as I said, it's related to searching using
On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme
wrote:
> I am seeing tons of these messages while running tail -f /var/log/messages
>
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(25): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(22): failed
> Dec 12 15
I initially jumped from -r326192 to -r326726 and
ended up with a rpi2 that would normally hang
somewhere around release APs being displayed.
(I have had a couple of completed boots but many
dozens of hung-up attempts.) Both a debug kernel
and a non-debug kernel hang the same way.
Bisecting the ker
On 11/09/2017 14:52, Konstantin Belousov wrote:
> Hello,
> I created two reviews to axe two features which I personally find of
> little use in modern FreeBSD.
>
> https://reviews.freebsd.org/D13015 xlint
Hi,
I just discovered that this change brakes building a pre change system
(using nanobsd s
45 matches
Mail list logo