Messages in this thread | | | Subject | Re: [RFC] klibc requirements | From | Juan Quintela <> | Date | 09 Jan 2002 14:23:46 +0100 |
| |
>>>>> "felix" == Felix von Leitner <felix-dietlibc@fefe.de> writes:
Hi
>> Comments from the various libc authors? Comments from other kernel >> developers about requirements and goals they would like to see from such >> a libc?
felix> I think you need to ask initrd users. felix> My understanding was that people want to use the IP autoconfiguration felix> stuff from the kernel to initrd. Is that still so? What other programs felix> are needed?
I can think of that in a fast thought:
- if fsck.* can be there, it will make fs nice, just now they have to be able to fsck a ro root fs. - I suppose that you can put here also the raid autodetect code and things like that. - you also need a very small minishell, something like nash (that cames with mkinitrd will suffice). Basic utility here is that you want to have several small programs and have a small shell script to configure them (a distribution dont' want to recompile all its boot programs for each target configuration). - as I suppose that you have supposed insmod is essential :) - you already put there IP autoconfiguration.
Later, Juan.
-- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy - 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/
| |