Archives
Archives
| From: | Tanstaafl <tanstaafl@×××××××××××.org> | ||
|---|---|---|---|
| To: | gentoo-user@l.g.o | ||
| Subject: | Re: [gentoo-user] Serious problem with linode vm | ||
| Date: | Mon, 15 Apr 2013 18:55:57 | ||
| Message-Id: | 516C4D00.9020603@libertytrek.org | ||
| In Reply to: | Re: [gentoo-user] Serious problem with linode vm by Michael Mol |
||
| 1 | On 2013-04-15 2:02 PM, Michael Mol <mikemol@×××××.com> wrote: |
| 2 | > Were this one of my systems (none of which is in a prod scenario, so |
| 3 | > take it with a grain of salt), I'd emerge -e --keep-going @system, and |
| 4 | > then emerge --resume a few times. You're stuck in something not unlike a |
| 5 | > bootstrap scenario. |
| 6 | |
| 7 | Ok, before I start... |
| 8 | |
| 9 | Michael, if this were you, would you use the 32bit or 64bit kernel when |
| 10 | doing the emerge -e --keep-going system? |
| 11 | |
| 12 | Again, the system was initially rolled out and was always 32 bit... |
| Subject | Author |
|---|---|
| Re: [gentoo-user] Serious problem with linode vm | Michael Mol <mikemol@×××××.com> |
| SOLVED - was Re: [gentoo-user] Serious problem with linode vm | Tanstaafl <tanstaafl@×××××××××××.org> |