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=zfs:test/root_role vfs.root.mountfrom="zfs:test/root_role" [root@test:~]# reboot -r [root@test:~]#
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 > On 19 Apr 2016, at 10:15, Eugene Grosbein <eu...@grosbein.net> wrote: > > 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. >> >> 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. >> >> 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. >> >> This leaves me feeling like I'm missing something obvious!? >> >> Can somebody please point me in the right direction? > > You should show exact command you type and exact error message. > > _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
