> 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...
This is what the LKCD with generic interface is .. LKCD with generic
interface has the capability to include various dump targets in a very clean
way. Originally the LKCD meant for saving dump only on the disks, but its
generic interface has provided the option to have a number of dump targets.
Regards
Deepak.
-
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/
This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:55 EST