If you guys deployed the distro before last evening when I fixed it, you have two options:

1. Redeploy the image. It should not have this problem.
2. Edit /etc/inittab, change "tty0" to "vc/0". Add "vc/0" to /etc/securetty. Then run "init q" as root.

-Chris

Perfect now


sorry for the delay, didn't checked the forum 'til today

thx for your support

I just deployed a new 2005 image and i'm unable to boot it, it gets stalled here with that same problem

* Mounting network filesystems... [ ok ]
* Starting sshd... [ ok ]
* Starting local... [ ok ]
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel


thanks

I am using the "older" Gentoo install, and keep my setup uptodate with fairly regular emerges, so all my packages are new versions.

I think my kernel is linux-2.4.26.

Would upgrading to this image make any sense to me? I know that it has a more recent kernel, but are there other advantages or disadvantages?

Would I have to totally backup my current setup offline, install the image, and restore my programs and data, or would my currently compiled programs have trouble running?

Kernels can be selected independently of the distro/version - edit your configuration profile(s) in the Linode Platform Manager.

If you tell emerge to update your current system you will be invited to upgrade your Gentoo profile if necessary - that is as good as a new install.

Do not restore programs from your current system to a new install - you will may end up linking against the wrong library versions and chaos and madness will follow.

_________________
/ Peter

Just change your profile. There's a doc on gentoo's site about how to upgrade your profile.

_________________
Jay Faulkner
http://oldos.org

Just to say that the "INIT: Id "c0" respawning too fast: disabled for 5 minutes" thing is still there. I've changed this and works:

2. Edit /etc/inittab, change "tty0" to "vc/0". Add "vc/0" to /etc/securetty. Then run "init q" as root.