I think it could help alot if the rescue image has an running sshd. The terminal with the limited size of 80, no mouse, ... makes it very hard to work in this mode - sure it is recue. But if would make it easier, more comfortable, if you could directly connect to this pc. Maybe we can "just add" an menu entry which starts sshd asks or justs shows an password and the current ip address. Or add a simple command on shell to add this feature. I had an remote user which I had to guide through to mount the remote system, bind mount dev, proc, sys, setup vts, chroot, start sshd (systemd does not work in chroot - or I don't know how), so I could finally see, what is going wrong and help him reinstall the efi entries to the bios (which were removed by a bios update). I hope my explantions are clear.
I think what you are suggesting is to enable 'rescue' to be done remotely rather than directly on the PC concerned. Can you confirm this (or say if different)?
CC: (none) => lewyssmith
yes, that's it.
Assigning to the mageiatools people, taking 'rescue' as being part of the Installer.
Assignee: bugsquad => mageiatoolsComponent: RPM Packages => Installer
CC: lewyssmith => (none)
Summary: Rescue: add/start opensshd => Rescue: add/start opensshd option to enable remote rescue.
Blocks: (none) => 33857
close as invalid
Status: NEW => RESOLVEDResolution: (none) => INVALID