Messages in this thread |  | | | Date | Tue, 11 Jul 2006 17:47:43 +0200 | | From | Olaf Hering <> | | Subject | Re: [klibc] klibc and what's the next step? |
| |
On Tue, Jul 11, Adrian Bunk wrote:
> On Tue, Jul 11, 2006 at 05:13:47PM +0200, Olaf Hering wrote: > > 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? > > Yes (it uses 2.6.9).
Ok, I suspect RHEL9 doesnt work with root on usb-storage or sbp2 either? If so, not a big deal. in-kernel kinit wouldnt work any better if it lacks support for async probing. But I dont know the details about the mpt failure. - 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/
|  |