Roger Leigh <rle...@codelibre.net> (25/05/2012): > 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.
Changing the default on upgrades in *not* acceptable. > What problems did you experience as a result of the change? ENOSPC while I have 100's of GB free on that fucking disk I've always been using. Breaking random apt-get source, breaking random chroot creation, breaking more or less anything I'm used to use /tmp for. (Why? Because I don't have to worry about the space there, and on getting stuff cleaned at some point.) Mraw, KiBi.
signature.asc
Description: Digital signature
