It's impossible to start compcache... I was need manually use modprobe zram
command. Can't find mistakes in script.
zram package: compcache starting
(5 posts) (3 voices)-
Posted 10 years ago #
-
I'm not sure what you're getting at, but if you have problems with zram not being loaded, add it to the MODULES array in /etc/rcS.conf.
Posted 10 years ago # -
The linux-zram tazpkg owns an init script
/etc/init.d/compcache
and/etc/compcache.conf
in addition to the zram.ko.xz kernel module.Reference:
http://hg.slitaz.org/wok/file/84c0372a9614/linux-zram/stuff/compcache
http://hg.slitaz.org/wok/file/84c0372a9614/linux-zram/stuff/cmpcache.confPosted 10 years ago # -
@necrophcodr
/etc/rcS.conf may be overwritten during update.@mojo
Running/etc/init.d/compcache start
gives error.
Aftermodprobe zram
,then first command TWICE, it works, but must to be only with /etc/init.d/ for starting from tazpanel.here http://hg.slitaz.org/wok/file/84c0372a9614/linux-zram/stuff/compcache
Line 19: modprobe zram num_devices=1 &&
Maybe thisnum_devices=1
is unnecessary and causes errors?Posted 10 years ago # -
If a configuration file such as /etc/rcS.conf is defined on the receipt of it's tazpkg (slitaz-boot-scripts)as $CONFIG_FILES it is not overwritten when the tazpkg is updated.
http://hg.slitaz.org/wok/file/tip/slitaz-boot-scripts/receipt <= line 17Reference: http://doc.slitaz.org/en:cookbook:receipt
$CONFIG_FILES : Some packages provide customized configuration files. The $CONFIG_FILES variable provides a list of these files that can be saved by the 'tazpkg repack-config' command. These files are not overwritten when reinstalling the package if they already exist and the package can be successfully recreated with 'tazpkg repack', (even if they have been modified since).linux-zram: http://hg.slitaz.org/wok/rev/6a53523bda6d
Change:
modprobe zram num_devices=1
to
modprobe zram zram_num_devices=1
I can't figure out how to stop warning.
zram: module is from the staging directory, the quality is unknown, you have been warned.
Posted 10 years ago #
Reply
You must log in to post.