From owner-freebsd-questions@FreeBSD.ORG Tue Sep 23 08:59:27 2014 Return-Path: Delivered-To: freebsd-questions@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 ESMTPS id 989E1813 for ; Tue, 23 Sep 2014 08:59:27 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0132.outbound.protection.outlook.com [157.56.111.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3188566B for ; Tue, 23 Sep 2014 08:59:26 +0000 (UTC) Received: from [IPv6:2601:2:4780:2fd:3cfa:1b41:db29:34df] (2601:2:4780:2fd:3cfa:1b41:db29:34df) by BY1PR0301MB0838.namprd03.prod.outlook.com (25.160.193.144) with Microsoft SMTP Server (TLS) id 15.0.1034.13; Tue, 23 Sep 2014 08:43:11 +0000 Message-ID: <5421328A.1030209@my.hennepintech.edu> Date: Tue, 23 Sep 2014 03:42:50 -0500 From: Andrew Berg User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Subject: freebsd-update won't update userland Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [2601:2:4780:2fd:3cfa:1b41:db29:34df] X-ClientProxiedBy: BY2PR07CA074.namprd07.prod.outlook.com (10.141.251.49) To BY1PR0301MB0838.namprd03.prod.outlook.com (25.160.193.144) X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0301MB0838; X-Forefront-PRVS: 0343AC1D30 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(107886001)(21056001)(92566001)(102836001)(87266999)(83506001)(79102003)(42186005)(92726001)(107046002)(50986999)(77096002)(2351001)(80022003)(59896002)(20776003)(4396001)(90102001)(110136001)(64706001)(65816999)(120916001)(46102003)(76482002)(99136001)(10300001)(23676002)(106356001)(83322001)(229853001)(50466002)(81542003)(95666004)(33656002)(97736003)(64126003)(88552001)(89122001)(74502003)(74662003)(47776003)(85852003)(81342003)(77982003)(31966008)(101416001)(75432002)(85306004)(86362001)(54356999)(99396002)(65956001)(87976001)(105586002)(83072002)(65806001)(89472002)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0301MB0838; H:[IPv6:2601:2:4780:2fd:3cfa:1b41:db29:34df]; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:0; LANG:en; X-OriginatorOrg: my.hennepintech.edu X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 08:59:27 -0000 I just upgraded from 10.0-RELEASE to 10.1-BETA2, and after rebooting into the new kernel, I accidentally ran 'freebsd-update fetch install', which seems to have put freebsd-update into a state where it thinks that I am completely updated (because it only checks the kernel and there are no security updates available for 10.1-BETA2). # freebsd-version -ku 10.1-BETA2 10.0-RELEASE-p9 # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. # ls -l /var/db/freebsd-update/files | wc -l 80930 The timestamps on the freebsd-update files are from when I went through the initial update process. Is it possible to get freebsd-update to see that it didn't complete the update or must I build world and resolve the configuration file conflicts again?