I encountered the same thing here. Remastersys required casper, and
casper set the compcache to 50%.
Regardless of the fact that it may be a good thing performance wise, I
still think it's not something that should happen without the user's
knowledge.
I had to waste quite a bit of time to find
It might make sense to do an additional run-time check to see if you
booted with boot=casper, and otherwise not set this variable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933712
Title:
casper
i am closing this bug for two reasons:
a) having compcache enabled isnt actually a bad thing, it raises the amount of
usable ram with no known drawbacks (and i dont know what you refer to regarding
a poor experience)
b) on normal installs casper is not installed, during installation casper (and
To elaborate on Oli's no known drawbacks comment, I think it's clear
that some people don't understand how zram works. While you're telling
it that you can use up to 50% of your RAM for compressed swap, that
doesn't actually kick in until you run out of RAM, precisely the point
where you'd
More information as to how Casper ended up on my laptop:
I installed the usb-creator on Oneiric, which required lupin-capser,
which pulled in casper. I upgrade from Oneiric to Precise on 2012-01-07.
On 2012-02-01, my host picked up the version of Casper which has the
compcache setting.
--
You
casper is not installed on the target system during the installation
process and afaict usb-creator doesn't require capser or lupin-casper so
I'm really not sure what happened to your system.
Additionally, compcache (according to the casper changelog) should only
be used on systems (running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933712
Title:
casper configures system to use 50% ram for compressed swap post
installation
To manage notifications about this bug go to:
