On Sun, Apr 07, 2002 at 03:41:02PM -0700, Justin Christopher wrote: > Ben, I think the point I'm trying to make is that even > if Apple is causing the problem, others have managed > to work around it. > > In any kind of computing project, sometimes you have > to "fix" things that you aren't responsible for. > > I write web pages. Half my day is spent working around > bugs created by browser manufacturers. Even though > those bugs aren't my problem, my pages have to > accomodate them. Why? Because the end user browsing my > pages doesn't care whether it's my fault or Netscape's > fault that the page doesn't work right. It becomes my > fault, and if I don't fix it, my users will find > another site that does.
Yes but you can't fix what you can't reproduce. You're the only one who has reported this. Have you tried running a tcpdump from another machine on your network (or something like it ethereal would be easier). To see what exactly is going on? This might give you a hint as to why it's failing. Also, there are several different DHCP clients in the distribution. dhcpcd, dhcp-client, and pump. Have you tried all of them? Just rpm -e the one you're currently using and rpm -ivh the other one. Constantly complaining about a bug only you are having without providing information to help resolve it, especially when nobody else has the necessary hardware to replicate it isn't going to solve your issue. -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org What difference does it make to the dead, the orphans, and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty and democracy? - Ghandi
