search for: switch_root

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 mounts maximilian attems (7):...

...very system boots, I got the panic error: * Mounting /dev/sdb1 on /sysroot * Mount: mounting /dev/sdb1 on /sysroot failed: No such file or directory * Mount: mounting /dev on /sysroot/dev failed: No such file or directory * * switching / to /sysroot * Switch_root: bad newroot /sysroot * Kernel panic - not syncing: Attempted to kill init! I've changed the recovery system fstab to use the correct devices. I deleted recovery system etc/lvm/cache/.cache file. But it still doesn't work. What am I missing? Thanks, - xinhuan...

...ves patches are for wider testing in: http://git.kernel.org/?p=libs/klibc/klibc-queue.git * Patches in the works: ----------------------- - mikew/bootscripts - kinit: Add callsites to execute files Needs discussion about /scripts path, maybe look at was udev does, like /lib/kinit/ ?? - maks/switch_root : Reworks run-init into feature equiv with switch_root Needs repost on top of aboves queue - hpa/stdio : Buffered stdio Small conflicts with missing ferror (no real blocker as current ferror does nothing). - maks/mv : Fix utils mv to work across fs Implemented recursively so can also ser...

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

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

...vda1): mounted filesystem with ordered data mode dracut: Mounted root filesystem /dev/xvda1 *dracut: chroot: failed to run command `/sbin/load_policy'': No such file or directory* dracut: Switching root *Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100* Pid: 1, comm: switch_root Not tainted 3.7.1-3.el6xen.x86_64 #1 Call Trace: [<ffffffff8149d541>] panic+0xc4/0x1d6 [<ffffffff81047131>] do_exit+0x3a5/0x834 [<ffffffff8111e70f>] ? vfs_write+0xd2/0x10a [<ffffffff8104763d>] do_group_exit+0x7d/0xa5 [<ffffffff8104767c>] sys_exit_group+0x17/0x1b...

...urpose. kexec is so simple if you put the kernel and initramfs you want to boot into the initramfs used to test your environment. Of course you also can also add some scripts, modules and binaries to the original initramfs to test your environment and decide whether to shutdown or do the final switch_root. A cool feature of syslinux helps that you do not need to assemble a complete new initramfs everytime: Prepare a second cpio with the overrides and load it after the original initramfs: initrd=original.img,mods.img Do you just have to identify that a certain I?C controller is present or do you...

Am 27.02.2014 20:49, schrieb H. Peter Anvin: > I2C can be provided through an almost infinite number of controllers, > and building an I2C subsystem in Syslinux would be a good step toward > making it a fullblown operating system. Why not use linux as bootloader? Booting a (rather small) linux kernel with I?C support and either shutting down or kexecing another linux kernel (plus

...files changed, 17 insertions(+), 16 deletions(-) thanks to all the involved parties. maks commit 61368211ae1e77fa2ef82bb9135c7b8e9447023e Author: maximilian attems <max at stro.at> Date: Wed Aug 25 20:34:26 2010 +0200 [klibc] run-init: get rid of over paranoid test for /init switch_root in util-linux hasn't it either. cc0c0262 added the checks, but probably didn't have the following application in mind. In fact it can break chainloading of bigger initramfs out of small one: "I boot via pxe, kernel + very small ramfs this ramfs start an ap...

...AUFSOPT} none ${ROOT} 2> /dev/null || \ { # If UnionFS fails, fall back to copy/bind mounting copyBindMount } ###################### } # END OF FUNCTIONS # ###################### # Make required applets easier to access for applet in cat chmod cp cut grep ls mkdir mknod mount umount switch_root \ rm mv vi cpio tar mke2fs sync fdisk dd ; do /bin/busybox ln /bin/busybox /bin/${applet} done # Clear the screen #clear # Don't! This will clear the Linux boot logo when using a framebuffer. # If you want to clear the screen on boot add the "clear" command to...

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 adding a "drop capabilities" a...