On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file
I run several boxes based on FreebSD 9.0-BETA1/amd64, compiled with
clang. Since yesterday, I run on all of these
machines into strange situations: buildworld won't build anymore, it
fails always on all boxes at
the very same position as showed by the error message below. I can build
and
Hello all!
I have:
uname -a
FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806: Sat Aug 13
11:17:49 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9 amd64
After update source code r224728 to r224806 - my kernel smash when i
start the game WorldOfGoo.
My
On Sat Aug 13 11, fidaj wrote:
Hello all!
I have:
uname -a
FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806: Sat Aug 13
11:17:49 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9 amd64
After update source code r224728 to r224806 - my kernel smash when i
On Sat Aug 13 11, fidaj wrote:
Hello all!
I have:
uname -a
FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806: Sat Aug 13
11:17:49 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9 amd64
After update source
On Sat, Aug 13, 2011 at 05:39, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
I run several boxes based on FreebSD 9.0-BETA1/amd64, compiled with clang.
Since yesterday, I run on all of these
machines into strange situations: buildworld won't build anymore, it fails
always on all boxes at
Hartmann, O. ohart...@zedat.fu-berlin.de writes:
I run several boxes based on FreebSD 9.0-BETA1/amd64, compiled with
clang. Since yesterday, I run on all of these
machines into strange situations: buildworld won't build anymore, it
fails always on all boxes at
the very same position as
Here's a followup with some pics I was able to take. Sorry about the
quality :-(
http://feld.me/stuff/freebsd/geom_mirror_9/
Cheers,
Mark
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Hi,
I have been testing a scratch filesystem, with soft updates journaling enabled.
I have been seeing one of these two panics:
panic: ino 0xc5d0f600(0x3C8209) 14147, 7047 != 14098
and
panic: Bad link elm 0xc4d7cd00 prev-next != elm
If I disable soft updates journaling, I do not see these
I've been building a release about once a week on current. The last
successful build was on august 8 but don't know when this started but
in the last few days.
I am building on
# uname -a
FreeBSD Home.EnContacto.net 9.0-BETA1 FreeBSD 9.0-BETA1 #16: Sat Aug
13 05:09:17 CDT 2011
On 13 August 2011 16:37, eculp ec...@encontacto.net wrote:
I've been building a release about once a week on current. The last
successful build was on august 8 but don't know when this started but in the
last few days.
I am building on
# uname -a
FreeBSD Home.EnContacto.net 9.0-BETA1
On Sat, Aug 13, 2011 at 8:52 AM, Chris Rees cr...@freebsd.org wrote:
On 13 August 2011 16:37, eculp ec...@encontacto.net wrote:
I've been building a release about once a week on current. The last
successful build was on august 8 but don't know when this started but in the
last few days.
I
On Sat, Aug 13, 2011 at 8:37 AM, eculp ec...@encontacto.net wrote:
I've been building a release about once a week on current. The last
successful build was on august 8 but don't know when this started but in the
last few days.
I am building on
# uname -a
FreeBSD Home.EnContacto.net
Test Rat ttse...@gmail.com writes:
[...]
Remaking `cat'
Results of making cat:
clang -O2 -pipe -O3 -Qunused-arguments -fcolor-diagnostics
-march=native -g -fno-omit-frame-pointer -std=gnu99 -fstack-protector
-Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter
On Sat, Aug 13, 2011 at 9:09 AM, Garrett Cooper yaneg...@gmail.com wrote:
On Sat, Aug 13, 2011 at 8:37 AM, eculp ec...@encontacto.net wrote:
I've been building a release about once a week on current. The last
successful build was on august 8 but don't know when this started but in the
last
hi there,
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique directory name for the old
kernel?
something like
On 13 August 2011 20:51, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique
On Sat Aug 13 11, Chris Rees wrote:
On 13 August 2011 20:51, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as
the
results of
On Aug 13, 2011, at 12:51 PM, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique
On Sat Aug 13 11, Garrett Cooper wrote:
On Aug 13, 2011, at 12:51 PM, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as
the
- Original Message -
From: Alexander Best arun...@freebsd.org
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique directory name
On Aug 13, 2011, at 1:15 PM, Alexander Best arun...@freebsd.org wrote:
On Sat Aug 13 11, Garrett Cooper wrote:
On Aug 13, 2011, at 12:51 PM, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to
I tried to mount a card from my phone (it's quicker to copy directly
than through USB) but I get this .. what am I missing here?
Aug 13 16:53:37 toshi kernel: sdhci0-slot0: Card inserted
Aug 13 16:53:37 toshi kernel: mmc0: MMC/SD bus on sdhci0
Aug 13 16:53:37 toshi kernel: mmc0: Probing bus
Aug
in the following kernel configuration (notably without ``device
bfp''), i get the following kernel build error. which is either a bug,
or not; just posting in case it's in someone's interest.
build log snippet begins
=== pfsync (all)
cc -O2 -fno-strict-aliasing -pipe
24 matches
Mail list logo
