>> Please, fix 4 times repetition of all its content in
>> stable/7/cddl/compat/opensolaris/include/libshare.h.
>>
>
> The same:
> stable/7/sys/cddl/compat/opensolaris/sys/pathname.h
> stable/7/sys/cddl/compat/opensolaris/sys/kidmap.h
> stable/7/sys/cddl/compat/opensolaris/sys/file.h
>
fixed by r1
2009/5/21 pluknet :
> 2009/5/21 Kip Macy :
>> On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote:
>>> I will be MFC'ing the newer ZFS support some time this afternoon. Both
>>> world and kernel will need to be re-built. Existing pools will
>>> continue to work without upgrade.
>>>
>>>
>>> If you choo
2009/5/21 Kip Macy :
> On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote:
>> I will be MFC'ing the newer ZFS support some time this afternoon. Both
>> world and kernel will need to be re-built. Existing pools will
>> continue to work without upgrade.
>>
>>
>> If you choose to upgrade a pool to take
On Wed, May 20, 2009 at 05:55:29PM -0400, Michael L. Squires wrote:
> I started having speed problems after shifting from 7.1-STABLE to
> 7.1-PRERELEASE. They have continued with 7.2-STABLLE.
>
> Reverting to the 7.1-STABLE kernel eliminated the problem.
>
> After downloading 7.2-STABLE from cv
TB --- 2009-05-20 23:21:28 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-05-20 23:21:28 - starting RELENG_7 tinderbox run for amd64/amd64
TB --- 2009-05-20 23:21:28 - cleaning the object tree
TB --- 2009-05-20 23:22:02 - cvsupping the source tree
TB --- 2009-05-20 23:22:02 - /usr/
On Wed, May 20, 2009 at 5:00 PM, Kip Macy wrote:
>> Not really a problem but a question: Is the v13 on-disk format
>> exactly the same as that used by Solaris/Opensolaris?
>
> It is supposed to be. The sources are the same. However, I have not
> tested interoperability.
>
>
>> Does this make
>> i
>
> Unfortunately not a lot but we can do the following:
>
> - Donate some hardware (Fibre Channel HBAs) to the FreeBSD project (paid
> from my pocket, not my employer's one);
> - Donate some money (paid from my employer's pocket, if I can demonstrate
> that this can help us to save big bucks on hi
> Not really a problem but a question: Is the v13 on-disk format
> exactly the same as that used by Solaris/Opensolaris?
It is supposed to be. The sources are the same. However, I have not
tested interoperability.
> Does this make
> it possible to have a ZFS-only dual boot system running FreeBS
On Wed, May 20, 2009 at 4:43 PM, Kip Macy wrote:
> On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote:
>> I will be MFC'ing the newer ZFS support some time this afternoon. Both
>> world and kernel will need to be re-built. Existing pools will
>> continue to work without upgrade.
>>
>>
>> If you choo
On Wed, May 20, 2009 at 2:59 PM, Kip Macy wrote:
> I will be MFC'ing the newer ZFS support some time this afternoon. Both
> world and kernel will need to be re-built. Existing pools will
> continue to work without upgrade.
>
>
> If you choose to upgrade a pool to take advantage of new features you
On Wed, May 20, 2009 at 3:11 PM, Mike Tancsa wrote:
> At 05:59 PM 5/20/2009, Kip Macy wrote:
>>
>> If you choose to upgrade a pool to take advantage of new features you
>> will no longer be able to use it with sources prior to today. 'zfs
>> send/recv' is not expected to inter-operate between diff
> To Pete: Did you overwritten the if_bce.c/if_bcereg.h with previous
> - -STABLE code or was it from 7.1-RELEASE?
I am using code from a csup with the date set to
2009.03.30.23.59.59, which is immediately before the
changes (the one which doesnt work is a csup with
a date of 2009.03.31.23.59.59).
At 05:59 PM 5/20/2009, Kip Macy wrote:
If you choose to upgrade a pool to take advantage of new features you
will no longer be able to use it with sources prior to today. 'zfs
send/recv' is not expected to inter-operate between different pool
versions.
Hi,
Thanks for working on ZFS! I
I will be MFC'ing the newer ZFS support some time this afternoon. Both
world and kernel will need to be re-built. Existing pools will
continue to work without upgrade.
If you choose to upgrade a pool to take advantage of new features you
will no longer be able to use it with sources prior to toda
I started having speed problems after shifting from 7.1-STABLE to
7.1-PRERELEASE. They have continued with 7.2-STABLLE.
Reverting to the 7.1-STABLE kernel eliminated the problem.
After downloading 7.2-STABLE from cvsup.freebsd.org at about 10:40 AM EST
on 5/20/2009, doing a buildworld/buildker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
pluknet wrote:
> 2009/5/19 Pete French :
>> Just wondering if there was any update to this ? I seem to
>> be the only one who actually has the problem, but I have
>> gone as far as I can trying to diagnose it unless someone
>> can send me patches to te
David La Croix wrote:
I experienced the same problem (same motherboard) ...both amd64
and i386 versions did the exact same thing ...
I got the installer to work by going into the BIOS and disabling the
onboard firewire.
Well, I can confirm that disabling on-board FireWire helps (though it
> Perhaps there's no /etc/exports file? While exporting shared zfs file
> systems doesn't require this, it looks like /etc/rc.d/mountd requires
> the file to be present.
>
>
> On May 19, 2009, at 2:33 PM, Zaphod Beeblebrox wrote:
>
> > 2009/5/18 Михаил Кипа
> >
> >> I have two servers with
On Wed, 2009-05-20 at 17:26 +0200, Paul B. Mahol wrote:
> On 5/20/09, Robert Noland wrote:
> > On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote:
> >> On 5/20/09, Robert Noland wrote:
> >> > On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
> >> >> > So, zapping is off by default now in 1.6.
On 5/20/09, Robert Noland wrote:
> On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote:
>> On 5/20/09, Robert Noland wrote:
>> > On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
>> >> > So, zapping is off by default now in 1.6.x. If you want it, add
>> >> Option
>> >> > "DontZap" "off". The
Quoting Robert Noland :
On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote:
On 5/20/09, Robert Noland wrote:
> On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
>> > So, zapping is off by default now in 1.6.x. If you want it, add
>> Option
>> > "DontZap" "off". The cross hatch is also go
Quoting Robert Noland :
On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
> So, zapping is off by default now in 1.6.x. If you want it, add
Option
> "DontZap" "off". The cross hatch is also gone, that is what the
-retro
> option is supposed to do. The session leader in a failsafe twm
session
On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote:
> On 5/20/09, Robert Noland wrote:
> > On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
> >> > So, zapping is off by default now in 1.6.x. If you want it, add
> >> Option
> >> > "DontZap" "off". The cross hatch is also gone, that is what t
On Tuesday 12 May 2009 12:10:25 pm Riccardo Torrini wrote:
> On Tue, May 12, 2009 at 11:44:20AM -0400, John Baldwin wrote:
>
> > If you can get a stack trace, that would be most helpful.
> > My guess is that the recovery thread is holding the mpt lock
> > and calling some CAM routine which attempt
on 20/05/2009 15:32 John Baldwin said the following:
> On Wednesday 20 May 2009 8:09:46 am Andriy Gapon wrote:
>> This is a patch that I currently use to fix the problem for myself - both 2KB
>> structs are allocated on the heap.
>> I am not sure what is the proper style for chained calls using cha
On 5/20/09, Robert Noland wrote:
> On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
>> > So, zapping is off by default now in 1.6.x. If you want it, add
>> Option
>> > "DontZap" "off". The cross hatch is also gone, that is what the
>> -retro
>> > option is supposed to do. The session leader in
On Wednesday 20 May 2009 8:09:46 am Andriy Gapon wrote:
>
> This is a patch that I currently use to fix the problem for myself - both 2KB
> structs are allocated on the heap.
> I am not sure what is the proper style for chained calls using chained
> if-else,
> but I think that the chaining is the
On Wed, 2009-05-20 at 14:25 +1200, Jonathan Chen wrote:
> Hi all,
>
> I'm running 7.2-STABLE/amd64 on a Dell 830, and have been attempting to get
> XOrg working with the "nv" driver. However, it fails with:
>
> X.Org X Server 1.6.1
> Release Date: 2009-4-14
> X Protocol Version 11, Revision 0
>
On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
> > So, zapping is off by default now in 1.6.x. If you want it, add
> Option
> > "DontZap" "off". The cross hatch is also gone, that is what the
> -retro
> > option is supposed to do. The session leader in a failsafe twm
> session
> > is the left
Quoting Chris H :
Greetings...
Quoting Jonathan Chen :
Hi all,
I'm running 7.2-STABLE/amd64 on a Dell 830, and have been attempting
to get XOrg working with the "nv" driver. However, it fails with:
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operat
Greetings...
Quoting Jonathan Chen :
Hi all,
I'm running 7.2-STABLE/amd64 on a Dell 830, and have been attempting
to get XOrg working with the "nv" driver. However, it fails with:
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD
This is a patch that I currently use to fix the problem for myself - both 2KB
structs are allocated on the heap.
I am not sure what is the proper style for chained calls using chained if-else,
but I think that the chaining is the best way to organize that piece of code, so
that there is only one e
On 20 May 2009, at 1:01, Kip Macy wrote:
I would recommend that you use the ZFS_MFC branch - it is the same as
what will be in RELENG_7 tomorrow afternoon.
This is great news, and given the testing it should be no problem I
feel...
After setting vm.kmem_size to the recommended minimum I r
I experienced the same problem (same motherboard) ...both amd64
and i386 versions did the exact same thing ...
I got the installer to work by going into the BIOS and disabling the
onboard firewire.
On Tue, May 12, 2009 at 4:32 PM, martinko wrote:
> Dan Nelson wrote:
>>
>> In the last episod
On Tuesday 19 May 2009, Mario Pavlov wrote:
> Hi,
> I tired CURRENT and it's working for me :)
> I only have one small issue...
> when I unplug the reader pcscd goes to some sort of infinite loop
> it would print this forever:
>
> 48111939 ccid_usb.c:491:WriteUSB() usb_bulk_write(/dev/usb//dev/ugen
35 matches
Mail list logo
