Great! That was it. I enabled devtmpfs in my kernel and my system boots with no problems. What I don't understand now is why my other system boots without devtmpfs. Obviously there must be something different. Any idea?

Both systems have:

sys-apps/baselayout-2.0.2
and
sys-apps/openrc-0.8.2-r1

For completeness, here is the output of etc-update (which shows no updates are pending):

# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0

_________________Check out this RPG: http://www.daysofdawn.com/. You can preorder it on their page. Linux needs some good RPGs and this one looks very promising!

Great! That was it. I enabled devtmpfs in my kernel and my system boots with no problems. What I don't understand now is why my other system boots without devtmpfs. Obviously there must be something different. Any idea?
...

Probably, your other system is using an older kernel than kernel-2.6.39. With new kernel-2.6.39, I think devtmpfs is required, since some kernel devs like the devtmpfs that speed up boot process. Actually, there must be a bug, because they say devtmpfs can be disabled._________________Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"

...
I cannot really figure out what is wrong here. Can anybody help?
...

Have you enabled devtmpfs in your kernel? After I enabled, my same problem is solved.

You have to enable both options, just in case people are wondering, i enabled only one of them and it didn't work, you also have to set the automatically mount devtmpfs option also_________________I know 43 ways to kill with a SKITTLE, so taste my rainbow bitch.

I had the same problem today. I resolved it by using older stage3 and portage archives. And by "older" I mean like "2010". So I have no clue, when the error has been introduced to the current/latest archives...

One more thing, with baselayout 2 and openrc df and mount shows root mount point as
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw....)
Is it possible to set old behaviour? (/dev/sdaX on /)? //not solved
And I am using ext4, on other mounted drives it show corrected ext4, but for root mount it shows ext2 //solved, my mistake

Mounting works fine and there are no kernel errors or anything. It is just stucking at init-early.sh.

I found the following in the migration guide:

Quote:

Previously, the initial rootfs entry was removed from /etc/mtab, and only the real root / entry was present. The duplicate rootfs item was actually added back during shutdown. In OpenRC, both entries must be present for full support of initramfs and tmpfs-on-root. This also means that less writing is required during shutdown.

But - unfortunately - I have no clue what to do now. At the moment it should just mount an unencrypted device and go on with the regular init. Later on I will use it for decrypting and mapping the device.

I'm having the same problem here - I've tried rebuilding my kernel with devfs and putting rw in the kernel command line, but i still get init-early.sh used greatest stack depth.... I'm not using an initramfs_________________ACTA is a war on your digital freedom

I'm having the same problem here - I've tried rebuilding my kernel with devfs and putting rw in the kernel command line, but i still get init-early.sh used greatest stack depth.... I'm not using an initramfs