"Greg 'groggy' Lehey" wrote:
> On Thursday, 19 June 2003 at 1:29:37 -0700, Terry Lambert wrote:
> > Greg 'groggy' Lehey wrote:
> >> On Wednesday, 18 June 2003 at 2:38:34 -0700, Terry Lambert wrote:
> >>> Greg 'groggy' Lehey wrote:
> Yes, it reminded me of that thread, but wkt was actually re
x27;t think
we'll be running it on a live server just yet, there are lots of cases
where it would be useful even so. And I'm sure that some people will be
inspired to strengthen and extend it.
-Ed
"Roman V. Palagin" <[EMAIL PROTECTED]> wrote:
: On
At Yahoo! we use a lot of shared memory, both in the form of .so's and
for IPC. It would be very useful to be able to accurately measure the
amount of shared and private memory associated with a process, the
number of references to a given shared memory object, resident vs. non-
resident pages, a
I wrote:
: This problem should exist in -current since I think FreeBSD finally drops
^^
That should be "shouldn't". I shouldn't post in a hurry (like I'm doing
now).
-Ed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in th
Exception-handling is broken with -O in -stable, and has been for years.
FreeBSD is one of the few systems that use setjmp/longjmp stack unwinds
to implement exceptions, so when the GCC folks broke that path, it was
never fixed. There are supposedly patches floating around that fix the
problem, b
: Alpha does quake? :-)
It supposedly does under Linux, at least (and if you're talking about
Quake I). Sources at:
http://www.idsoftware.com/q1source/
These sources might need a bit of work, even for Linux, though there
are folks out there who have it running under Linux/Alpha. I'd a
I'm quite pleased with what we, as individuals, will be able to learn
about Eclipse, and the terms of the license don't interfere with that
one bit. But--and this is my *only* objection to the license terms--we
each are prohibited from discussing what we discover, absent Lucent's
written permissi
: It doesn't appear, from their licensing page, these changes are ever
: intended to be released to the FreeBSD project. The license is very
: restrictive about redistribution.
Not only that, but it contains that pernicious gag clause: "You agree not
to release the results of any evaluation of t
If you want to read some more about this in the mainstream press, check
out:
http://www.washingtonpost.com/wp-dyn/business/A23174-2000Feb7.html
http://news.cnet.com/news/0-1005-200-1544455.html
http://news.cnet.com/news/0-1005-200-1543918.html
The NY Times coverage is reasonable as w
Just so there is no misunderstanding.
I wrote:
As for free alternatives--I don't think there are any, especially if
you are looking for something "better" than the current GCC. The
various free C compilers I've seen over the years have been little
better than toys.
Obviously, compi
: I have just upgraded my system to -current w/egcs 2.95.2 and I have
: several problems with it, especially when using optimizations (-O2 and
: such)
Have you reported those problems to <[EMAIL PROTECTED]>? Bugs aren't
very likely to get fixed if no one reports them.
As for free alternatives--
e was .5GB of physical
memory on an N440BX (500MHz P-III) server w/IDE disk.
-Ed Hall <[EMAIL PROTECTED]>
Technical Yahoo,
Yahoo! Inc.
A sample stack trace:
siointr1(c617e000,e8e33f44,c01c1057,0,8010) at siointr1+0xb9
siointr(0)
Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?)
In-Reply-To: Your message of "Tue, 07 Dec 1999 20:01:39 +0800."
<[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
I just reviewed the (so far) working 3.3 test system. I was mistaken
about the 4
: you wrote:
: : I wrote:
: :4) Using a different SCSI driver (Peter managed to get a driver from 4.0
: : hooked up under 3.3, and it survived two days of torture that would
: : have toasted things within an hour using the stock driver; you'll have
: : to ask him for details).
:
: Ed, t
I've confirmed that neither problem exists in 4.0. There are ample
work-arounds, both hardware and software, including just not using 3.3.
No fixes, though, just work-arounds... Workarounds for the NCR/FXP
issue included:
1) Using 2.2.8 (4.0 isn't a production option).
2) Using a different NIC
Mike,
So I'm to blame that my project schedule didn't happen to coincide
with the FreeBSD release schedule? Give me a break. The project hasn't
even gone into production yet. And I think you'll find that your apparent
assumption that no one was told about the problems is equally rash. I
poste
You write:
: we can not identify the specific problem from this message.
: without sufficient information to indentify and hopefully reproduce
: the problem, we can not address it. please provide this information
: if it is available to you. if it is not, please provide us contact
: informa
in Santa Clara and is studying the problem as I
write. More information will be upcoming...
-Ed Hall
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
18 matches
Mail list logo
