similar to: refactoring do-mounts out of kinit

On a train ride to Bruxelles, brought out my axe and directly attacked run_init(8). run_init(8) is dead, long live switch_root(8). The next run on switch_root(8) involves fdopendir, so another push for the upcoming stdio 1.6 branch. The following is boot tested with initramfs-tools, kinit(8) tests would very much be appreciated!? Michal Suchanek (1): [klibc] switch_root: Fix single file

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

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

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,

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.

hello hpa, nothing particular stands out, just syncing with latest Debian upload and subsequent patch emails. please review merge or nack. thanks :) maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md assembly if mdX exists Colin Watson (1): [klibc] mount/umount FUSE support Harald Jenny (1): [klibc] fstype:

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. This functionality is implemented in a newly introduced run_parts() call, which calls scandir() to iterate through files which in then executes in sequence. run_parts() is also available as a

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

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

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 , 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

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

Hello, While some people might scuba dive, let's summarize recent progress and state (People cc'ed have either patches in queue or are involved): * Patches pending review, allmost ready for klibc ------------------------------------------------- - mikew/drop_cap - kinit: Add drop_capabilities support adds the ability to kinit to allow the dropping of POSIX capabilities. (patch even

Hi, The following set of patches is intended mostly to improve ipconfig and nfsmount compatibility with glibc. The context: I'm working on yaird, an alternative to mkinitrd, and currently implementing nfs root file systems. This is based on ipconfig and nfsmount from klibc, with a rewritten version of kinit. Users should be able to build the package with vanilla glibc, since klibc is not

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

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

Building on the work in ff0a614bd724f6c4c6a5014a9955dc1bc028f336, this moves the capability code down into the run-init library, so that run-init can use it as well, via the new "-d" flag. Signed-off-by: Kees Cook <kees at outflux.net> --- usr/kinit/Kbuild | 3 +-- usr/kinit/capabilities.h | 10 ++++++++++ usr/kinit/kinit.c | 6 +++---

The following patchset implements 3 seperate series of changes. External Building ================= Patches 1 through 8 enable to use of klibc's build system while leaving the src tree pristine (and potentially read only). Specifically: - srctree=<Sources for klibc> - objtree=<Ouput directory for klibc> - KLIBCKERNELSRC=<Kernel sources> - KLIBCKERNELOBJ=<Kernel

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

This patch adds the ability to kinit to allow the dropping of POSIX capabilities. kinit is modified by this change, such that it understands the new kernel command line "drop_capabilities=" that specifies a comma separated list of capability names that should be dropped before switching over to the next init in the boot strap (typically on the root disk). When processing capabilities