Re: [gentoo-amd64] About to install on a 64 bit system. Advice wanted.

[Mateusz Arkadiusz Mierzwinski]

Dale, I tell You one thing - choose multilib. This don't do nothing wrong.
You can use 32-bit app compatibility and this don't reduce performance of
overall system. Easyest way for Me is:

- boot minimal CD
- format drive (partitioned allready)
- fetch with links stage3 od amd64
- fetch portage
- unpack
- mounting binded dev and mounting proc, copy resolv.conf
- chroot and update environment by env-update, source
- set environment (timezone, fstab, net)
- emerge some standard packages (vixie-cron, syslog-ng, dhcp, dbus, hal,
udev) and making global system update (-uva --deep system), setting USE
flags and CXXFLAGS as needed.
- emerge lilo, genkernel, gentoo-sources
- setting genkernel with menuconfig and run kernel compilation
- configure lilo ;) and running lilo.
- reboot
- emerging rest of software - aka KDE4 - this will push all packages needed
(aka. kde-meta will take deps like xorg, mesa and else so You don't have to
worry about - enable hal flag for convenience :) ).

Done! Works for me, without any incovenience, as You see nothing strange
happens, os is working without any strange things to do. You can set now KDE
profile, it should be listed by eselect for portage optimization.

One You should do: choose lilo - it's old, it's good, it's tested.
Configuration is fast and it's up and runnning in no time. Multilib you
should set for some applications compatibility if You will fetch in future
some deb/rpm packages from third party companies.


Be aware _lastest_ available in portage flash player - it has no support for
64bit browser (i don't know why). I've needed to get downgrade by hand. Now
after each upgrade flash player must be downgraded by hand (sic!) i will
mask it in packages.mask localy ;).

That's it - pure purity (64-bit only) can make you sick later, ill tell You
;)


2010/12/9 Paul Jewell <paul@×××××.org>

> 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!
>
> Rgds.,
> Paul
> -----Original Message-----
> From: Florian Philipp <lists@f_philipp.fastmail.net>
> Date: Thu, 09 Dec 2010 10:48:29
> To: <gentoo-amd64@l.g.o>
> Reply-to: gentoo-amd64@l.g.o
> Subject: Re: [gentoo-amd64] About to install on a 64 bit system. Advice
> wanted.
>
> Am 09.12.2010 06:29, schrieb Dale:
> > Mateusz Arkadiusz Mierzwinski wrote:
> [...]
> >>     Frank Peters wrote:
> >>
> >>         On Wed, 08 Dec 2010 15:17:18 -0600
> >>         Dale<rdalek1967@×××××.com <mailto:rdalek1967@×××××.com>>
>  wrote:
> [...]
> >>             What are some things that I should watch for and enable
> >>             that isn't so
> >>             obvious for someone new to 64 bit?
> [...]
> >>         The first thing to decide is whether or not you want a pure
> 64-bit
> >>         system or a 64-bit system that keeps 32-bit capability.
> >>
> >>         I am a purist.  I left 32-bit programs in the dust a long time
> >>         ago.
> >>         But as a consequence there are some things that I will miss
> >>         because
> >>         they are available in 32-bit packages only.  An example would be
> >>         Acroread, the PDF viewer, from Adobe.  Without Acroread, you
> will
> >>         only view pdf files through the 64-bit xpdf.  The Intel C++
> >>         compiler is another example.  In fact, most commercial software
> >>         that bothers to release a Linux version will do so in 32-bit
> >>         format only.
> [...]
> >> You can set it in KERNEL by disabling 32 bit application support and
> >> recompiling GLIBC and GCC without MULTILIB ;). Try also running 32 bit
> >> app. System is not slower or anything else wrong happens. If You drop
> >> 32-bit support You cannot use WINE and load PE32 apps (aka Win32).
> >>
> [...]
> > I don't use Wine.  I have never heard of PE32 so I don't guess I have a
> > need for it either.  lol   It sounds like I should go pure 64 bit.
> > Anyone disagree with that?  Someone mentioned pdf files but I can use
> > KDE's program for that as I do now.  I can use OOo as a backup too.
> > [...]
>
> Didn't you post on gentoo-user that you watch youtube videos? Well, the
> currently stable version of adobe-flash (10.1.102.64) is 32bit-only.
> That will change again with the next higher version in the tree but the
> switch to 32bit can happen again when Adobe decides once again that it
> doesn't need to fix its security bugs for amd64.
>
> You might also want to think about pre-compiled OSS applications in
> portage (`eix -- -bin`). Not all of them come in pure 64bit flavor.
>
> AFAIK there are only two reasons to avoid a multilib setup:
> 1. Disk space (~230MB on my system)
> 2. Compile time on packages that support multilib.
>
> I don't think either of these will be an issue for your new system ;)
> IMHO the increased flexibility is well worth the effort.
>
> Hope this helps,
> Florian Philipp
>
>
>


-- 
Mateusz Mierzwiński

Bluebox Software http://www.blueboxsoft.pl/mateusz-mierzwinski