Date: Thu, 11 Dec 2003 19:20:33 -0700 From: Joe Fenton <jlfenton@citlink.net> To: freebsd-amd64@freebsd.org Subject: Re: Packages/Ports problem Message-ID: <3FD925F1.1070207@citlink.net> In-Reply-To: <20031211200037.37CDD16A4D8@hub.freebsd.org> References: <20031211200037.37CDD16A4D8@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Adriaan de Groot wrote: > > > On Wednesday 10 December 2003 21:45, Jimmie Houchin wrote: > > > > As an alternative, if you've got a spare i386 box sitting around, you could > > install FreeBSD on that too, and install the i386 cvsup package on it. Then > > use that cvsup to update the sources and ports trees (you can share source > > and ports trees with NFS). > > Well I have an Athlon 700mhz desktop, which I am considerig switching to > FreeBSD after I move some data off of the spare drive. http://www.onlamp.com/pub/a/bsd/2002/05/09/Big_Scary_Daemons.html This shows how to make a dual-boot setup. In this case, he is setting up his computer to boot FreeBSD -current or FreeBSD -release. Use the same method to set up FreeBSD i3686 and FreeBSD amd64. I did that on my Opteron workstation. If strange things happen in amd64, you can reboot into i386 and try to figure things out from there. Set up three slices - one for i386, one for amd64, and a common slice. This same site has a very good article on setting up your FreeBSD to handle kernel panics using the swap partition as has been mentioned a few times recently.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FD925F1.1070207>