Tycho Nightingale wrote: > > On Thu, 4 Dec 2008, Karen Tung wrote: > >> Hi Sanjay, >> >> It turns out that the entry for /etc/system is not there. >> I am not sure why. Will look at the DC code. >> >> We added the entries by hand, now, we don't have >> the panic. It got much further in the booting process, but >> it got into an infinite loop with failures on trying to execute the >> following 2 commands: >> >> ----------------------- >> INIT: Command >> "exec /sbin/autopush -f /etc/iu.ap" >> failed to execute. >> errno = 2 (exec of shell failed) >> >> INIT: Command >> "exec /sbin/soconfig -f >> /etc/sock2path" >> >> failed to execute. errno = 2 (exec of shell failed) >> ----------------------- >> >> I checked the root archive, the /sbin/autopush and /sbin/soconfig are >> both >> there, and have the correct permissions. /etc/iu.ap and /etc/sock2path >> are also there. >> >> Thoughts? > > Looks like init is unable to execute the binaries not that the files > are missing. Yes, it appears that way. I didn't have time to fully investigate yet. That was from my 30 second investigation. Mainly, I want to let people know that we seemed to have gotten past the panic, and the new errors we got. In case people know off the top of their head what is wrong. We will take a closer look tomorrow.
> > What does /dev and /devices look like? Has devfsadm been run? On the root archive, /dev has about 220 items, which are either symlinks or directories. /devices has 1 directory called "pseudo", and it has no contents. devfsadm should have been run by the Distro Constructor as part of the process of creating the root archive. Thanks, --Karen > > Tycho
