Date: Sat, 4 Dec 1999 22:09:17 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Wes Peters <wes@softweyr.com> Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Message-ID: <199912050609.WAA59355@apollo.backplane.com> References: <41264.944342473@zippy.cdrom.com> <199912042149.NAA57545@apollo.backplane.com> <3849BE44.EF52448C@softweyr.com> <199912050453.UAA58889@apollo.backplane.com> <3849FC0D.E29DF371@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:Oh hell, how did I manage to fall into alt.philosophy.est? Wait a minute,
:this *is* freebsd-hackers. It's *you* who is off topic, and off base.
:
:As penance, you get to go read everything ever posted to a freebsd mailing
:list by JMJr.
:
:People do change, and I continually await improvement from the lot of 'em.
:I'm rarely pleasantly surprised.
:
:--
: "Where am I, and what am I doing in this handbasket?"
:
:Wes Peters Softweyr LLC
It's not really philosophy, just common sense. If you want to affect
a change then, believe me, the way you are going about it isn't helping.
If you post responses that only perpetuate the problem, then you are going
to be waiting a *long* time.
Now, this probably seems a bit jaded coming from me since my dealings with
core have spilled over into the lists, but that's a different situation.
Core has been holding an axe over my head for 11 months with arbitrary
commit restrictions and can't come up with a straight answer for why they
are still doing it. Perhaps if they take away the axe or state in a clear
and concise and non-vague manner why the axe is there and what I can do
to have it taken away, they might be pleasantly surprised. Until that
happens though nothing will change. The self perpetuation of the problem
in my case is that axe and since I don't control the axe core has created
a self fullfilling prophesy for as long as they continue to hold it over
me.
In this case there is no axe, so there is no real reason why the problem
should continue to perpetuate, yet it does and you have to consider the
possibility that you are partially to blame and fix that part before
you can expect to see any change realized by the other party.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912050609.WAA59355>