Messages in this thread | | | Date | Tue, 11 Jul 2006 10:23:44 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [klibc] klibc and what's the next step? |
| |
Olaf Hering wrote: > On Tue, Jul 11, Jeff Garzik wrote: > >> Two are IMO fairly plain: >> >> * Makes sure you can boot the kernel you just built. > > There is always some sort of prereq when new features get added. > Documentation/Changes has a long list. Some setup need more updates, > some need fewer updates. No idea what your experience is. > Old klibc was trivial to build (modulo that kernel header mess), and I > expect that kinit handles old kernels. >
"Old klibc" still exists and is the same code out of the same source tree.
>> * Makes it easier to move stuff between kernel and userspace. > > What do you have in mind here? > Once prepare_namespace is gone, there is no userspace code left.
Things that have been bandied about, for example:
- suspend/resume - partition discovery
I'm sure there is more.
-hpa - 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/
| |