atom feed22 messages in org.freebsd.freebsd-currentRe: interesting problem
FromSent OnAttachments
Tony JohnsonSep 27, 2000 3:55 pm 
Kris KennawaySep 27, 2000 4:48 pm 
Tony JohnsonSep 27, 2000 5:06 pm 
Kris KennawaySep 27, 2000 5:17 pm 
Alfred PerlsteinSep 27, 2000 5:18 pm 
Greg LeheySep 27, 2000 5:34 pm 
Tony JohnsonSep 27, 2000 6:25 pm 
Alfred PerlsteinSep 27, 2000 6:39 pm 
Thomas David RiversSep 28, 2000 3:32 am 
Tony JohnsonSep 28, 2000 5:53 pm 
Greg LeheySep 28, 2000 6:50 pm 
Tony JohnsonSep 28, 2000 7:44 pm 
Nickolay DudorovSep 28, 2000 8:00 pm 
Greg LeheySep 28, 2000 8:04 pm 
Jordan HubbardSep 28, 2000 9:05 pm 
Alfred PerlsteinSep 29, 2000 12:18 am 
Alfred PerlsteinSep 29, 2000 12:30 am 
Gerhard SittigSep 29, 2000 10:11 am 
Tony JohnsonSep 30, 2000 4:46 pm 
Bill FumerolaSep 30, 2000 5:01 pm 
Matthew ThyerSep 30, 2000 6:53 pm 
Siobhan Patricia LynchOct 2, 2000 6:34 pm 
Subject:Re: interesting problem
From:Gerhard Sittig (Gerh@gmx.net)
Date:Sep 29, 2000 10:11:11 am
List:org.freebsd.freebsd-current

On Thu, Sep 28, 2000 at 21:45 -0500, Tony Johnson wrote:

Since I am complaining then I need to figure out what U have done to make 5.0-CURRENT crash?? Well atleast U admit that U do not know and U do not care. So anyone who is using FreeBSD should also not care?? This is more screwed up then I thought and people @FreeBSD have made this much harder then necessary.

<irony mode on> It seems you finally got it. Somebody thought about "what can I do to break _his_ system? I have some spare time and I feel bored ...". <irony mode off>

But it could be just as well the way the handbook told you: -CURRENT is the place where development takes place. Using -CURRENT you're supposed to know what you do and how to help yourself.

What the participants in the past thread wanted you to do is to provide some more info to make them able to help you better. Claiming "you broke it somewhere - guess where - , fix it or I'll leave" will make you get answers like "feel free to choose the second". Chances are that the "broken code" works for other people. Only you and nobody else can provide the info what exactly breaks things for _you_ -- nobody else has the system to repeat and explore it.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message