Date: Sat, 4 Feb 2006 09:41:55 +0000 (UTC) From: Denny White <dennyboy@cableone.net> To: Xn Nooby <xnooby@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Why does portsdb -Uu run so long? Message-ID: <Pine.BSO.4.63.0602040937090.12419@badboybox.cableone.net> In-Reply-To: <bdf25fde0602032318u7e01d789u58fe877c25e574cd@mail.gmail.com> References: <bdf25fde0602010241i30ed79c9x2818c3fa35abf731@mail.gmail.com> <ef10de9a0602032110g5ff97760tb6ead7a638c1ed86@mail.gmail.com> <bdf25fde0602032318u7e01d789u58fe877c25e574cd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today Xn Nooby spake forth boldly: >> It just does, after you cvsup new ports cd into /usr/ports and type >> make fetchindex. what way is the "old foolproof way"? >> > > Here is how I update my system (without using a 'make fetchindex') > > cvsup -g -L 2 /root/stable-supfile > less UPDATING > make buildworld > make buildkernel > make installkernel > shutdown now > cd /usr/src > make installworld > mergemaster > shutdown -r now > portsdb -Uu > portversion -l "<" > portupgrade -arR > reboot > > It takes forever, but it works everytime. Everything else I've ever tried > has always had some kind of error, and I never know what they mean or what I > should do. > > Maybe by never doing a fetchindex, I've never really updated my system, and > thats why its never had a problem, lol. That would be embarassing. > _______________________________________________ Try portsdb -uUF Please do not CC me. Already subscribed to mailing list. GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (OpenBSD) iD8DBQFD5Hbsy0Ty5RZE55oRAlr9AJ0XLqkm4vTDasR1PDRSCbl9e2+VKACfU4XQ oHFZVw5HuVkkrhs6Yuy7S1s= =NXHH -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSO.4.63.0602040937090.12419>