Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I specified rdinit=/bin/sh and manually booted the system (in chroot) from command line, complete with mounted filesystems, network services and X desktop. The init is still busybox's /bin/sh.

The problem is that I see many uncollected "zombie" processes.

How to start proper init, but not all boot scripts again? I feel that if I "exec chroot /mnt /sbin/init" then it either starts extra things or exit with some error and "kernel panic".

(Don't advice just to reboot)

Update: Just executed into system bash (instead of busybox's one) exec chroot /mnt /bin/bash and now zombies gone.

share|improve this question
Check out how Busyboxs init works: and is good too – micke Jan 10 '12 at 16:08
This file must be on the kernel ramdisk instead of on the root filesystem. – bZezzz Jan 10 '12 at 16:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.