On Fri, 14 Jan 2000, Brian Hall wrote:
|>No, it applied cleanly against the i386 branch. I edited the patch for
|>i386/vmdump.c and applied it against my modified Alpha version, which resulted
|>in me having to hand resolve one or two things (no big surprise, and not a
|>problem).
|>
|>Getting close to actually testing the dumping mechanism on Alpha, I
|>think. I hope to try it via the method in the FAQ on Monday or Tuesday next
|>week. If that part works I'll release it to the list (danger! pre-patch!),
|>hopefully someone else here with an Alpha can try it and/or see if it is
|>correct. Then, I'll start working on the lcrash tools.
|>
|>Unless there is some reason to do otherwise, I'll plan on providing the
|>Alpha (testing) version as a patch against lkcd-1.0.4 (i.e. apply the lkcd &
|>sgi+straw patches to the 2.2.13 tree, then the Alpha patch).
Sounds cool, we can provide the patch either as part of the main patch,
or on our web site. Let me know what you'd like to do.
Also, I'm a bit closer on the IDE stuff, once I got through to some
people about what I was trying to do to the drive. There are other
problems, however. I'd like to write out to disk without ever having
to hit a lock. This requires writing my own interface for dumping.
If I'm going to bother doing this, I might as well write one function
with a switch() case based on drive type, so then it won't matter
what happens to the file_operations[] and block/char driver changes.
Any thoughts?
--Matt
P.S. I'll try to get to the rc.sysinit stuff next week.
|>On 14-Jan-2000 Matt Robinson wrote:
|>> Okee, I'll do that instead. Any problems with the patch?
|>>
|>> --Matt
|>>
|>> On Fri, 14 Jan 2000, Brian Hall wrote:
|>>|>The patch format for rc.sysint is probably better, since it is smaller and
|>>|>more
|>>|>adaptable.
|