Re: [klibc] klibc and what's the next step?

 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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [klibc] klibc and what's the next step?
  - From: Alan Cox <[email protected]>
- Re: [klibc] klibc and what's the next step?
  - From: Adrian Bunk <[email protected]>

References:
- Re: klibc and what's the next step?
  - From: Olaf Hering <[email protected]>
- Re: klibc and what's the next step?
  - From: Theodore Tso <[email protected]>

Prev by Date: Re: [PATCH -mm 7/7] forbid the use of the unshare syscall on ipc namespaces
Next by Date: RE: Commenting out out_of_memory() function in __alloc_pages()
Previous by thread: Re: klibc and what's the next step?
Next by thread: Re: [klibc] klibc and what's the next step?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]