On Thu, 2012-05-31 at 02:40 +0200, Lennart Poettering wrote: > Heya! > > Please be aware that since the most recent systemd uploads /tmp is now > in tmpfs by default in Rawhide/F18. > > For details please see this feature page: > > https://fedoraproject.org/wiki/Features/tmp-on-tmpfs > > If you have an explicit /tmp entry in fstab things should continue to > work the same as before. If you don't then you will now get a tmpfs on > /tmp by default. > > This will most likely lead to a problem or two with software that isn't > happy about /tmp being small. We have created a tracker bug to keep > track of this: > > https://bugzilla.redhat.com/show_bug.cgi?id=826015 > > If you have identified a bug that is triggered by /tmp being on tmpfs > now, please add it to this tracker bug! > > For a bit of background on all of this and recommendations for > developers, please see: > > http://0pointer.de/blog/projects/tmp.html
Lennart is there any smarts about it based on available RAM ? I regularly install VMs with < 1GiB of RAM and /tmp in RAM would make them unusable. On a development laptop with 4GiB of RAM and many VMs I would still find /tmp in RAM a bit of a stretch, but whatever. So is there any smarts there that disable this feature when there is little RAM available from the get go ? Simo. -- Simo Sorce * Red Hat, Inc * New York -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
