Hi
I've had problems before with GEOM mirror and my SATA drives, and
i've posted about it here before too. The solution seemd to be a
change of motherboard, this reduced the crash very much (and also the
speeds archieved was greatly improved, from 10-15MB/s to 40-50MB/s..).
However after
Any hints on this available? Suggestions, more info, anything else?
On 5/15/06, m m [EMAIL PROTECTED] wrote:
On 5/14/06, Alexander Kabaev [EMAIL PROTECTED] wrote:
On Thu, 11 May 2006 20:57:20 -0400
m m [EMAIL PROTECTED] wrote:
I am writing in regard to PR at
On Wed, May 17, 2006 at 01:22:59PM +0300, Dmitry Pryanishnikov wrote:
Hello!
On Tue, 16 May 2006, Colin Percival wrote:
Personally, since FreeBSD 4.11 will reach its EoL about 8 months
from now, and the 4.x-[56].x upgrade path is non-trivial, I
recommend installing FreeBSD 6.1 instead.
On Mon, May 15, 2006 at 07:35:53PM -0600, Brett Glass wrote:
Is there a server currently furnishing snapshots of the FreeBSD 4.11 security
branch? We have some servers running various 4.x versions that might not be
happy with 6.x due to memory requirements. They also might have slower file
Hi,
got the following trap on an i386 SMP system running with recent RELENG_6
sources. The system was doing copies from/to geli encrypted disks,
using hifn(4) hardware crypto.
Core and debug kernel are available, but the trace appears to be
corrupted.
- Christian
Fatal trap 12: page fault
Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last month), it
shouldn't be a problem to do a 4.12 release as a last gasp to tide us over
until September. (Hopefully, Colin and the summer of code folks can
work on performance enhancements to the network stack, UFS2, and the hard
On Sun, May 21, 2006 at 09:04:05PM +0200, Christian Brueffer wrote:
Core and debug kernel are available, but the trace appears to be
corrupted.
Sorry to hijack your thread, but I'm also seeing corrupted backtraces
from kgdb involving generic_bcopy().
Is there something about its asm
On Sun, 2006-May-21 13:20:24 -0600, Brett Glass wrote:
Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last month),
it
shouldn't be a problem to do a 4.12 release as a last gasp to tide us over
Maybe for April 1st next year - though novel April Fools Day jokes are
always much
On Sun, May 21, 2006 at 01:13:35PM -0400, m m wrote:
Any hints on this available? Suggestions, more info, anything else?
On 5/15/06, m m [EMAIL PROTECTED] wrote:
On 5/14/06, Alexander Kabaev [EMAIL PROTECTED] wrote:
On Thu, 11 May 2006 20:57:20 -0400
m m [EMAIL PROTECTED] wrote:
I
On Sun, May 21, 2006 at 01:20:24PM -0600, Brett Glass wrote:
Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last month),
it
shouldn't be a problem to do a 4.12 release as a last gasp to tide us over
until September. (Hopefully, Colin and the summer of code folks can
work
On Sun, 21 May 2006 13:13:35 -0400
m m [EMAIL PROTECTED] wrote:
Any hints on this available? Suggestions, more info, anything else?
On 5/15/06, m m [EMAIL PROTECTED] wrote:
On 5/14/06, Alexander Kabaev [EMAIL PROTECTED] wrote:
On Thu, 11 May 2006 20:57:20 -0400
m m [EMAIL PROTECTED]
On Mon, May 22, 2006 at 10:03:33AM +1200, Andrew Thompson wrote:
On Sun, May 21, 2006 at 01:20:24PM -0600, Brett Glass wrote:
Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last
month), it
shouldn't be a problem to do a 4.12 release as a last gasp to tide us
over
Hi,
Sorry this is only a 'me too' message...
On Sun, 21 May 2006 11:16:14 +0200,
Johan Ström [EMAIL PROTECTED] said:
May 21 02:04:58 elfi kernel: ad6: FAILURE - device detached
May 21 02:04:58 elfi kernel: subdisk6: detached
May 21 02:04:58 elfi kernel: ad6: detached
May 21 02:04:58
On Sun, May 21, 2006 at 06:22:34PM -0400, m m wrote:
n 5/21/06, Konstantin Belousov [EMAIL PROTECTED] wrote:
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x294c0ad8 in __do_global_dtors_aux () from
Dear FreeBSD users and system administrators,
While the FreeBSD Security Team has traditionally been very good at
investigating and responding to security issues in FreeBSD, this only
solves half of the security problem: Unless users and administrators
of FreeBSD systems apply the security
On May 21, 2006, at 11:55 , Colin Percival wrote:
The Security Team has been concerned for some time by anecdotal
reports
concerning the number of FreeBSD systems which are not being promptly
updated or are running FreeBSD releases which have passed their End of
Life dates and are no longer
On May 21, 2006, at 20:55, Colin Percival wrote:
If you administrate system(s) running FreeBSD (in the broad sense
of are
responsible for keeping system(s) secure and up to date), please
visit
http://people.freebsd.org/~cperciva/survey.html
and complete the survey below before May 31st,
On Sun, 21 May 2006, Colin Percival wrote:
In order to better understand
which FreeBSD versions are in use, how people are (or aren't) keeping
them updated, and why it seems so many systems are not being updated, I
have put together a short survey of 12 questions.
I applaud this survey,
Doug Hardie wrote:
On May 21, 2006, at 20:55, Colin Percival wrote:
If you administrate system(s) running FreeBSD (in the broad sense of
are
responsible for keeping system(s) secure and up to date), please visit
http://people.freebsd.org/~cperciva/survey.html
and complete the survey below
Brent Casavant wrote:
On Sun, 21 May 2006, Colin Percival wrote:
In order to better understand
which FreeBSD versions are in use, how people are (or aren't) keeping
them updated, and why it seems so many systems are not being updated, I
have put together a short survey of 12 questions.
I
20 matches
Mail list logo
