Working on implementing option 2, I noticed that friendly-recovery depends on whiptail which is in /usr/bin.
We're not going to be moving whiptail and libnewt out of /usr this cycle but it's definitely something that should happen for next cycle (opening bug tasks for these two).
For now, friendly-recovery itself will be in /lib and will simply drop to a root shell if /urs/bin/whiptail can't be accessed.
Whenever we move whiptail to /bin we should also make sure nothing currently refers to it with an hardcoded path as friendly-recovery used to do.
Working on implementing option 2, I noticed that friendly-recovery depends on whiptail which is in /usr/bin.
We're not going to be moving whiptail and libnewt out of /usr this cycle but it's definitely something that should happen for next cycle (opening bug tasks for these two).
For now, friendly-recovery itself will be in /lib and will simply drop to a root shell if /urs/bin/whiptail can't be accessed.
Whenever we move whiptail to /bin we should also make sure nothing currently refers to it with an hardcoded path as friendly-recovery used to do.