Date: Wed, 24 Feb 2016 06:02:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207069] setting loader password in loader.conf disallows boot Message-ID: <bug-207069-8-Ti5VLyYWF0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207069-8@https.bugs.freebsd.org/bugzilla/> References: <bug-207069-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207069 --- Comment #1 from david@dcrosstech.com --- Created attachment 167348 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D167348&action= =3Dedit Works for me! uses getenv on 'kernelname' to see if the kernel is loaded (copied from oth= er places in the code), if it is, calls load_kernel and load_modules (attempted with load_kernel_and_modules, but that was throwing a stack underflow, and I don't understand the code well enough to just throw things onto the stack, other parts of the code was also calling load_kernel and load_modules separately), and then continue and execute autoboot as normal, restoring the functionality from 10.1 and earlier. Testing under the following conditions: 1) no password set -- doesn't delay boot, or interfere with anthing as expected 2) password set -- autboot as designed, asks for password if interrupted. 3) password set and kernel loaded -- does not attempt to reload kenrel or modules, continutes with autoboot 4) zfs_load=3D"yes" set in loader.conf loads kernel and zfs module, contin= ues with autoboot. Untested:modules loaded, but no kernel. Is this even legal/supported? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207069-8-Ti5VLyYWF0>