In message [EMAIL PROTECTED], Chad David writes:
On Fri, Oct 19, 2001 at 05:00:16PM +0200, Poul-Henning Kamp wrote:
Sounds like the bug is the md driver cloning md10ec which it shouldn't
do. This bug must naturally be in md_clone(), but I don't have the
minutes right now to hunt it down.
úÄÒÁ×ÓÔ×ÕÊÔÅ, freebsd-current.
--
Best regards,
Vadim Zaychenko
mailto:[EMAIL PROTECTED]
ICQ: 92369162
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
íÁÌÏÉÚ×ÅÓÔÎÙÊ ÓÅÄØÍÏÊ ÚÁËÏÎ îØÀÔÏÎÁ: ðÔÉÃÁ × ÒÕËÅ ÂÅÚÏÐÁÓÎÅÊ, ÞÅÍ ÎÁÄ ÇÏÌÏ×ÏÊ.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Mon, 22 Oct 2001, Harry Starr wrote:
The problem is the new inclusion of ipfilter stuff.
Make will change directory to .OBJDIR if it exists, and it does NOW that
there is an ipfilter SUBDIR.
The support for a separate object tree unfortunately gives separate
object directories even to
For small devices (unclear definition of small), the following (changed
from swap to vnode from the mdconfig man page example) is broken:
sproing# dd if=/dev/zero of=foo bs=1024000 count=1
1+0 records in
1+0 records out
1024000 bytes transferred in 0.234674 secs (4363498 bytes/sec)
sproing#
On Mon, 22 Oct 2001 14:23:17 -0400 (EDT), Robert Watson wrote:
For small devices (unclear definition of small), the following (changed
from swap to vnode from the mdconfig man page example) is broken:
sproing# dd if=/dev/zero of=foo bs=1024000 count=1
1+0 records in
1+0 records out
Just as a data point, vmware 2.0.4.1142 under 4.4-STABLE as host boots
4.2-4.4-STABLE guest extremely slowly, and freezes at the 'mounting root'
line under 5.0-CURRENT, as of 10/21/2001.
I left it alone for five hours under -CURRENT, no way it would move.
Brad
// -- http://www.BRAD-X.com/ --
On Thu, 18 Oct 2001, Terry Lambert wrote:
In the non-LRP case, the percentage drop in interrupt overhead
is ~10% (as has been observed by others). THis makes sense,
too, if you consider that NETISR driving of receives means
less time in interrupt processing. If we multiply the 15%
(100%
On Mon, Oct 22, 2001 at 11:58:23AM +1000, Harry Starr wrote:
It seems to be nigh impossible to build a previous release on -current.
Problems include incomplete cross tool building, header files, and of
course, device support, in particular differences
between the old vn stuff, and the new
Problems include incomplete cross tool building, header files, and
of course, device support, in particular differences between the
old vn stuff, and the new md device.
kris I build worlds in a jail populated with the target release so there's
kris no problems with this.
That's true, maybe
- Original Message -
From: Makoto MATSUSHITA [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 23, 2001 10:21 AM
Subject: Re: RELENG_4 builds on -current
That's true, maybe he only wanna say about 4-stable make release
with (recent) 5-current box in the latter half of
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, Oct 23, 2001 at 12:08:17PM +1000, Harry Starr wrote:
- Original Message -
From: Makoto MATSUSHITA [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 23, 2001 10:21 AM
Subject: Re: RELENG_4 builds on -current
That's true, maybe he only wanna say about
On Fri, 19 Oct 2001, Mark Peek wrote:
MPYes, it does appear to be due to this commit. The first address on the
MPinterface queue has an address of 0.0.0.0. Here's a patch that works for
MPme to block the messages. I'm guessing at the correct behavior so use at
MPyour own risk. At least the
Doctors,
Lawyers, Business Owners, Home Makers, Students, and More!
What Do ALL These People Have In Common?
They all have been opened up to a NEW way of thinking!
Our organization has helped people from all walks of life earn from 10k to 50k per
14 matches
Mail list logo