Sun, Feb 26, 2012 at 01:34:23PM +, Bob Bishop wrote:
> I'd like to hear from somebody who understands this stuff on the
> relative merits of blackhole routes vs firewall drop rules for
> dealing with packets from unwanted sources. I'm particularly
> interested in efficiency and scalability. Tha
>> +++ swap_pager.c2012-02-25 13:19:51.0 +0100
>> @@ -119,7 +119,7 @@
>> * The 32-page limit is due to the radix code (kern/subr_blist.c).
>> */
>> #ifndef MAX_PAGEOUT_CLUSTER
>> -#define MAX_PAGEOUT_CLUSTER 16
>> +#define MAX_PAGEOUT_CLUSTER 256
>> #endif
> [snip]
>> but swap_pag
on 28/02/2012 11:43 Wojciech Puchar said the following:
>>> +++ swap_pager.c2012-02-25 13:19:51.0 +0100
>>> @@ -119,7 +119,7 @@
>>> * The 32-page limit is due to the radix code (kern/subr_blist.c).
>>> */
>>> #ifndef MAX_PAGEOUT_CLUSTER
>>> -#define MAX_PAGEOUT_CLUSTER 16
>>> +#de
Hello!
I am trying to install 9.0-RELEASE from standard amd64 memstick image.
During the install huge amount of "rescan already queued" messages
breaks installer interface.
(noperiph:ata1:0:-1:-1): rescan already queued
(noperiph:ata1:0:-1:-1): rescan already queued
(noperiph:ata1:0:-1:-1): resca
On Tue, Feb 28, 2012 at 2:21 AM, Andriy Gapon wrote:
> on 28/02/2012 11:43 Wojciech Puchar said the following:
+++ swap_pager.c 2012-02-25 13:19:51.0 +0100
@@ -119,7 +119,7 @@
* The 32-page limit is due to the radix code (kern/subr_blist.c).
*/
#ifndef MAX
Sorry but, perhaps should I write this another FreeBSD mailing list?...
perhaps this one, it's not it's place... if this can be the situation,
please tell me which mailing list to send to this suggestion.
Thanks a lot for you're time,
Best regards.
On Mon, 27 Feb 2012 11:22:25 +0100, ego...@ra
On Mon, 2012-02-27 at 04:09 -0800, Karl Pielorz wrote:
>
> --On 27 February 2012 12:04 + Karl Pielorz
> wrote:
>
> > Once the kernel is loading you see:
>
> Sorry - that should be, once the O/S is booting, not kernel loading - you
> see: ...
>
> > "
> > ugen1.2: at usbus1
> > ums0: > 1
On Tue, 2012-02-28 at 07:33 -0800, Dmitry S. Kasterin wrote:
> Hello!
>
> I am trying to install 9.0-RELEASE from standard amd64 memstick image.
> During the install huge amount of "rescan already queued" messages
> breaks installer interface.
>
> (noperiph:ata1:0:-1:-1): rescan already queued
>
I was trying to cross compile sudo for i386 on an amd64 host and was
befuddled by the following ./configure error output.
checking for library containing crypt... -lcrypt
checking for library containing getspnam... no
checking for library containing getprpwnam... no
configure: error: "dlopen prese
- Original Message -
From: John Baldwin
To: rank1see...@gmail.com
Cc: hack...@freebsd.org, "Roman Divacky"
Date: Mon, 27 Feb 2012 11:23:59 -0500
Subject: Re: BUG: 9.0 stage 2 boot (/boot/boot)
> On Saturday, February 25, 2012 9:41:48 am rank1see...@gmail.com wrote:
> > > Do you only see
>>> right. but still 32 pages is 128kB, but i see 64kB I/Os in systat/vmstat
>>
>> Right, but the comment says to not define MAX_PAGEOUT_CLUSTER to a value
>> greater
>> than 32, but you did that. So all bets could be off unless you examined the
>> code and know exactly what should happen in this
On Tue, Feb 28, 2012 at 1:06 PM, Wojciech Puchar
wrote:
right. but still 32 pages is 128kB, but i see 64kB I/Os in systat/vmstat
>>>
>>> Right, but the comment says to not define MAX_PAGEOUT_CLUSTER to a value
>>> greater
>>> than 32, but you did that. So all bets could be off unless you ex
Try i486 instead. There is a setting in the compiler code that was
changed a long while back to where it will only compile to i486 and
above. I would think that this is probably what you are seeing.
This is what I have on 8-STABLE for GCC but for clang I have no clue.
contrib/gcc/config/i386/i38
Sean, good day.
Tue, Feb 28, 2012 at 11:00:19AM -0800, Sean Bruno wrote:
> I was trying to cross compile sudo for i386 on an amd64 host and was
> befuddled by the following ./configure error output.
>
> checking for library containing crypt... -lcrypt
> checking for library containing getspnam...
Hi Sean!
2012/2/28, Sean Bruno :
> I had the same issue on my laptop with an eSATA port. I disabled the
> eSATA port and that made the messages go away. According to mav@ these
> were harmless, but annoying.
The problem is that my laptop has no eSATA port.
I've thoroughly examined the case and
15 matches
Mail list logo