inittab is not executing after my Linux box boots up

Dave Hylands dhylands at
Sun Jun 19 13:52:52 EDT 2011

Hi Projish,

On Sun, Jun 19, 2011 at 8:24 AM, Prajosh Premdas
<premdas.prajosh at> wrote:
> Hi
> Please find the entire boot sequence here
> TCP cubic registered
> NET: Registered protocol family 17
> rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
> IP-Config: Guessing netmask
> IP-Config: Complete:
>      device=eth0, addr=, mask=, gw=,
>      host=, domain=, nis-domain=(none),
>      bootserver=, rootserver=, rootpath=
> eth0: link up (100/Full)
> VFS: Mounted root (nfs filesystem) on device 0:12.

So it looks like your root file system was mounted successfully.

> Freeing init memory: 128K

All message from this point onwards come from init.

> Starting network...
> ip: RTNETLINK answers: File exists
> Starting dropbear sshd: generating rsa key... generating dsa key... OK

And since sshd is starting, it's actually processing stuff from your
root file system.

You may want to try disabling ssh. Generating the rsa key can take
several minutes, depending on how fast your target is. So it may look
like the system is hung, but it will actually continue to boot.

You may want save away the generated RSA key and include it in your
generated image so that this step is faster. For a given filesystem,
it only happens the first time, and once the generated key is stored,
ssh will just use the previously generated key. But if you're
constantly rebuilding your filesystem without any generated keys then
the first time you boot the new filesystem you'lll gget a long delay.

Dave Hylands
Shuswap, BC, Canada

More information about the Kernelnewbies mailing list