Hello, I'm just messing around for learning purposes.

Basically what I tried is:
- remove initrd boot option
- add rootfstype=ext4

This seems to work. Kernel runs my /sbin/init file in statically linked busybox, the script mounts sysfs devtmpfs and proc and give user console.

My problem is whenever I try to run something dependent on glibc. I get "file not found" error, which as I found out in fact means "cannot find your shared libs".

Then I tried mounting /dev/hda1 (that's the device from which I boot, so I'm mounting the disk that's already mounted at /) to /mnt/a
Set LD_LIBRARY_PATH=/mnt/a and voila ldd runs.

So I conclude this has something to do with me running from rootfs. Apparently shared libs cannot be found on rootfs
And that's my question, why not? What is the difference between rootfs and an actual extfs in respect to dynamic loader?
If you think there is some code I need to see to understand, feel free to reference it, I'm proficient in C, but I haven't read much of the post Linux boot code yet.

So...
What you're saying is that when you "Set LD_LIBRARY_PATH=/", that don't work?

Yes

Hmmm it says here https://www.kernel.org/doc/Documenta...-initramfs.txt

"Most systems just mount another filesystem over rootfs and ignore it."

Which expectedly for me prints device busy. Also it doesn't behave as tmpfs because the changes persist across restarts. Alright, I think I know what to do..

Ahhhh... I think I know what the problem is.. I probably messed up some options when I compiled glibc and now it's looking for SYSTEM_DIRS in the directory of my prefix as it was on the build machine. setting LD_LIBRARY_PATH=/lib also works. well that sucks glibc builds forever. Well valuable lesson though, I won't forget this again I bet.