On 5/25/12 3:52 PM, Brandon Stafford wrote:
On Fri, May 25, 2012 at 4:30 PM, Mark Hatle<[email protected]> wrote:
>> Has the boot process changed? What should I be doing instead of
>> calling /sbin/init?
>
>
> You should check your new rootfs. is there anything called init on it, even
> in a different directory?
So far as I can tell, there is no file named init in the filesystem.
> Are you using meta-oe and systemd?
meta-oe: yes
systemd: only if it is enabled by default, so I don't think so. I can
still see /etc/rc[0-5].d, so I think that means Sys V is still in
place.
meta-oe may have systemd enabled by default, but I'm not sure. I haven't used
it recently enough to know for sure.
>
> You should have some type of an init in the new filesystem.. if not, then
> something is wrong with your image and you'll need to diagnose that first.
Sounds like I have something amiss with my filesystem.
Is there a way to tell which package previously generated /sbin/init,
so I can see whether it has changed?
Usually busybox, or sysvinit are the packages that generate that binary. You
should be able to see if either was built. Search the filesystem for systemd
may tell you as well..
--Mark
Regards,
Brandon
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
