Date: Fri, 15 Dec 2006 17:24:20 -0900 From: Beech Rintoul <beech@alaskaparadise.com> To: freebsd-questions@freebsd.org Cc: Old Ranger <ranger@oldpathsbaptistchurch.org> Subject: Re: cvsup and amd64 Message-ID: <200612151724.24112.beech@alaskaparadise.com> In-Reply-To: <200612151818.08425.ranger@oldpathsbaptistchurch.org> References: <ADA47EFE15ACA74E8B702B6EF90D913907523A34@UTDEVS08.campus.ad.utdallas.edu> <200612151818.08425.ranger@oldpathsbaptistchurch.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1216358.kvGJVCPNgr Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 15 December 2006 16:18, Old Ranger wrote: > On Friday 15 December 2006 18:04, Schmehl, Paul L wrote: > > Please tell me, did I need to specify anything specifically about the > > amd64 architecture when running cvsup? Did I possibly get a GENERIC > > kernel file through cvsup that is not compatible with amd? > > > > ********************************************************************** > > > > Sorry for the horrible formatting, but for reasons beyond my control, I > > only have access to Microsoft Outlook right now. It appears no one has > > answered you yet, so, to alleviate your fears, yes, unless you've chang= ed > > the kernel in any way (and it sounds like you haven't), a simple make > > buildkernel and make installkernel should work just fine. Reboot > > afterwards, and you should be running the new kernel. The only reason > > you would *need* to make a change would be if you're running dual > > processors or you need to customize the kernel for performance reasons.= =20 > > Otherwise the GENERIC kernel will suffice. > > > > Paul Schmehl (pauls@utdallas.edu) > > Senior Information Security Analyst > > University of Texas at Dallas > > http://www.utdallas.edu/ir/security/ > > **** > > Thank you! > Somehow, I got through it today, with SMP working too! > > I had a little problem with mergemaster, after buildworld, which had a > couple of problems that I got around with the make -k argument. > Some things didn't get built. > > > Mergemaster rejected some files - /var/tmp/temproot/etc/rc.d/jail > /var/tmp/temproot/etc/ssh/ssh_config > /var/tmp/temproot/etc/ssh/sshd.config > /var/tmp/temproot/etc/motd > > I elected to "merge by hand", just to coplete the process. > Now I'll have to learn what it means to "merge by hand." > > Thanks to all who responded with advice and insights. > > I have now a working amd64x2 kernel and a partially built, installed, and > merged world. > > There are still some strange messages appearing at boot time. > > That's for another day. Merge by hand means to go to /usr/src/etc and copy the files you need to /e= tc=20 then add in any changes by hand. Since you are doing a fresh install, just= =20 copy the files to /etc and you should be fine. Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - Sys. Administrator - beech@alaskaparadise.com /"\ ASCII Ribbon Campaign | Alaska Paradise Travel \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com =2D------------------------------------------------------------------------= =2D------------- --nextPart1216358.kvGJVCPNgr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBFg1jXp5D0B1NlT4URAu93AJwKSa56GgBrsNUcLMaXHFDtAv+5qgCbBTvZ 8N59pzoDIqdpUSWiFZiFc9c= =akSh -----END PGP SIGNATURE----- --nextPart1216358.kvGJVCPNgr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612151724.24112.beech>