similar to: klibc integrated in the kernel

Hi, Greg - I have a 2.5.70 BK repository, with klibc integrated, at: bk://klibc.bkbits.net/2.5-klibc This repo has the following features: * Completely up-to-date w.r.t. klibc itself. * Kbuild sort of happy, but still needs an eyeball from Kai to figure out why it always rebuilds everything in usr/. * Supports both IP autoconfig and NFS root from initramfs.

klibc integrated with the kernel can now be found at: http://linux-sam.bkbits.net Se the repository: klibc. For non-BK users the patches can be retreived using the following links: klibc on top of 2.6.8-rc2: http://linux-sam.bkbits.net:8080/klibc/gnupatch@41098c67CQHEC6lH2E3rfIXcnRW1RA kbuild adaptions to klibc: http://linux-sam.bkbits.net:8080/klibc/gnupatch@4109923a7O1XqfXw_V7JzAmet_AzbA

Hi all. I have pushed my earlier announced kbuild improvements patch to: bk://linux-sam.bkbits.net/2.5-klibc First cset is the earlier posted cset, whit a few small modifications. One important change is that the usr/Makefile now uses *.a files in initramfs-y assignment. I realised that the purpose was to express what kinit were using / referring. Second cset is a trivial cset that just move

There are two hosted BitKeeper repos: klibc is a BK clone of the klibc CVS tree 2.5-klibc is my attempts to integrate klibc into the kernel If you want commit access to either repo, send me an ssh1 public key. <b

I just pushed out klibc-1.2.1; it actually has a working kinit. There are still pieces missing, but at least it works for ipconfig+nfsroot, which has been my test configuration. There is code to handle initrd already in kinit, but it hasn't been tested and so is almost certainly broken; I think the code to load a ramdisk from a floppy or other block device is not yet there. -hpa

Hi, I've been messing around with the early userspace for the last couple days. What are the goals of early userspace? Is the end goal to use it as an initrd replacement or is it simply to do all the mounting (nfsroot, initrd, hard disk) that is currently done in init/do_mounts*? thanks mh -- Martin Hicks Wild Open Source Inc. mort@wildopensource.com 613-266-2296

I'm still pondering with kbuild and klibc. Next in line was to get ipconfig support in the kernel (build wise). A little challenge that is bigger than anticipated was to create a shared executable. This required a far bigger rewrite of Kbuild.klibc than originally planned. The good part is that I now managed to treat linking of objects with single and multiple .o files almost the same.

kinit/nfsmount.c:mount_nfs_root() should use the bootpath specified by bootp/dhcp. If the "nfsroot" option is specified then it overrides the boot server bootpath and a message indicating the override is printed. --- klibc-0.194/kinit/nfsroot.c.orig 2005-01-05 04:13:47.043897880 -0700 +++ klibc-0.194/kinit/nfsroot.c 2005-01-05 04:13:09.316633296 -0700 @@ -66,34 +66,21 @@ const int

some files depend on nodes.h, but there is no dependency for that fact. olaf@mandarine:~/klibc-0.87> grep -Er 'include.*nodes.h' ash/ | sed 's-^[^/]\+/\([^.]*\).*-\1.o-' | xargs echo OBJ_NODES = OBJ_NODES = cd.o eval.o exec.o expand.o jobs.o main.o nodes.o options.o parser.o redir.o show.o trap.o var.o make spotless doesnt work reliable, the patch adds a few more targets. Is

Hopefully I should be up to date with all patches; haven't integrated the module-init-tools, and some of Erik's patches didn't make it for different reasons, which hopefully can be resolved soon. If you have sent another patch which I haven't applied, please do let me know. -hpa

hello hpa, pushed out new patch queue :) It contains the sync with latest dash git, renaming of some README's to ease their packaging, sparc32 socket test and a sh4 fix by Debian porters (numbers of changes is huge, but mostly contained in dash). git pull git://git.debian.org/users/maks/klibc.git maks initramfs-tools seems happy with that version of dash, saw no regression on boot test with

Well, as of right now, both Linus and Andrew have rejected klibc in the kernel based on "it doesn't add anything new" (Linus) and "lack of interest" (Andrew). It seems that there is little hope of getting it into the kernel any time soon, unless there is additional features, and/or people start actively asking for it. I would appreciate hearing suggestions. The

Add support for scandir() and alphasort() as defined in POSIX.1-2008. Signed-off-by: Mike Waychison <mikew at google.com> --- usr/include/dirent.h | 7 +++++ usr/klibc/Kbuild | 2 + usr/klibc/scandir.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 84 insertions(+), 1 deletions(-) create mode 100644 usr/klibc/scandir.c diff --git

OK guys, I've been communicating with Greg KH and I think I'm ready to tackle getting the early userspace stuff to a more functional level than it stands today (quite a commitment there, eh?). Before I get started, I wanted to list the major points I see that need to be done to make sure I'm not duplicating anyone else's efforts, or reinventing something that's already

Hi all. Proposal for directory structure in the kernel: usr/include <= _all_ include files usr/include/{net,sys,..} usr/include/arch/$(ARCH) <= arch specific include files *1 usr/klibc <= klibc files usr/klibc/arch/$(ARCH) <= arch specific config and files except include files usr/kinit <= program integrated in the kernel usr/kinit/nfsmount <= used by kinit,

The following patches come from Debian and/or Ubuntu packages of klibc. Ben. Ben Hutchings (1): [klibc] run-init: Add dry-run mode Jay Vosburgh (1): [klibc] ipconfig: Use separate sockets for DHCP from multiple interfaces Mathieu Trudel-Lapierre (1): [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER YunQiang Su (1): [klibc] mips: setjmp.S: don't

Hi!! I found your ipconfig stuff in the udev rpm in SuSE 9.1. I'm about to setup a initramfs (pretty cool - much better than initrd) to boot linux diskless clients over the net. All the tools I would need, seem to be there with ipconfig/nfsmount ... I like to use the information I get from PXE/syslinux or Etherboot writing something like:

Hello what is the difference between busybox and klibc? Say, I want to use an initramfs in order to mount root over nfs, I can choose to use klibc with ipconfig and nfsmount? But I can also choose to use busybox with ifconfig and mount. So what's the difference, and why and in which case one is preferable to the other? If it's a FAQ, I'm sorry, just give me the link Thanks

Hi hpa and others. With my ongoing work to prepare for potential integration of klibc in the kernel I wonder if there wold be any interest in using part of the kbuild infrastructure to build the vanilla klibc? The rationale is obvious: - common codebase for Kbuild files, so one only has to fix things in one place - I force klibc developers to create Kbuild files usable in the kernel - Much

This patchset applies to klibc mainline. This patchset introduces the ability to kinit to execute scripts or executable files present in in the initramfs before switching over to the root filesystem. It is implemented by first implementing scandir() and alphasort() as present in POSIX.1-2008 in klibc itself, and then using that as the basis for iterating and executing files via a run_scripts()