On Tue, May 20, 2008 at 3:49 PM, Freddie Cash <[EMAIL PROTECTED]> wrote:
> On May 20, 2008 12:08 pm Dick Hoogendijk wrote:
> > On 18 May Zaphod Beeblebrox wrote:
> > > However, when using Norton Ghost to make backup snapshots, the files
> > > (on ZFS) come out corrupt. They are not corrupt on UFS
On May 20, 2008 12:08 pm Dick Hoogendijk wrote:
> On 18 May Zaphod Beeblebrox wrote:
> > However, when using Norton Ghost to make backup snapshots, the files
> > (on ZFS) come out corrupt. They are not corrupt on UFS backed SAMBA
> > service.
>
> Since when does Norton Ghost claim to support ZFS?
On 18 May Zaphod Beeblebrox wrote:
> However, when using Norton Ghost to make backup snapshots, the files
> (on ZFS) come out corrupt. They are not corrupt on UFS backed SAMBA
> service.
Since when does Norton Ghost claim to support ZFS?
If not, how can you expect the files *not* to be corrupted?
Nick Barnes wrote:
> One of our FreeBSD boxes has a SCSI controller and disk, which showed
> problems earlier this week. There was a lot of of chatter from the
> SCSI driver in /var/log/messages and to the console. However, the
> console is unattended and we only discovered the problem subseq
Dave Uhring wrote:
cc -O2 -fno-strict-aliasing -pipe -m32 -march=athlon-mp -DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\"/usr/share/zoneinfo\" -Demkdir=mkdir -I/usr/src/usr.sbin/zic/zdump/.. -I/usr/src/usr.sbin/zic/zdump/../../../lib/libc/stdtime -o
On Tue, May 20, 2008 at 09:24:11AM -0500, Dave Uhring wrote:
> Tried again this morning with a fresh cvsup from cvsup4.freebsd.org and the
> build went to completion.
>
> maxwell# grep -v ^# /etc/make.conf
> CPUTYPE?=k8
> CFLAGS= -O2 -fno-strict-aliasing -pipe -m32
> CXXFLAGS+= -fconserve-space
>
Karel Rous wrote:
My home computer (no internet access, cannot share results :-) is
single processor Athlon 64 on 2250 Mhz/512 KB L2. Visually I have seen
that on stable it doesn't behave as speedily as on FreeBSD number 6. I
have checked utility in subject (which is probably not the best
a
On Tue, May 20, 2008 at 09:24:11AM -0500, Dave Uhring wrote:
> cc -O2 -fno-strict-aliasing -pipe -m32 -march=athlon-mp -DTM_GMTOFF=tm_gmtoff
> -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE
> -DTZDIR=\"/usr/share/zoneinfo\" -Demkdir=mkdir
> -I/usr/src/usr.sbin/zic/zdump/..
> -I/usr/
On 20 May 2008, at 14:31, Dave Uhring wrote:
On Tue, May 20, 2008 at 12:54:59PM +0100, Doug Rabson wrote:
On 20 May 2008, at 12:25, Dave Uhring wrote:
On Tue, May 20, 2008 at 08:50:14AM +0100, Doug Rabson wrote:
In this, your build is explicitly using '/usr/bin/gcc' for the
build
which
Tried again this morning with a fresh cvsup from cvsup4.freebsd.org and the
build went to completion.
maxwell# grep -v ^# /etc/make.conf
CPUTYPE?=k8
CFLAGS= -O2 -fno-strict-aliasing -pipe -m32
CXXFLAGS+= -fconserve-space
MAKE_SHELL?=sh
COPTFLAGS= -O -pipe
INSTALL=install -C
MTREE_FOLLOWS_SYMLINKS=
On Tue, May 20, 2008 at 12:54:59PM +0100, Doug Rabson wrote:
>
> On 20 May 2008, at 12:25, Dave Uhring wrote:
>
>> On Tue, May 20, 2008 at 08:50:14AM +0100, Doug Rabson wrote:
>>>
>>> In this, your build is explicitly using '/usr/bin/gcc' for the build
>>> which
>>> is not the way buildworld norma
On Mon, May 19, 2008 at 11:15 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Mon, May 19, 2008 at 10:24:43PM +1200, James Butler wrote:
>> Second problem: When the system panics, I don't get a dump (or
>> textdump for that matter, when I turn them on); in the boot messages,
>> I see "kernel du
On Tue, May 20, 2008 at 01:33:15PM +1000, Mark Andrews wrote:
>
> And when tested does behave the way you describe.
>
> Mark
>
> drugs:9.5.x 13:30 {4371} % bash
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ printenv | grep FOO
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ FOO=ll
> [EMAIL PROTECTED] ~/cvs/9.
On 20 May 2008, at 01:02, Dave Uhring wrote:
On Mon, May 19, 2008 at 06:46:41PM -0500, Jeffrey Goldberg wrote:
On May 19, 2008, at 1:21 PM, Dave Uhring wrote:
In any case, that problem has been solved by putting the updated
header
files
in /usr/include/sys and will be properly fixed when I
On 2008-May-19 21:51:30 -0500, Dave Uhring <[EMAIL PROTECTED]> wrote:
>On Tue, May 20, 2008 at 11:58:03AM +1000, Mark Andrews wrote:
>>
>> > # export CFLAGS=""
>>
>> This does NOT remove CFLAGS from the environment.
>
>It does when you shell is bash.
As Mark pointed out, this just means bas
15 matches
Mail list logo