To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Sun, 6 Aug 2000, Mike Silbersack wrote:
If my memory serves me right, someone who was working with doing squid
benchmarks had such patches. Searching through the archive for -net for
squid and/or freebsd 3.2 should find the message - he linked to a page
with performance tuning tips.
Dennis writes:
The change in 4.1 to ether_ifattach() needs a check to see if the device is
already attached.
calling ether_ifattch() with a device already attached will lock up the
system consistently.
No interface should be attached twice, Ethernet or other, right?
So try this patch and
On Sun 2000-08-06 (12:44), Archie Cobbs wrote:
No interface should be attached twice, Ethernet or other, right?
So try this patch and find out which driver is broken.
I think the concern was because the semantics to attach devices changed,
meaning that drivers from before no longer work.
Neil
Neil Blakey-Milner writes:
No interface should be attached twice, Ethernet or other, right?
So try this patch and find out which driver is broken.
I think the concern was because the semantics to attach devices changed,
meaning that drivers from before no longer work.
Hmm.. my
On Sun 2000-08-06 (13:28), Archie Cobbs wrote:
No interface should be attached twice, Ethernet or other, right?
So try this patch and find out which driver is broken.
I think the concern was because the semantics to attach devices changed,
meaning that drivers from before no longer
Here's the site I was thinking of:
http://polygraph.ircache.net/Tips/FreeBSD-3.3/
Beware...their patch does a malloc M_WAITOK in interrupt state. I've
pointed this out to them, but they haven't changed it yet.
Alan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
options MD_NSECT=30
into my kernel for a 150-meg /tmp. But I have done so, and it seems to
make no difference. I must be missing something.
% uname -a
FreeBSD narcissus.net 4.1-STABLE FreeBSD 4.1-STABLE #0: Thu Aug 3
16:58:39 EDT 2000 [EMAIL
On Thu, 3 Aug 2000, Vladimir N. Silyaev wrote:
Bridging on by default may
have nasty side effects for multi-interface machines (especially security
side effects).
It's several ways to work around about that:
- compile kernel without bridging support.
- remove bridge starting code
Has anyone been having their system just plain lock up running vmware? Mine
has been.. (4.1-stable)..
-matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Sun, 6 Aug 2000, Robert Watson wrote:
Un-announced, the vmware port enabled bridging between the ethernet
interfaces on my notebook
This is bad - ethernet segments should not be bridged without explicit
user confirmation, because they are commonly separated precisely for
security reasons.
Hi!
Here is a patch, it seems it fix some bugs in nullfs.
At least i was able to make kernel on nullfs mounted
filesystem.
All results are welcome!
Good luck!
patch
12 matches
Mail list logo
