Jeremy Chadwick wrote:
Is anyone aware of the situation where FreeBSD behaves erratically when
a disk is physically removed without atacontrol detach ataX being run
prior to removal (at least on RELENG_7)?
I can confirm this behaviour on FreeBSD 6.2. It sometimes freezes or
panic when I
On Sun, Feb 17, 2008 at 09:35:28AM +0200, David Naylor wrote:
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
On Feb 17, 2008 3:19 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Sat, Feb 16, 2008 at 09:08:38PM -0200, Carlos A. M. dos Santos wrote:
On Feb 16, 2008 7:07 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
Is anyone aware of the situation where FreeBSD behaves erratically when
a disk is
On Feb 17, 2008 4:25 AM, Andrey V. Elsukov [EMAIL PROTECTED] wrote:
17.02.08, 02:08, Carlos A. M. dos Santos [EMAIL PROTECTED]:
precautions prior to yanking the disk. Upon reinsertion, the system
found the disk and I could continue I/O operations on it as if it had
never been
17.02.08, 16:51, Carlos A. M. dos Santos [EMAIL PROTECTED]:
Quoting the message you pointed out:
You might lose cached and in-flight data of course, and userspace
applications may or may not handle the disappearance of their
underlying filesystem with grace and aplomb :)
Perhaps you believe
On Sun, Feb 17, 2008 at 11:03:31AM -0300, Carlos A. M. dos Santos wrote:
On Feb 17, 2008 3:19 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Sat, Feb 16, 2008 at 09:08:38PM -0200, Carlos A. M. dos Santos wrote:
On Feb 16, 2008 7:07 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
Is anyone
On Fri, Feb 15, 2008 at 01:44:13PM +0100, Harald Weis wrote:
Fatal server error:
could not open default font 'fixed'
I've learned two lessons.
1. As a constant user of portupgrade since ages, this time,
before and after the xorg-upgrade procedure, I have carelessly
omitted the `-R' option.
Nathan Lay wrote:
[deleted]
Anyone else experience this strange behavior? It is of note, that if
the card is plugged in before booting, it is properly detected and
attached during boot. It is only when plugging it into a running
FreeBSD 7.0 system for the first time that it behaves this
One line summary:
Too many files in a top-level UFS-2 filesystem directory will cause
a panic on mount.
Kern/Critical/High Priority/SW-Bug
Which FreeBSD Release You Are Using:
6.3-STABLE
Environment (output of uname -a on the problem machine):
FreeBSD wahoo.sd67dfl.org 6.3-STABLE
FYI: The system assigned kern/120781 to this bug report.
IMHO, a security advisory should be issued ASAP.
Jim Bryant wrote:
One line summary:
Too many files in a top-level UFS-2 filesystem directory will cause
a panic on mount.
Kern/Critical/High Priority/SW-Bug
Which FreeBSD Release
Hi Everyone,
The FreeBSD Status Reports for the Fourth Quarter of 2007 are now
available at:
http://www.freebsd.org/news/status/report-2007-10-2007-12.html
Regards,
Brad Davis
___
freebsd-stable@freebsd.org mailing list
in message [EMAIL PROTECTED], wrote Harald Weis
thusly...
2. The `pkg_info -L' check does not certify that the file is
actually in its place
To actually verify the existence of the files, stat(2) them somehow
(will work at least in bourne like shells) ...
pkg_info -L port-name \
| awk
12 matches
Mail list logo
