On Fri, May 25, 2012 at 09:44:50AM +0200, Cyril Brulebois wrote: > from previous “RAMTMP isn't so bad” IRC sessions, it appears it's > supposed to be on for new installations, and not turned on during > upgrades.
We previously didn't enable this for upgrades primarily because it wasn't possible to. It wasn't possible to upgrade /etc/default/rcS. Also, quite a few people complained about the semantics of RAM* in rcS changing since it used to refer to /var/* rather than the new locations (mainly from RAMRUN and RAMLOCK). To address these concerns, all the RAM* settings were moved to /etc/default/tmpfs, putting all the tmpfs-related settings in a single place. However, this does result in tmpfs being enabled on upgrade. Whether the default is set to enabled or disabled, we now have a single place to configure it, which will take effect for upgrades or new installs. Having a consistent default for both upgrades and new installs is, I think, generally desirable, irrespective of what that default ends up being. What problems did you experience as a result of the change? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
