At 10:39 PM -0800 2002/11/22, Terry Lambert wrote:
This was kind of my point. Each OS is going to need different things to be easily gathered and reported, and in this case I think we need to enable more information more easily available regarding kernel panics and crash dumps, etc....In terms of kernel problems, the absolutely most useful information is the DDB traceback, followed by a DDB traceback mapped against a debug kernel, followed by a system dump image and a debug kernel, etc.. By default, the system, as distributed, is not setup to supply this.
The MacOS X model does not directly apply here. What we want is the concept of taking the important information and making it as easy as possible to collect and report.
I understand. Indeed, this is the issue that has brought me into this subject -- my wanting to be able to contribute (but not being able to do so through coding), and Mark observing that my skills in beating the hell out of things might be useful in helping to debug the upcoming -RELEASE.Plus we aren't really talking about -CURRENT, we are talking about "5.0-DP2", or "almost 5.0-RC1", if we're being honest.
These kinds of things get all that much more important when we're talking about a -RELEASE coming up.
--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E W+++(--) N+ !w---
O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
