Brian Hall wrote:
>
> There hasn't been much traffic on the LKCD list lately, and it has been awhile
> since the last new release. I'm still working on getting lcrash working on
> Alpha, but I saw no replies to my last couple of questions. Is the project not
> being worked on as much now, or...? I understand that most (if not all) of the
> developers working on this also have other tasks.
Hi Brian,
I have been out of town (and off line) for the last week and a half. I'll have
to go back and see what questions you refer to. As for current status, Matt and
I ARE a bit behind in posting a status message. We have made a number of changes
and are preparing a new patch (for 2.2.14). We have been spending most of our
time (Matt in the kernel and myself with lcrash) porting LKCD to 2.3.x. I know
that from an lcrash point of view, you can grab the latest source (for 2.2 and
2.3) from SourceForge (project lkcd). With the 2.3 version of lcrash, you can
run
lcrash against a live system and can now generate a compressed dump from live
system
memory -- without crashing the system (I'm going to back port this feature to
2.2).
Matt can provide status on where he stands with regard to the kernel porting
effort.
Pushing the source to SourceForge is part of our efforts to make the project
more
open for participation by "outside" developers (which is good, because Matt
falls
into that category now). :]
Yes, we all have other stuff we need to work on. I can assure you though, that
this project is a very high priority for myself and is factored into the
supportability of SGI's Linux offering (again, Matt can speak for himself). As
for the work you are doing with respect to an Alpha port, I think that it's
very
important for this functionality to be supported on a wide range of
architectures.
What you are doing is very important to this effort. If there is any help that I
can
provide, please let me know (I'm sure Matt feels the same).
Thanks,
Tom
|