On Wed, Nov 28, 2012 at 8:35 PM, Andriy Gapon wrote:
>
> Recently some changes were made to how a root pool is opened for root
> filesystem
> mounting. Previously the root pool had to be present in zpool.cache. Now it
> is
> automatically discovered by probing available GEOM providers.
> The n
On Thu, Dec 13, 2012 at 2:56 PM, Freddie Cash wrote:
...
> You could at least point to the FreeBSD Forums version of that post. :)
>
> https://forums.freebsd.org/showthread.php?t=31662
Andriy,
I figured out my problem. It was really, really stupid PEBKAC (copied
a KERNCONF from one system tha
On Wed, Dec 19, 2012 at 3:46 PM, Łukasz Wąsikowski
wrote:
> W dniu 2012-12-19 07:14, Kimmo Paasiala pisze:
>
>>> I wrote a small patch for /etc/network.subr to add support for
>>> ipv6_addrs_IF aliases in rc.conf(5) to match the already existing
>>> ipv4_addrs_IF aliases for ipv4 addresses. With t
I finally remembered to remove the .it phk :-).
On Wed, 19 Dec 2012, Luigi Rizzo wrote:
On Wed, Dec 19, 2012 at 10:51:48AM +, Poul-Henning Kamp wrote:
...
As I said in my previous email:
typedef dur_t int64_t;/* signed for bug catching */
#define DURSEC ((dur_t
In message <50d1e0d8.9070...@freebsd.org>, Alexander Motin writes:
>It would be late to change this after committing. I would definitely
>like it to be done earlier to not redo all the tests, but I think we
>could convert callout and eventtimers code to 32.32 format in several
>days. T
On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
In message <20121220005706.i1...@besplex.bde.org>, Bruce Evans writes:
On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
Except that for absolute timescales, we're running out of the 32 bits
integer part.
Except 32 bit time_t works until 2
On Wed, 19 Dec 2012, Davide Italiano wrote:
On Wed, Dec 19, 2012 at 4:18 AM, Bruce Evans wrote:
I would have tried a 32 bit format with a variable named 'ticks'.
Something like:
- ticks >= 0. Same meaning as now. No changes in ABIs or APIs to use
this. The tick period would be constant
schrieb Alexander V. Chernikov am 08.05.2011 15:09 (localtime):
> At the moment the only possible way to set packet fib from userland is
> ipfw(8) setfib rule. Since no 'setfib tablearg' exists ruleset grows
> with every fib.
> Additionally, there is no way to set packet fib before netgraph
> proc
On Wed, Dec 19, 2012 at 7:37 AM, Poul-Henning Kamp wrote:
>
> In message <20121219150809.ga98...@onelab2.iet.unipi.it>, Luigi Rizzo
> writes:
>
> >> typedef dur_t int64_t;/* signed for bug catching */
> >> #define DURSEC ((dur_t)1 << 32)
> >> #define DUR
dropping phk _AT_ onelab2 _DOT_ something from CC as long as it
doesn't seem a valid mail address and I'm annoyed mails bounce back.
On Wed, Dec 19, 2012 at 6:20 AM, Bruce Evans wrote:
> On Wed, 19 Dec 2012, Davide Italiano wrote:
>
>> On Wed, Dec 19, 2012 at 4:18 AM, Bruce Evans wrote:
>
>
>>>
On 19.12.2012 16:20, Bruce Evans wrote:
On Wed, 19 Dec 2012, Davide Italiano wrote:
On Wed, Dec 19, 2012 at 4:18 AM, Bruce Evans
wrote:
I would have tried a 32 bit format with a variable named 'ticks'.
Something like:
- ticks >= 0. Same meaning as now. No changes in ABIs or APIs to use
In message <20121219150809.ga98...@onelab2.iet.unipi.it>, Luigi Rizzo writes:
>> typedef dur_t int64_t;/* signed for bug catching */
>> #define DURSEC ((dur_t)1 << 32)
>> #define DURMIN (DURSEC * 60)
>> #define DURMSEC (DURSEC / 1000)
>>
On Wed, Dec 19, 2012 at 10:51:48AM +, Poul-Henning Kamp wrote:
>
> In message
>
> , Davide Italiano writes:
>
> >Right now -- the precision is specified in 'bintime', which is a binary
> >number.
> >It's not 32.32, it's 32.64 or 64.64 depending on the size of time_t in
> >the speci
Oops, I did my usual brain fart again and forgot to attach the
patch. Here it is, rick
- Original Message -
> Just fyi, r243965 introduced a minor pola violation where the
> nfsd daemon won't start for kernels built without "options INET6".
>
> The attached patch, which I will commit to h
Just fyi, r243965 introduced a minor pola violation where the
nfsd daemon won't start for kernels built without "options INET6".
The attached patch, which I will commit to head later to-day, fixes
the problem. (Or you can add "options INET6" to your kernel config.)
Reported and tested by avg@.
r
On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
In message <20121219221518.e1...@besplex.bde.org>, Bruce Evans writes:
With this format you can specify callouts 68 years into the future
with quarter nanosecond resolution, and you can trivially and
efficiently compare dur_t's with
In message <20121220005706.i1...@besplex.bde.org>, Bruce Evans writes:
>On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
>> Except that for absolute timescales, we're running out of the 32 bits
>> integer part.
>
>Except 32 bit time_t works until 2106 if it is unsigned.
That's sort of not a
W dniu 2012-12-19 07:14, Kimmo Paasiala pisze:
>> I wrote a small patch for /etc/network.subr to add support for
>> ipv6_addrs_IF aliases in rc.conf(5) to match the already existing
>> ipv4_addrs_IF aliases for ipv4 addresses. With this patch the ipv6
>> aliases can be written like:
[...]
> Did
On Wed, Dec 19, 2012 at 4:18 AM, Bruce Evans wrote:
> On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
>
>>
>> In message
>>
>> , Davide Italiano writes:
>>
>>> Right now -- the precision is specified in 'bintime', which is a binary
>>> number.
>>> It's not 32.32, it's 32.64 or 64.64 depend
In message <20121219221518.e1...@besplex.bde.org>, Bruce Evans writes:
>> With this format you can specify callouts 68 years into the future
>> with quarter nanosecond resolution, and you can trivially and
>> efficiently compare dur_t's with
>> if (d1 < d2)
>
>This would make a bette
On Wed, 19 Dec 2012, Poul-Henning Kamp wrote:
In message
, Davide Italiano writes:
Right now -- the precision is specified in 'bintime', which is a binary number.
It's not 32.32, it's 32.64 or 64.64 depending on the size of time_t in
the specific platform.
And that is way overkill
In message <50d192e8.3020...@freebsd.org>, Alexander Motin writes:
>Linux uses 32.32 format in their eventtimers code.
(And that is no accident, I know who they got the number from :-)
>But if at some point we want to be able to
>handle absolute wall time, [...]
Then you have other pr
In message
, Davide Italiano writes:
>Right now -- the precision is specified in 'bintime', which is a binary number.
>It's not 32.32, it's 32.64 or 64.64 depending on the size of time_t in
>the specific platform.
And that is way overkill for specifying a callout, at best your clock
has
Hiroki Sato wrote
in <20121207.101917.103513550140980591@allbsd.org>:
hr> Hi all,
hr>
hr> I received many emails asking why
hr> https://pub.allbsd.org/FreeBSD-snapshots/ is stopped working and when
hr> it will recover, so I just wanted to let you know that FreeBSD daily
hr> snapshot bui
On 19.12.2012 12:03, Davide Italiano wrote:
On Wed, Dec 19, 2012 at 1:54 AM, Poul-Henning Kamp wrote:
In message <1355873265.1198.183.ca...@revolution.hippie.lan>, Ian Lepore writes
:
On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
I'm not so sure about the 2^k precision. Yo
On Wed, Dec 19, 2012 at 1:54 AM, Poul-Henning Kamp wrote:
>
> In message <1355873265.1198.183.ca...@revolution.hippie.lan>, Ian Lepore
> writes
> :
>>On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
>
>>I'm not so sure about the 2^k precision. You speak of seconds, but I
>>would be
In message <1355873265.1198.183.ca...@revolution.hippie.lan>, Ian Lepore writes
:
>On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
>I'm not so sure about the 2^k precision. You speak of seconds, but I
>would be worrying about sub-second precision in my work.
It is a bad idea, and
On 19.12.2012 01:37, Ian Lepore wrote:
On Wed, 2012-12-19 at 00:29 +0100, Luigi Rizzo wrote:
On Tue, Dec 18, 2012 at 04:27:45PM -0700, Ian Lepore wrote:
On Tue, 2012-12-18 at 23:58 +0100, Luigi Rizzo wrote:
[top posting for readability;
in summary we were discussing the new callout API trying
28 matches
Mail list logo
