On 02/09/2012 01:04, Tim Kientzle wrote:
> Will new versions of pkgng support old packages?
>
> Some folks maintain their own package repositories and
> will get rather grumpy if an update to pkgng requires them
> to rebuild their entire repository.
There's a distinction between the format of pkg
I have patches to add locking for the bt(4) driver if anyone is able to
test them. The patches should apply to 8 or 9 as well as HEAD. Please
enable INVARIANTS during at least initial testing. Thanks.
http://www.FreeBSD.org/~jhb/patches/bt_locking.patch
--
John Baldwin
___
On Sep 1, 2012, at 12:40 PM, Matthew Seaman wrote:
> On 01/09/2012 18:43, Tijl Coosemans wrote:
>> In this scenario the ports tree needs to keep support for older releases,
>> but that's a consequence of the fact that there's only one ports tree for
>> all releases. Somewhere in between the ports
On Sat, Sep 01, 2012 at 08:40:03PM +0100, Matthew Seaman wrote:
> On 01/09/2012 18:43, Tijl Coosemans wrote:
> > In this scenario the ports tree needs to keep support for older releases,
> > but that's a consequence of the fact that there's only one ports tree for
> > all releases. Somewhere in bet
On Sat, Sep 1, 2012 at 12:40 PM, Matthew Seaman wrote:
> On 01/09/2012 18:43, Tijl Coosemans wrote:
>> In this scenario the ports tree needs to keep support for older releases,
>> but that's a consequence of the fact that there's only one ports tree for
>> all releases. Somewhere in between the po
-- Eir Nym
On 1 September 2012 03:12, Dimitry Andric wrote:
> On 2012-08-30 18:43, Eir Nym wrote:
>>
>> On 30 August 2012 20:16, Dimitry Andric wrote:
>
> ...
>
>>> It seems the WERROR= in the xfs module Makefile was right there from the
>>> start, but it was never removed. I have compiled it
On 01/09/2012 18:43, Tijl Coosemans wrote:
> In this scenario the ports tree needs to keep support for older releases,
> but that's a consequence of the fact that there's only one ports tree for
> all releases. Somewhere in between the ports and the various releases there
> has to be some form enca
On 9/1/2012 7:43 PM, Tijl Coosemans wrote:
On 31-08-2012 14:22, Baptiste Daroussin wrote:
On Fri, Aug 31, 2012 at 08:10:50AM -0400, John Baldwin wrote:
On Friday, August 31, 2012 5:59:10 am Baptiste Daroussin wrote:
On Thu, Aug 30, 2012 at 01:02:06PM -1000, Doug Barton wrote:
I agree with Joh
On 31-08-2012 14:22, Baptiste Daroussin wrote:
> On Fri, Aug 31, 2012 at 08:10:50AM -0400, John Baldwin wrote:
>> On Friday, August 31, 2012 5:59:10 am Baptiste Daroussin wrote:
>>> On Thu, Aug 30, 2012 at 01:02:06PM -1000, Doug Barton wrote:
I agree with John on all counts here. Further, the
Hi!
> Please file a PR against rc ASAP.
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/117711
> Looks like Matteo Riondato had created a patch for the problem in 2008:
>
> http://people.freebsd.org/~matteo/diff/117711rpcbind.diff
>
> but he never received any feedback from Carl
Hi, Gleb.
GS> Can you please provide your full host configuration: rc.conf, firewall
GS> rules if there are any?
How to repeat:
ifconfig rl0 add 192.168.0.2/24
route add default 192.168.1.1
192.168.1.1 is not on my LAN 192.168.0.0/24
FreeBSD must log right error messages so people can understoo
Still working on patches for drivers from the last century.
The latest installment is a patch for aic(4). It should
apply to 8 and 9 as well as HEAD. Please ensure INVARIANTS
is enabled during testing.
http://www.FreeBSD.org/~jhb/patches/aic_locking.patch
--
John Baldwin
__
12 matches
Mail list logo
