Okay so on bootup, kernel message is spit out: The system still boots and runs...or tries to.

1) There seem to be around 32 processes running with [khelper] using [modprobe] on char-major-235-12.
2) This causes the system to...practically convulse.. System lags and every program eventually becomes [defunct].
3) this happens even in init 1
4) killall -9 does not work against those processes, probably due to the kernel process [khelper].

So..
1) Is this a kernel problem..I am currently recompiling it on another host, using chroot.?
2) is this a modprobe problem..I recompiled it as well under the chroot?
3) what is char-major-235-12. This seems to be /dev/erandom, thanks to some research. This leads me to believe that the erandom patch does not work, or it corrupts the kernel..

Any ideas? I will probably try recompiling from a vanilla, or at least an erandom free, kernel.

one final question, is a "runaway loop" the same as an infinite loop?

when you built the kernel did you build in frandom not as a module and include sysctl
i think that's how it's supposed to work ?
are the devices in dev after you boot up
i think udev does not create the devices and you have to do it in the boot scripts
if Salfs is some version of lfs then check if these lines are in /etc/sysconfig/createfiles or create them
echo "/dev/frandom dev 0755 root root char 235 11" >> /etc/sysconfig/createfiles
echo "/dev/erandom dev 0755 root root char 235 12" >> /etc/sysconfig/createfiles
/dev/erandom and /dev/frandom getting created and there shoud i think be a temp file
these command are in hlfs
install -m0600 /dev/null /var/tmp/random-seed
/bin/dd if=/dev/urandom of=/var/tmp/random-seed count=1
to get framdon seeded

i also see a blfs-bootscripts-frandom-2.patch in the archives now -- don't know exactly what that is
it just soulds like to me your boot scripts aren't set up right

sorry, overlooked this reply of yours.

I'll look into what you said as soon as I can, I have been using the system without frandom for some time now.


In the order in which you asked:
1) *dont remember*
2) yes
3) I have makedev scripts make the devices as a failsafe in case ramfs mount does not work, trying. And, I am slowly moving to udev and I want to make sure everything else works before I try using it. So I have not been using udev during these attempts. (could that be my problem?)
4) Salfs = Slightly Automated Linux From Scratch. I wrote some shells scripts to auto-do some things and speed up my installation time.
5) echo "/dev/frandom dev 0755 root root char 235 11" >> /etc/sysconfig/createfiles
echo "/dev/erandom dev 0755 root root char 235 12" >> /etc/sysconfig/createfiles
This I will try.
6) I'll try
7) Yes, I seem to have missed that patch. With any luck this will fix it. I'll do this approach first.