similar to: klibc current state

This patchset applies to klibc mainline. As is it will probably collide with Maximilian's recent patch to rename run-init to switch_root posted last week. To boot an untrusted environment with certain capabilities locked out, we'd like to be able to drop the capabilities up front from early userspace, before we actually transition onto the root volume. This patchset implements this by

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

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

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

Using the new method for building a standalone kernel module (although seems to happen with the traditional way as well) I get "mach_mpspec.h: No such file or directory" Same result if I try to do a kernel 'make'. Subsequently I get MAX_MP_BUSSES and MAX_IRQ_SOURCES undeclared. This should surely work 'out of the box' with Centos ? Any ideas about what's missing ?

Trying the most basic 'vanilla hello world' kernel driver, install using insmod, and trying in module_init to do a simple kmalloc() fails, kmalloc returns NULL - i.e. cannot allocate memory. The driver loads fine under another non-VM system. Is this a CentOS/VMware quirk ? Does anyone know of a workaround or is it just a fact of life that you cannot use insmod once the system is running

hello hpa, here my birthday submission :) please pull: git pull git://git.debian.org/users/maks/klibc.git maks Sam fixed a longstanding x86_32 build bug, thus it seems a good time to flush the queue of the piled up patches, the shortlog tells it: Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Mike Waychison (2):

The kernel header guard to ensure that headers aren't included from userland moved in commit 69c8f52b. This causes the following message to be emitted when building klibc (which is designed to use kernel headers explicitly): /usr/local/src/git/linux-2.6//include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see

Which plugins do you mean? I thought I remember Winamp, for instance, being able to do word-length reduction on the fly. The only place I can find this feature is in the Monkey's Audio codec plugin, though. Anyway, great news Josh! Thanks for making 24-bit audio support in FLAC a priority. :) MW On Tue, 11 Jun 2002, Josh Coalson wrote: > --- Mike Wren <mikew@etree.org>

Sorry to be so slow in responding. I've done what you suggested. I created /etc/sysconfig/desktop and entered "$DISPLAYMANAGER=KDM". I rebooted but there was no change. GDM is still being used. Any other suggestions? mw ======================== Just create the file /etc/sysconfig/desktop and put in it: DESKTOP=KDM I believe it's DESKTOP - you can dbl check /etc/X11/prefdm

Hi, I am recovering a CentOS 5.4 system. I've copied all partitions into the recovery system. I've installed grub boot loader. However, the original system is using /dev/sdb1 for root (/), while the recovery system is using LVM (/dev/vg0/lv1) for root (/). When recovery system boots, I got the panic error: * Mounting /dev/sdb1 on /sysroot * Mount: mounting

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

Hello, the topic was already discussed in (for example) http://syslinux.zytor.com/archives/2006-March/006586.html but I'd like to f'up as there does not seem to be a fix yet. I'm maintainer of a Live-CD and several users reported the problem: | Unknown keyword in config file | Could not find kernel image: grml to me. The problem wasn't present with older isolinux versions (IIRC

So, today, I'm using kinit from our initramfs to handle early boot up sequence. Our init is actually a shell script that does a some setup stuff (plugging values into appropriate proc files mostly), and the script currently passes on to kinit by finishing with "exec /kinit "$@"". I have a situation now though, where due to some ubuntu weirdness, I seem to need to do

This uses time, ASLR and pid for randomisation. (Closes: #516774) Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- usr/include/stdlib.h | 2 + usr/klibc/Kbuild | 2 +- usr/klibc/mkstemp.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 96 insertions(+), 1 deletions(-) create mode 100644 usr/klibc/mkstemp.c diff --git a/usr/include/stdlib.h

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

Am 08.10.2013 14:46, schrieb Stefan G. Weichinger: >> Try enabling the flag, re-emerging the package, setting the logs and >> then reproduce it again. Check the logs and you should see why it's >> disconnecting. The docs say that libvirtd has to listen on the TCP port ... checked that: # netstat -alnp | grep libv tcp 0 0 0.0.0.0:16509 0.0.0.0:*

Hi, recent isolinux versions work fine with current linux kernels on current hardware. But on older hardware there isn't a bootsplash visible at all - like if there isn't a CD in the tray. :( Sadly the older isolinux versions don't work with current kernels (giving me an empty /proc/cmdline for example when using kernel 2.6.23), otherwise I'd just use an old isolinux version of

Hi! The problem is that the BTRFS raid10 filesystem without any understandable cause refuses to mount. Here is dmesg output: [77847.845540] device label linux-btrfs-raid10 devid 3 transid 45639 /dev/sdc1 [77848.633912] btrfs: allowing degraded mounts [77848.633917] btrfs: enabling auto defrag [77848.633919] btrfs: use lzo compression [77848.633922] btrfs: turning on flush-on-commit [77848.658879]

Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my