I was using a LiveCD to tar up some filesystems on an existing installation. Since some of the filesystems were large, I walked away after starting the tar jobs. I come back to find the computer has suspended. The computer does not successfully wake back up. The filesystem to which I was writing the tar files did not get sync’d or unmounted, so it had issues when I restarted the system. The end result is I had to redo everything I had done (after disabling auto-suspend).
If I recall correctly, suspend is not 100% guaranteed to work on all hardware. As such, suspend is something that users should only do once they are sure it works for their computer. (Meaning, they try suspending manually a few times. If it works, then sure, enable auto-suspend.)
There are legal requirements around power saving that the default suspend is meeting. I would be surprised if your requested would be implemented.
But you could raise a bug report with your suggestion and get the maintainers response.
However you can go into the power settings and turn off the suspend that would meet your needs.
Yes, I remembered to turn it off when I repeated the backup. I just know I’m not going to remember the next time I use a LiveCD. Seems odd to have a legal requirement that risks crashing a computer [and possibly corrupting a filesystem]. Even a reminder or dialog prompt that gets displayed after the install-Fedora-or-try-Fedora dialog would be good.
There is a movement to reduce the carbon foot print of computing.
The suspend after idle is part of that. May not have legal force for a live cd,
But seems to be policy for Fedora offering.
As I suggested raising a ticket would be the way to know what the maintainers think.
You might also look into running things like this using systemd-inhibit, which will prevent sleep, shutdown, etc. from happening. I use this in my backup scripts so they run to completion.