Messages in this thread | | | Date | Thu, 31 Oct 2002 13:10:07 -0500 | From | Chris Friesen <> | Subject | Re: What's left over. |
| |
Linus Torvalds wrote:
> In particular when it comes to this project, I'm told about > "netdump", which doesn't try to dump to a disk, but over the net. > And quite frankly, my immediate reaction is to say "Hell, I > _never_ want the dump touching my disk, but over the network > sounds like a great idea". > > To me this says "LKCD is stupid". Which means that I'm not going to apply > it, and I'm going to need some real reason to do so - ie being proven > wrong in the field.
How do you deal with netdump when your network driver is what caused the crash?
Ideally I would like to see a dump framework that can have a number of possible dump targets. We should be able to dump to any combination of network, serial, disk, flash, unused ram that isn't wiped over restarts, etc...
Chris
-- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |