From owner-freebsd-stable@FreeBSD.ORG Sat Oct 19 16:52:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 48886FF9 for ; Sat, 19 Oct 2013 16:52:05 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 217B3244D for ; Sat, 19 Oct 2013 16:52:05 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id z10so6267469pdj.16 for ; Sat, 19 Oct 2013 09:52:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=LW0Yk99f1DYniqXQO69SXk4hBehIMWoGQREQravQNGc=; b=OC1frxwBRaUEaRVdwMDqVYQD8aVQ/inBpgIaA4tG+gmUH/e2IRgW/FY3c0hOcsdK/x dKmV72FDAJN2VTo47y9R4fLYkaUBTGAyKQJj/izDzCEy03fR1N9Njbgiur9DKHW3imzG y0GW0Z6utXDC6RJgYqoA1t9KWryR0SU0SlCjSSqLhQ06jZgkszjE2YR3dHF3lv/zC2Pj uSvq/LIHpOa63b9YZs41/i9R7q0im45tONl9Sawa0/81y8r9CBi7r9S4Y+1jjghTYMh9 c/jswYOe8Elmp2eq77b+xvhlTR8SourveT72sJ+hpWXCT8j6oeaJpAbTiJvduB55u27Q HASQ== MIME-Version: 1.0 X-Received: by 10.68.59.38 with SMTP id w6mr8757066pbq.135.1382201524838; Sat, 19 Oct 2013 09:52:04 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Sat, 19 Oct 2013 09:52:04 -0700 (PDT) In-Reply-To: References: <83FF91088F9ADFD31D4A912B@atuin.in.mat.cc> Date: Sat, 19 Oct 2013 09:52:04 -0700 X-Google-Sender-Auth: c9u7UW74IRmRWgjKIHV_BrYdFHY Message-ID: Subject: Re: Going from -STABLE to -RELEASE with freebsd-update support? From: Kevin Oberman To: Michael Sperber Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org Stable" , Mathieu Arnold X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2013 16:52:05 -0000 On Sat, Oct 19, 2013 at 7:57 AM, Michael Sperber wrote: > > Mathieu Arnold writes: > > > One easy way to do it would be to use freebsd-update directly, say you're > > running 8.3-STABLE and want to go to 8.4-RELEASE : > > > > # UNAME_r=8.3-RELEASE freebsd-update -r 8.4-RELEASE upgrade > > > > It'll trick freebsd-update into thinking it's running on 8.3-RELEASE, > which > > is more or less not that untrue, and it'll run the normal upgrade process > > to 8.4. > > Thanks! > > Last I checked, freebsd-update looked at the actual files and their > checksums, and would refuse to run if it doesn't find what it expects. > Will setting UNAME_r override this? > > -- > Regards, > Mike > Another way is to simply update to 8.4-RELEASE and start using freebsd-update from that point. I you are using svn, use the switch command to change the repo branch from stable/8 to release/8.4.0. Then update /usr/src and run the normal 'make' operations to get to 8.4-RELEASE. Make sure that you are either running a GENERIC kernel or install one into /boot. You're ready to go. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com