Difference between revisions of "Talk:Zswap"

From ArchWiki
Jump to navigation Jump to search
(highlight importance of dmesg)
 
Line 2: Line 2:
 
It is still important to know how to check the config with {{ic|<nowiki>$ dmesg | grep zswap</nowiki>}} in order to know what was originally loaded by the system, runtime parameters can differ from boot time because some processes altered it like systemd-zswap. I would recommend to add it back.
 
It is still important to know how to check the config with {{ic|<nowiki>$ dmesg | grep zswap</nowiki>}} in order to know what was originally loaded by the system, runtime parameters can differ from boot time because some processes altered it like systemd-zswap. I would recommend to add it back.
 
[[User:Kewl|Kewl]] ([[User talk:Kewl|talk]]) 19:50, 19 December 2017 (UTC)
 
[[User:Kewl|Kewl]] ([[User talk:Kewl|talk]]) 19:50, 19 December 2017 (UTC)
 +
 +
== Adding compression modules to ramdisk ==
 +
 +
Is there any particular reason the example uses the {{ic|# mkinitcpio -g /boot/initramfs.img}} command instead of {{ic|# mkinitcpio -p <preset_name>}}?
 +
--[[User:Crashlog|Crashlog]] ([[User talk:Crashlog|talk]]) 09:42, 17 February 2018 (UTC)

Revision as of 09:42, 17 February 2018

initial config

It is still important to know how to check the config with $ dmesg | grep zswap in order to know what was originally loaded by the system, runtime parameters can differ from boot time because some processes altered it like systemd-zswap. I would recommend to add it back. Kewl (talk) 19:50, 19 December 2017 (UTC)

Adding compression modules to ramdisk

Is there any particular reason the example uses the # mkinitcpio -g /boot/initramfs.img command instead of # mkinitcpio -p <preset_name>? --Crashlog (talk) 09:42, 17 February 2018 (UTC)