You are not logged in.
Pages: 1
It's impossible to start compcache... I was need manually use [c]modprobe zram[/c] command. Can't find mistakes in script.
Offline
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.
Offline
The linux-zram tazpkg owns an init script [c]/etc/init.d/compcache[/c] and [c]/etc/compcache.conf[/c] 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.conf
Offline
@necrophcodr
/etc/rcS.conf may be overwritten during update.
@mojo
Running [c]/etc/init.d/compcache start[/c] gives error.
After [c]modprobe zram[/c] ,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 this [c]num_devices=1[/c] is unnecessary and causes errors?
Offline
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 17
Reference: 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:
[c]modprobe zram num_devices=1[/c]
to
[c]modprobe zram zram_num_devices=1[/c]
I can't figure out how to stop warning.
[c]zram: module is from the staging directory, the quality is unknown, you have been warned.[/c]
Offline
Pages: 1
[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]