Hi,

I've just signed up for a Linode 64 which I plan to use with Gentoo. I need to compile quite a lot of things via emerge to get started.

But, if I shutdown my putty.exe, all the processes running are closed, so I cannot start emerge, then shutdown my computer at home, go to sleep and then re-connect and see that it is still running.

I've read something about screen, but I cannot get it work.

Can this be done? I've installed some Linux's but always from console, so there was no problem.

Thank you in advance!

No problem. To do what you want to do... hop on the console.

Lish lets you connect to the console. It also uses screen.

That means you just ssh to yourusername@hostXX.linode.com then connect to console. Do whatever. When you're done for the night, just press 'control-d' keys to disconnect from screen session. Then log out of lish, and kill putty.

In the morning, come back and ssh back in to lish and connect to console again.

That sounds good, but when I do that:

Using username "xxx".
xxx@host46.linode.com's password:
[xxx@host46 lish] Fri May 13 00:25:51 EDT 2005
[xxx@host46 lish] Linode Shell (lish) Console starting...
[xxx@host46 lish]
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes
INIT: Id "c0" respawning too fast: disabled for 5 minutes

and I cannot type anything :'(

Hmm. I use Gentoo on a 128 MB Linode (works great).

I didn't start with 2005.0 image because I signed up before 2005.0 was available. I used 2004.2 back then, which worked great.

My /etc/inittab has:

c0:12345:respawn:/sbin/agetty 115200 tty0 linux

The error message you listed sounds like either /sbin/agetty is not there or /dev/tty0 is not there.

If you press enter a couple of times; no login prompt at all?

And you're starting from the 2005.0 config from the Distribution Wizard on your Linode management web page? And you are using what kernel -- 2.4 or 2.6?

(2005.0 uses 2.6 by default, but wanted to double check which you're using because of 2.4/devfs vs 2.6/udev which could explain your problem and how to fix it.)

Has anyone else here tried a Gentoo install recently from a 2005.0 image?

I've done this:

http://www.linode.com/forums/viewtopic.php?p=7471#7471

and it works. It is a new Gentoo 2005.0 (yesterday) with Latest 2.4 series (2.4.29-linode39-1um).

I'll try now using lish. Thank you!

FWIW, it's easy enough to use screen for the same; actually lish depends on screen on the host itself, so if lish works, and you have screen installed on your Linode, screen should work too.

Simply log into your SSH, su to root, and run "screen". Then, you can use emerge and other commands. To return to a prompt outside screen, simply press Ctrl-A, then release them, then press D on its own. You can then use "exit" and your emerge will be running happily on its own.

To look back on it, log in again, then use "screen -r". This will reattach you to your previous screen session, so you can see how things are.

(As stated, lish uses the same mechanisms - when you log in via lish, you have to use Ctrl-A then D to get back to the lish prompt, then "exit" to quit SSH.)

screen -r was the key! Thank you very much!