Messages in this thread |  | | Date | Wed, 30 Oct 2002 23:20:42 -0500 (EST) | | From | Patrick Finnegan <> | | Subject | Re: What's left over. |
| |
I'm kind of new here, but I'll present my case in hope that someone listens to me.
On Wed, 30 Oct 2002, Linus Torvalds wrote:
> On Thu, 31 Oct 2002, Rusty Russell wrote: > > > Crash Dumping (LKCD) > > This is definitely a vendor-driven thing. I don't believe it has any > relevance unless vendors actively support it.
This is something that we're just starting to use in my department in Purdue - we work with clustering, and LKCD will let us determine why our nodes decide to kernel panic since it's generally not worthwhile to connect a head to each machine.
I see LKCD as having a big impact by allowing kernels to be debugged after they have panic'd (and thus don't send out a message to syslog). It can especially be usful in compute farms, or other scenerios where it's difficut or cost prohibitive to connect a console (or console server) to each individual machine.
> > EVMS > > Not for the feature freeze, there are some noises that imply that SuSE may > push it in their kernels.
I think that the integration between RAID and LVM is a good thing, and EVMS's 'plug-in module' architecture will help tremendously to bring interoperation with other systems' volume management subsystems. Specifically, the interoperation with IBM's JFS LVM and MS's LVM will be helpful for people trying to migrate their servers over from those OS's to GNU/Linux.
-- Pat
Purdue University ITAP/RCS Information Technology at Purdue Research Computing and Storage http://www-rcd.cc.purdue.edu
- 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/
|  |