what to do? amd64 - i386

dick hoogendijk dick at nagual.st
Sun Jul 31 18:47:15 GMT 2005


On Sun, 31 Jul 2005 19:38:01 +0200
Benjamin Lutz <benlutz at datacomm.ch> wrote:

> Yes. Ports that are known not to build on certain architectures have an
> ONLY_FOR_ARCH flag set. Eg:
> 
>   cd /usr/ports/www/opera; make -V ONLY_FOR_ARCH

Just tried this, but got no response. Maybe it works now.

> There are a few things that will not work at all on amd64 right now,
> however: OpenOffice.org, proprietary media codecs, hardware OpenGL
> acceleration...

Any ideas about _WHAT_ does not work? Do you have examples?
"If I can't live without them, then.." ;-))

> Personally, I have two installations of FreeBSD, both i386 and amd64.
> They share /home. i386 is my production version, and the amd64
> installation is for playing around (or when the added speed comes in
> handy). Why not try that arrangement. That way you can periodically
> check up on FreeBSD/amd64's progress and decide yourself when you want
> to switch.

Sounds nice, although I'm not that keen on keeping too much systems
up2date. Takes too much time.. My main (internet) server still runs on
4.11-stable. I have begun to explore 5.4 to get familiar with the new
system but find it to be not ready for 24/7. I.e. I use ipfilter which
seems to be unstable on 5.4. I don't want to change to pf just for that
reason. Maybe 5.5 will be a better point to change the server. It's
always difficult to find the right point in time to make such a
switch ;)

-- 
dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja


More information about the freebsd-questions mailing list