1 |
When I installed my system back in January, I started off with 64 bit only, and immediately hit a problem with grub compilation. I switched to multilib, and the installation went smoothly. I would recommend Pappy's seeds as a starting point for kernel configuration. Even if you don't use his seed, the debian resource to identify drivers is useful. If you need a link, I'll sort it out when I get home. I have not had any issues with the multilib setup, and compared to my old AthlonXP system it flies!
|
2 |
|
3 |
Rgds.,
|
4 |
Paul
|
5 |
-----Original Message-----
|
6 |
From: Florian Philipp <lists@f_philipp.fastmail.net>
|
7 |
Date: Thu, 09 Dec 2010 10:48:29
|
8 |
To: <gentoo-amd64@l.g.o>
|
9 |
Reply-to: gentoo-amd64@l.g.o
|
10 |
Subject: Re: [gentoo-amd64] About to install on a 64 bit system. Advice wanted.
|
11 |
|
12 |
Am 09.12.2010 06:29, schrieb Dale:
|
13 |
> Mateusz Arkadiusz Mierzwinski wrote: |
14 |
[...]
|
15 |
>> Frank Peters wrote: |
16 |
>> |
17 |
>> On Wed, 08 Dec 2010 15:17:18 -0600 |
18 |
>> Dale<rdalek1967@×××××.com <mailto:rdalek1967@×××××.com>> wrote: |
19 |
[...]
|
20 |
>> What are some things that I should watch for and enable |
21 |
>> that isn't so |
22 |
>> obvious for someone new to 64 bit? |
23 |
[...]
|
24 |
>> The first thing to decide is whether or not you want a pure 64-bit |
25 |
>> system or a 64-bit system that keeps 32-bit capability. |
26 |
>> |
27 |
>> I am a purist. I left 32-bit programs in the dust a long time |
28 |
>> ago. |
29 |
>> But as a consequence there are some things that I will miss |
30 |
>> because |
31 |
>> they are available in 32-bit packages only. An example would be |
32 |
>> Acroread, the PDF viewer, from Adobe. Without Acroread, you will |
33 |
>> only view pdf files through the 64-bit xpdf. The Intel C++ |
34 |
>> compiler is another example. In fact, most commercial software |
35 |
>> that bothers to release a Linux version will do so in 32-bit |
36 |
>> format only. |
37 |
[...]
|
38 |
>> You can set it in KERNEL by disabling 32 bit application support and |
39 |
>> recompiling GLIBC and GCC without MULTILIB ;). Try also running 32 bit |
40 |
>> app. System is not slower or anything else wrong happens. If You drop |
41 |
>> 32-bit support You cannot use WINE and load PE32 apps (aka Win32). |
42 |
>> |
43 |
[...]
|
44 |
> I don't use Wine. I have never heard of PE32 so I don't guess I have a |
45 |
> need for it either. lol It sounds like I should go pure 64 bit. |
46 |
> Anyone disagree with that? Someone mentioned pdf files but I can use |
47 |
> KDE's program for that as I do now. I can use OOo as a backup too. |
48 |
> [...] |
49 |
|
50 |
Didn't you post on gentoo-user that you watch youtube videos? Well, the
|
51 |
currently stable version of adobe-flash (10.1.102.64) is 32bit-only.
|
52 |
That will change again with the next higher version in the tree but the
|
53 |
switch to 32bit can happen again when Adobe decides once again that it
|
54 |
doesn't need to fix its security bugs for amd64.
|
55 |
|
56 |
You might also want to think about pre-compiled OSS applications in
|
57 |
portage (`eix -- -bin`). Not all of them come in pure 64bit flavor.
|
58 |
|
59 |
AFAIK there are only two reasons to avoid a multilib setup:
|
60 |
1. Disk space (~230MB on my system)
|
61 |
2. Compile time on packages that support multilib.
|
62 |
|
63 |
I don't think either of these will be an issue for your new system ;)
|
64 |
IMHO the increased flexibility is well worth the effort.
|
65 |
|
66 |
Hope this helps,
|
67 |
Florian Philipp |