Will do - it behaves the same even without PXE. I believe the issue is that kern.proc.pathname does not exist on any of my systems
Mel > On 19 Apr 2016, at 11:19, Eugene Grosbein <eu...@grosbein.net> wrote: > > CCing Edward Tomasz Napierala, "Root Remount" project contact. > > On 19.04.2016 16:42, Melissa Jenkins wrote: >> 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 > > It seems, reroot currently does not work for PXE-booted systems. > You should fill a PR. > _______________________________________________ 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"
