Updating Gentoo from image questions.

Does anyone have a 'best practices' for updating a Gentoo image upon a new installation? I keep b0rking mine. I've tried both

emerge –update world


emerge --update system

and both have just stopped at some point. I have a Linode 64 w/ 'Latest 2.6 Series' kernel. I just ran across the message that suggested MAKEOPT="-j1" and I'll try that. Any other suggestions?

4 Replies

Just to watch "cat /proc/io_status" (only applies if your not on a new host with the CFQ-TS patches, which if you just signed up, chances are you're on one of the new hosts), and keep these tips in mind:


Setting MAKEOPT="-j1" is highly recommended as well.

In what way is it "b0rking" your Linode? Why does emerge stop? Are you overwriting config files using etc-update that your not watching or don't understand? I could use a little more clarification on the problem.

I don't know where or why it's stopping. Sometime after running either of those commands I can't login via ssh and lish get's me to a command prompt but I can't manually start or restart anything.

I haven't gotten a prompt to update etc files and I'm not running it at the prompt in lish.

That's all the clarification I can give I think. I've just deleted everything and am starting over from scratch, being a lot more careful about what I'm doing at each step. Quite probably I did something screwy but I don't know what.

Thanks for the url, I'll look at it and see if I can get it working.

I'd login via Lish and see if the OOM killer killed sshd.


The problem most likely occurs during linking of glibc - my L64 only just manages it. You need 256 MiB of swap to avoid having the OOM killer activate.

Even on the CFQ-TS patched hosts, there must be some penalty for excessive swapping. If a Linode that is busy swapping is made to wait for disk i/o during swap, it looks as if the VM system eventually freaks out and behaves as if it has run out of memory.


Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct