From 04ee93f1507682b0ef7fdff9b59298918c912c0b Mon Sep 17 00:00:00 2001
From: Colin Guthrie <colin@mageia.org>
Date: Fri, 15 May 2015 15:08:21 +0100
Subject: [PATCH] resume: Do not hardcode the resume= device in the initramfs

While this may make sence for some things (such as LVM + RAID stuff)
we don't want to hold the resume= argument in quite the same regard.

After recent patches this doesn't have quite the same impact as even if
we do embedd the resume ID into our initramfs, the worst it can do is
timeout.
---
 modules.d/95resume/module-setup.sh | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/modules.d/95resume/module-setup.sh b/modules.d/95resume/module-setup.sh
index b964b3e..bf83dbf 100755
--- a/modules.d/95resume/module-setup.sh
+++ b/modules.d/95resume/module-setup.sh
@@ -30,11 +30,6 @@ cmdline() {
 install() {
     local _bin
 
-    if [[ $hostonly_cmdline == "yes" ]]; then
-        cmdline  >> "${initdir}/etc/cmdline.d/95resume.conf"
-        echo  >> "${initdir}/etc/cmdline.d/95resume.conf"
-    fi
-
     # Optional uswsusp support
     for _bin in /usr/sbin/resume /usr/lib/suspend/resume /usr/lib/uswsusp/resume
     do
-- 
2.3.2