Ah progress! ;) Good find.
On Fri, Sep 30, 2016 at 1:30 PM, Maxwell Bottiger <
sleepyli...@jive-turkey.net> wrote:
> Got it. I needed to turn switch on CONFIG_DEVTMPFS=y, and
> CONFIG_DEVTMPFS_MOUNT=y in the kernel. Now dev is populated and everything
> else came along with it.
>
> Thanks!
>
Nope, you are seeing exactly what I would have expected. You have verified
a lot of functionality. Your kernel boots, mounts a root file system, and
executes your init command. So that's a big step. Now you need to sort
out your sysV init stuff. You can actually do a lot from that simple
shell.
Got it. I needed to turn switch on CONFIG_DEVTMPFS=y, and
CONFIG_DEVTMPFS_MOUNT=y in the kernel. Now dev is populated and everything
else came along with it.
Thanks!
-Max
On Fri, Sep 30, 2016 at 12:16 PM, Maxwell Bottiger <
sleepyli...@jive-turkey.net> wrote:
> Chris,
>
> Thanks for the sugge
Chris,
Thanks for the suggestions. The system is based on SystemV and uses the
old school init scripts.
I rebuilt my kernel with init=/bin/sh and I can get into the system now!
The thing is, I don't see anything in /proc, and only /dev/null exists in
the /dev directory. I don't know if the lack
You could sell this as a very secure box ;)
Kidding aside, it didn't "zip" through runlevel 5, in fact, you don't know
what runlevel it is actually in. 11 seconds after your file system is
mounted, a reboot is issued. From your trace, nothing running in userspace
displayed any messages to the co
I've been working on setting up a poky distro on an older intel XScale
system, and I finally got a working kernel and root filesystem. However,
when I boot the box it zips through runlevel 5, then halts. It seems to me
like maybe init isn't kicking off getty or some sort of interactive login.
Has
