| 1 |
felix@×××××××.com wrote: |
| 2 |
> On Sat, Sep 15, 2012 at 12:45:51AM +0100, Kerin Millar wrote: |
| 3 |
>> felix@×××××××.com wrote: |
| 4 |
>>> I have a shiny new System76 laptop with a "3rd Generation Intel Core i7-3720QM Processor (2.60GHz 6MB L3 Cache - 4 Cores plus Hyperthreading)". |
| 5 |
>>> |
| 6 |
>>> It comes with Ubuntu, so naturally my first move was to split the Ubuntu partition in half and install gentoo. I will say no more about my first experiences with Unity. |
| 7 |
>>> |
| 8 |
>>> The Ubunto uname -a says "3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux". |
| 9 |
>> Take note - it's a x86_64 host environment. |
| 10 |
>> |
| 11 |
>>> I installed the latest stage3 tarball and set up make.conf as |
| 12 |
>> Which stage3 tarball exactly? |
| 13 |
> |
| 14 |
> Maybe that's part of my confusion -- I was following the x86 handbook, not amd64, because it's not amd. But if amd64 should be used for all 64 bit installs, that's probably my problem. |
| 15 |
> |
| 16 |
> As for the exact stage3 tarball, the ftp choice was "gentoo/releases/x86/current-stage3". This was about Sep 10. |
| 17 |
> |
| 18 |
|
| 19 |
It will work if you chroot as described in my previous message. linux32 |
| 20 |
is a symlink to setarch so you can read the setarch manpage if you're |
| 21 |
curious as to why it is necessary. Still, unless you have a particular |
| 22 |
reason not to avoid using an amd64 stage tarball, I'd suggest starting |
| 23 |
over with one. |
| 24 |
|
| 25 |
--Kerin |
Archives