Date: Sun, 8 Jul 2007 07:29:05 -0700 From: David Wolfskill <david@catwhisker.org> To: Marc UBM Bocklet <ubm@u-boot-man.de> Cc: freebsd-current@freebsd.org Subject: Re: status of 7.0 Message-ID: <20070708142905.GB22374@bunrab.catwhisker.org> In-Reply-To: <20070708132545.5604cbe9.ubm@u-boot-man.de> References: <8cdf6c720707070710k2b7e030v37683e460d983bf9@mail.gmail.com> <20070708111105.C9997@fledge.watson.org> <20070708132545.5604cbe9.ubm@u-boot-man.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--+pHx0qQiF2pBVqBT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 08, 2007 at 01:25:45PM +0200, Marc UBM Bocklet wrote: > ... > I'd like to do some testing, but I'm a little bit afraid of the upgrade > procedure 6.2-stable to -current. Is it possible to do a simple upgrade > if I follow the guidelines in UPGRADE or are there any hidden caveats? > (like "you've to recompile all installed ports", etc. :-)) It hasn't been a problem in my experience to date. Each of the 4 slices on my laptop is bootable, with its own / and /usr; the swap space and all other file systems are mounted in the same logical places in the tree (such as /var and /home --and in direct response to your query, /usr/local is a symlink to a place in one of these common file systems). I just finished building today's STABLE (RELENG_6) on slice 1, then updated all installed ports that warranted it; I'm now updating today's CURRENT (HEAD) on slice 4: g1-1(7.0-C)[1] uname -a FreeBSD g1-1.catwhisker.org. 7.0-CURRENT FreeBSD 7.0-CURRENT #476: Sat Jul = 7 10:00:45 PDT 2007 root@g1-1.catwhisker.org.:/common/S4/obj/usr/src/s= ys/CANARY i386 g1-1(7.0-C)[2]=20 Up until the recent 802.11 code overhaul, CURRENT had been working quite well for me, though I normally only run it while I'm building CURRENT, doing a reality check or two, or some testing for one of the developers. Since that point, my miniPCI wi0 NIC won't associate, so I've fallen back to a PCMCIA an0, which mostly works (but flakes out with a "kernel: an0: xmit failed" message every once in a while; I've found that forcing re-association appears to circumvent the connection-dropping that otherwise results, though that's a gross hack). And I think I goit through the recent sed(1) issues; there weren't many changes in CURRENT in the last 24 hrs. :-} Peace, david --=20 David H. Wolfskill david@catwhisker.org Anything and everything is a (potential) cat toy. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --+pHx0qQiF2pBVqBT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkaQ9K4ACgkQmprOCmdXAD3wPACfT4zUoU0ucgxpZ8KcaYlqEw5a Y7YAnRfWljW3AYxRVKfRC6x3RUgsQU28 =RHwo -----END PGP SIGNATURE----- --+pHx0qQiF2pBVqBT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070708142905.GB22374>