similar to: The future of klibc in the kernel

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

Peter, we found that nfs over udp will corrupt data under very extrem load, there is no way to fix it due to the way how UDP works. TCP will not have these problems. I also wonder why the package size is only 1k. Everyone who wishes a slow connection can pass the desired options via the kernel cmdline. Everyone else prefers probably the fast mount. The defaults should look more like that: ---

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

This seem to be a good timing taking up the integration of klibc in the kernel again. Based one klibc-0.152 and klibc.bkbits.net/2.5-klibc I will take a shot of it. I will focus on getting the library compiled (should be pretty straighforward). Next two steps are: 2) Adding minimum applications to the kernel (if any) 3) Support applications outside the kernel I will put my work on bkbits.net

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.

In case anyone's interested, I followed up in the linux-nfs mailing list: https://marc.info/?l=linux-nfs&m=156887818618861&w=2 Thanks, Alkis On 9/15/19 10:51 AM, Alkis Georgopoulos wrote: > I think I got it. > > Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. > By lowering this to 32K, all issues are gone, even with the default > timeo=7. And

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

I can't explain why 700 msecs aren't enough to avoid timeouts in 100 Mbps networks, but my tests verify it, so I'm writing to the list to request that you increase the default timeo to at least 30, or to 600 which is the default for `mount -t nfs`. How to reproduce: 1) Cabling: server <=> 100 Mbps switch <=> client Alternatively, one can use a 1000 Mbps switch and

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,

Hey all, bug report time. I started tracking this down, but am at a bit of a loss for time, so I figured I'd report over this list to see if anyone else has the time to fix this or at least find the error. When calling nfsmount on it's own, say "nfsmount 1.2.3.4:/home/nfs /root" it works just fine, however, when calling nfsmount_main from within kinit (via nfsroot=), things get

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

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

[please CC me on replies, I'm not subscribed] Hi, I'm trying to get dmraid 1.0.0rc9 [0] to compile with --enable-klibc, however I have some troubles with mkfifo defined in /usr/lib/klibc/include/sys/stat.h. /usr/lib/klibc/include/sys/stat.h: In function 'mkfifo': /usr/lib/klibc/include/sys/stat.h:28: error: 'S_IFMT' undeclared (first use in this function) after

as the next klibc release 1.5.16 looks like shaping up, I have a trouble to build that for Debian. currently I build depent on linux-libc-dev, I don't know what against I can build latest klibc, see klibc fails to build due too: make -C linux/ ARCH=x86_64 INSTALL_HDR_PATH=debian/tmp/usr/lib/klibc/ headers_install make[3]: *** No rule to make target `headers_install'. Stop. make[2]: ***

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

Hi , I am doing some tests with klibc 1.1.16. I would like to have my root file system on an nfs export , but the /etc folder it to be mounted from a different nfs export. I am using 2.6.15.1 with initrd ramdisk initramfs nfsroot etc compiled in. My pxelinux.cfg looks like this: default opteron label opteron kernel gentoo/vmlinuz-opteron append initrd=gentoo/initramfs.img ip=dhcp

[ adding klibc ml to cc ] On Thu, Feb 01, 2007 at 09:29:52AM -0600, John Goerzen wrote: > > It appears to be largely undocumented, but a review of > /usr/share/initramfs/scripts/nfs shows that this package supports NFSv2 > and v3 only. I don't know why v4 isn't supported. yup, this needs nfs v4 support in klibc nfsmount. would be could to get that soon postetch, but someone

2ad780978b7c0c3e7877949f098cbd06e7c73839 broke klibc build MNTPROC_MNT and MNTPROC_UMNT no longer defined. usr/kinit/nfsmount/mount.c: In function ?mount_call?: usr/kinit/nfsmount/mount.c:179: error: ?MNTPROC_MNT? undeclared (first use in this function) usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier is reported only once usr/kinit/nfsmount/mount.c:179: error: for each function

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

Hi all, I have pushed out klibc-1.5, as well as an integrated klibc against 2.6.21-rc2. Have fun :) -hpa