From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750944AbWGKPNx (ORCPT ); Tue, 11 Jul 2006 11:13:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750988AbWGKPNx (ORCPT ); Tue, 11 Jul 2006 11:13:53 -0400 Received: from cantor2.suse.de ([195.135.220.15]:49077 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1750871AbWGKPNx (ORCPT ); Tue, 11 Jul 2006 11:13:53 -0400 Date: Tue, 11 Jul 2006 17:13:47 +0200 From: Olaf Hering To: Theodore Tso , "H. Peter Anvin" , Roman Zippel , linux-kernel@vger.kernel.org, klibc@zytor.com, torvalds@osdl.org Subject: Re: [klibc] klibc and what's the next step? Message-ID: <20060711151347.GA15625@suse.de> References: <20060711044834.GA11694@suse.de> <20060711134554.GC24029@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20060711134554.GC24029@thunk.org> X-DOS: I got your 640K Real Mode Right Here Buddy! X-Homeland-Security: You are not supposed to read this line! You are a terrorist! User-Agent: Mutt und vi sind doch schneller als Notes (und GroupWise) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 11, Theodore Tso wrote: > > In earlier mails you stated that having kinit/klibc in the kernel sources > > would make it easier to keep up with interface changes. > > What interface changes did you have in mind, and can you name any relevant > > interface changes that were made after 2.6.0 which would break an external > > kinit? > > When you load a SCSI driver (the one that bit me was the MPT Fusion > driver), it no longer waits for SCSI bus probe to finish before > returning. So the RHEL4 initrd fails to find the root filesystem, and > bombs out. This change was definitely made after 2.6.0, and is an > example of the sort of change which wouldn't have happened if kinit > was under the kernel sources and not supplied by the distro. Was RHEL4 designed for 2.6?