>Number: 147757
>Category: misc
>Synopsis: zoneinfo out of date
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id:
Synopsis: zoneinfo out of date
Responsible-Changed-From-To: freebsd-bugs->edwin
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jun 10 09:30:51 UTC 2010
Responsible-Changed-Why:
IIRC edwin has been looking after zoneinfo.
http://www.freebsd.org/cgi/query-pr.cgi?pr=147757
__
Synopsis: mdconfig(8): mdconfig -l doesn't properly increment device number
State-Changed-From-To: patched->feedback
State-Changed-By: jh
State-Changed-When: Thu Jun 10 15:13:31 UTC 2010
State-Changed-Why:
Can you clarify which revision(s) should be MFCd?
http://www.freebsd.org/cgi/query-pr.cgi?
>Number: 147767
>Category: kern
>Synopsis: route -n change operation with INVARIANTS kernel causes mutex
>radix node head not owned ASSERTION failure
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Qua
>Number: 147769
>Category: kern
>Synopsis: 'ifconfig epair0 create' hangs the whole system
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class:
Synopsis: 'ifconfig epair0 create' hangs the whole system
Responsible-Changed-From-To: freebsd-bugs->bz
Responsible-Changed-By: bz
Responsible-Changed-When: Thu Jun 10 17:59:41 UTC 2010
Responsible-Changed-Why:
epair(4) is mine.
http://www.freebsd.org/cgi/query-pr.cgi?pr=147769
_
The following reply was made to PR bin/143558; it has been noted by GNATS.
From: Eitan Adler
To: bug-follo...@freebsd.org, eitanadlerl...@gmail.com
Cc:
Subject: Re: bin/143558: [patch] Add verbose option to pkill(1)
Date: Thu, 10 Jun 2010 23:43:05 +0300
Changing stdout to stderr.
Index
On 2010-06-04, at 20:47 , Garrett Cooper wrote:
> On Fri, Jun 4, 2010 at 5:28 PM, Mayo Jordanov wrote:
>> Hi Andy,
>>
>> Thanks for the suggestion. I have all my ports mapped directly as you have,
>> and I also tried setting the bios to reserve the IRQs so nothing else gets
>> to use them.
>>