From owner-freebsd-stable@freebsd.org Tue Apr 19 09:42:21 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AAF4B13526 for ; Tue, 19 Apr 2016 09:42:21 +0000 (UTC) (envelope-from melissa-freebsd@littlebluecar.co.uk) Received: from filter.blacknosugar.com (filter.blacknosugar.com [212.13.204.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDD1F1005 for ; Tue, 19 Apr 2016 09:42:20 +0000 (UTC) (envelope-from melissa-freebsd@littlebluecar.co.uk) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=littlebluecar.co.uk; s=dkim; h=Subject:To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Mime-Version:Content-Type; bh=HNeHIhO7eeVHy+X1ZlfZp2wNzC7IlsojIEr0ku6oAJA=; b=TrQ1nZNVo7zGD4s+JDC5QFF2A Nem3X+OHdc09aW7ThHKuFkr+Mvci4PDc2fnCfUJ+p2+knfmzfeIYesiVcxpHhhdFXJYOZfD/8mLKQ jOwcFbaOOqWcJUvmsnDgWarqKb; Received: from [212.250.79.109] (helo=[192.168.6.47]) by filter.blacknosugar.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.86_2 (FreeBSD)) (envelope-from ) id 1asSAi-0007np-Vk; Tue, 19 Apr 2016 10:42:18 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Melissa Jenkins In-Reply-To: <5715F73F.7050208@grosbein.net> Date: Tue, 19 Apr 2016 10:42:13 +0100 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <45B67BCE-540F-432A-9AA2-192B20312D27@littlebluecar.co.uk> <5715F73F.7050208@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3124) X-SA-Exim-Connect-IP: 212.250.79.109 X-SA-Exim-Mail-From: melissa-freebsd@littlebluecar.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on filter.blacknosugar.com X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: 10.3 and reboot -r (reroot) X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on filter.blacknosugar.com) X-Testing: Hello! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 09:42:21 -0000 My apologies: [root@test:~]# sysctl -A kern.proc.pathname [root@test:~]# kenv vfs.root.mountfrom nfs:nfsserver:/bootenv/10.3 [root@test:~]# kenv vfs.root.mountfrom=3Dzfs:test/root_role vfs.root.mountfrom=3D"zfs:test/root_role" [root@test:~]# reboot -r [root@test:~]#=20 Apr 19 09:35:28 test reroot: rerooted by melissa Apr 19 09:35:28 test init: failed to get kern.proc.pathname: No such = file or directory Apr 19 09:35:28 test init: reroot failed; going to single user mode Apr 19 09:35:28 test root: /etc/rc: WARNING: could not store hostuuid in = /etc/hostid. Apr 19 09:35:31 test root: /etc/rc: WARNING: failed to start dev It actually doesn't do seem to either drop to single user mode or = actually kill anything off. If you reroot to the existing directory it = seems to panic though I don't have a crash file from this. The machine has been booted from a vanilla 10.3 PXE boot. I've then = created a zfs file system on local disks, installed the operating system = in it and would like to 'restart the system into' this new file system. = Normally I'd use the init_script and init_chroot kenv flags but = rerooting seems cleaner and may allow chroots to work better Mel =20 > On 19 Apr 2016, at 10:15, Eugene Grosbein wrote: >=20 > On 19.04.2016 15:06, Melissa Jenkins wrote: >> I've been trying to get reboot -r to work but get an error that = kern.proc.pathname is undefined. It then drops to single user mode. >>=20 >> Interestingly I've checked the value of kern.proc.pathname and it = appears to be undefined on all the OS boxes we have from 9.3 up to = current. In fact the kern.proc tree doesn't appear to contain anything = though it does exist at least on some of the boxes. >>=20 >> I haven't been able to find much about the kern.proc node except the = source code, and there doesn't appear to be anything in the OPTIONS file = that needs to be defined. =20 >>=20 >> This leaves me feeling like I'm missing something obvious!? >>=20 >> Can somebody please point me in the right direction? >=20 > You should show exact command you type and exact error message. >=20 >=20