Add a small reminder that users are best of preparing for emergencies. Doesn't cost us much and might prevent data-loss for a few people, as disabling DKMS, installing mainline and other tasks this guide suggest can break the system in you're unlucky. Signed-off-by: Thorsten Leemhuis <linux@xxxxxxxxxxxxx> --- Documentation/admin-guide/reporting-bugs.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Documentation/admin-guide/reporting-bugs.rst b/Documentation/admin-guide/reporting-bugs.rst index 4828e8924136..05de4e0259cb 100644 --- a/Documentation/admin-guide/reporting-bugs.rst +++ b/Documentation/admin-guide/reporting-bugs.rst @@ -549,6 +549,19 @@ See the section 'Duties after the report went out' for details how to get properly involved. +Prepare for emergencies +----------------------- + + *Create a fresh backup and put system repair and restore tools at hand.* + +Reminder, you are dealing with computers, and they sometimes do unexpected +things, especially if you fiddle with crucial parts like the kernel of its +operating system. That's what you are about to do in this process. Thus, make +sure to create a fresh backup; also ensure you have all tools at hand to repair +or reinstall the operating system as well as everything you need to restore the +backup. + + .. ############################################################################ .. Temporary marker added while this document is rewritten. Sections above .. are new and dual-licensed under GPLv2+ and CC-BY 4.0, those below are old. -- 2.26.2
