Messages in this thread | | | Date | Sat, 01 Jul 2006 03:04:55 +0400 | From | Michael Tokarev <> | Subject | Re: klibc and what's the next step? |
| |
Pavel Machek wrote: [klibc/kinit in kernel] > I'd like to eventually move swsusp out of kernel, and klibc means I > may be able to do that without affecting users. Being in kinit is good > enough, because I can actually share single source between kinit > version and suspend.sf.net version.
Heh. Take a look at anyone who's using real initramfs for their boot process. Not initrd, not kernel-without-any-preboot-fs, but real initramfs. For them, if kinit/klibc will be in kernel, nothing changes, because their initramfs *replaces* in-kernel code and future supplied- with-kernel-klibc-based-kinit. So if you'll move swsusp into kinit, it WILL break setups for those users!.. ;)
And with time, amount of such users increases. Because everyone's switching from initrd to initramfs; or because everyone's starting using initramfs (not initrd as "obsolete") since their systems now require some sort of custom stuff while mounting root (like firmware loading, or device-mapper setup for sata pseudo-raids, or whatever).
Oh well.
/mjt - 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/
| |