On 14/02/2008, Oliver Fromme [EMAIL PROTECTED] wrote:
David Naylor wrote:
It is a strange problem, normal installworld works fine, but somehow
the duplicate manpages result in a failure when installing with
DESTDIR=, here are some possible reasons:
1) I use tmpfs when using DESTDIR
On 14/02/2008, Oliver Fromme [EMAIL PROTECTED] wrote:
David Naylor wrote:
It is a strange problem, normal installworld works fine, but somehow
the duplicate manpages result in a failure when installing with
DESTDIR=, here are some possible reasons:
1) I use tmpfs when using
On 13/02/2008, Rong-En Fan [EMAIL PROTECTED] wrote:
On Wed, Feb 13, 2008 at 10:52:50AM +0100, Christian Brueffer wrote:
On Wed, Feb 13, 2008 at 11:15:29AM +0200, David Naylor wrote:
Hi,
When doing an installworld DEST=? it fails twice when trying to
install duplicate man pages
Hi,
Building the kernel with CFLAGS=-Os breaks when compiling module
scsi_low. Sorry no output available.
Placing CFLAGS+= -O in the Makefile fixes the problem. Last build
with -O2 did work (for everything, world, kernel and ports).
From my research it appears the -Os produces code faster
Hi,
With a recent (this weekend) cvsup of FreeBSD7 I have tried to do a:
# make installworld DESTDIR=/tmp/build
however it fails as follows:
=== lib/ncurses (install)
=== lib/ncurses/ncurses (install)
[Lots of lines removes]
/tmp/build/usr/share/man/man3/tigetstr.3.gz -
On 09/11/2007, Jeremy Chadwick [EMAIL PROTECTED] wrote:
Okay, so it's probably that area of the disk which has some problem...
It may but I can confirm that FreeBSD is not handling it properly (see below)
There's a free utility called HDTune which has a sector scanner which
explicitly looks
Hi,
I have been using this laptop for a few months now with FreeBSD without any
problems with the hard disk however today as I installed editors/vim the
system crashed (without a core dump or any message).
When ever the system boots (and proceeds to do a fsck on ad0e (/usr)) it
also crashes
On 08/11/2007, Jeremy Chadwick [EMAIL PROTECTED] wrote:
Sounds like something mechanical inside of the disk is failing, or
possibly the drive firmware is somewhat buggy when it comes to handling
bad blocks. What brand/model of hard disk is this? atacontrol output
would suffice. I'm just
