Date: Sat, 05 Apr 2003 10:42:43 -0500 From: "Tommy Forrest - KE4PYM" <tforrest@shellworld.net> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Cannot Fork: /etc/rc.devfs Message-ID: <200304051542.h35FgkYe083168@server1.shellworld.net>
next in thread | raw e-mail | index | archive | help
Howdy. I'm getting pretty frustrated with FBSD 5.0. Somehow I've managed to goof up the system. It started after I built a custom kernel. After rebooting into the new kernel I start getting all sorts of cannot fork errors. One specific one is "/etc/rc.devfs cannot fork: resource temporarily unavailable". The only thing I did was comment out the 486 and 586 cpu sections as well as the floppy drive. I thought at first it was because of the addition of the IPFIREWALL options. Because when the new kernel boots I cannot login (cannot fork: resource temporarily unavailable). I recopied the GENERIC kernel to my custom kernel made NO changes to the GENERIC kernel, built it, installed it and rebooted. Still no login (cannot fork: resource temporarily unavailable). So I reinstalled. Then made a new kernel. Still no login (cannot fork: resource temporarily unavailable). So I checked /etc/rc.devfs. I saw nothing worth noting in that file. 98% of it is commented out. I'm seriously ready to give this thing the fork alright. But I do not want to damage my nice silverware. Why is this thing not forking? I do not even know where to continue my troubleshooting now. Tommy Forrest - KE4PYM - tforrest@shellworld.net My two cents: Windows NT: Vapourware of the desperate and scared.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304051542.h35FgkYe083168>