In article <m11wtcvw5k.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx> you wrote: > Vivek Goyal <vgoyal@xxxxxxxxxx> writes: > >> On Mon, Jun 26, 2006 at 07:41:00AM +0530, Maneesh Soni wrote: >> >> Maneesh, Keeping this code under a config option becomes a problem when we >> will have a relocatable kernel. At some point of time we got to have >> relocatable kernel so that people don't have to build two kernels. In fact >> this is becoming a pain area for distros. That's the reason I thought >> of making it a command line parameter. > > Ok. Even if we do this with a command line, we need to have a clean concept. > If the concept is ignore devices with a brittle init routine that is compre= > hensible > and potentially useful for other reasons than crash dumps. > > If the concept is crashdump it is a poorly defined concept and all of Andre= > ws > objections apply. > >> I remember few months back, Eric had mentioned that he has got patches for >> relocatable kernel ready for review for i386 and x86_64. Eric, do you have >> any plans to post the patches for review? > > I have some code that I keep intending to get to. It has probably bit > rotted since I wrote it, but it shouldn't be too bad to clean up. > Unfortunately the whole crashdump thing is fairly low on my priority > list. Hi Eric, If you have some code to relocate the i386 and x86_64 kernels then I for one would really like a chance to look over it. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
