54 messages in org.freebsd.freebsd-currentRe: Using TMPFS for /tmp and /var/run?| From | Sent On | Attachments |
|---|---|---|
| O. Hartmann | Mar 29, 2012 7:17 am | |
| David Wolfskill | Mar 29, 2012 9:14 am | |
| Chris Rees | Mar 29, 2012 9:41 am | |
| Vitaly Magerya | Mar 29, 2012 9:59 am | |
| O. Hartmann | Mar 29, 2012 12:49 pm | |
| Eric van Gyzen | Mar 29, 2012 12:49 pm | |
| David Wolfskill | Mar 29, 2012 12:57 pm | |
| O. Hartmann | Mar 29, 2012 1:06 pm | |
| David Wolfskill | Mar 29, 2012 1:13 pm | |
| Xin Li | Mar 29, 2012 1:49 pm | |
| Eric van Gyzen | Mar 29, 2012 1:51 pm | |
| Xin Li | Mar 29, 2012 1:52 pm | |
| Matt Thyer | Mar 30, 2012 5:50 am | |
| sth...@nethelp.no | Mar 30, 2012 6:18 am | |
| Chris Rees | Mar 30, 2012 7:42 am | |
| jb | Mar 30, 2012 8:16 am | |
| Lucas Holt | Mar 30, 2012 8:28 am | |
| sth...@nethelp.no | Mar 30, 2012 10:14 am | |
| C. P. Ghost | Mar 30, 2012 10:31 am | |
| Chris Rees | Mar 30, 2012 10:55 am | |
| Steve Kargl | Mar 30, 2012 11:15 am | |
| matt | Mar 30, 2012 11:25 am | |
| Adrian Chadd | Mar 30, 2012 12:36 pm | |
| Chris Rees | Mar 30, 2012 12:41 pm | |
| Adrian Chadd | Mar 30, 2012 12:44 pm | |
| deep...@gmail.com | Mar 30, 2012 5:57 pm | |
| Adrian Chadd | Mar 30, 2012 6:59 pm | |
| Benjamin Kaduk | Mar 30, 2012 7:05 pm | |
| jb | Mar 30, 2012 7:47 pm | |
| Matthias Andree | Mar 30, 2012 11:07 pm | |
| Matthias Andree | Mar 30, 2012 11:15 pm | |
| Matthew Seaman | Mar 31, 2012 12:30 am | |
| Gary Palmer | Apr 1, 2012 6:40 am | |
| Rainer Duffner | Apr 1, 2012 7:14 am | |
| jb | Apr 1, 2012 12:54 pm | |
| deep...@gmail.com | Apr 1, 2012 3:49 pm | |
| Warren Block | Apr 1, 2012 7:14 pm | |
| grarpamp | Apr 2, 2012 2:41 am | |
| Gleb Kurtsou | Apr 2, 2012 3:30 am |  .txt |
| David Wolfskill | Apr 2, 2012 3:59 am | |
| David Wolfskill | Apr 2, 2012 6:26 am | |
| jb | Apr 2, 2012 8:46 am | |
| Chris Rees | Apr 2, 2012 8:51 am | |
| Gleb Kurtsou | Apr 2, 2012 2:03 pm | .txt |
| Chuck Burns | Apr 2, 2012 3:05 pm | |
| Doug Barton | Apr 2, 2012 3:22 pm | |
| John Baldwin | Apr 3, 2012 6:41 am | |
| David Wolfskill | Apr 3, 2012 10:01 am | |
| jb | Apr 3, 2012 10:29 am | |
| David Wolfskill | Apr 4, 2012 6:38 am | |
| Gleb Kurtsou | Apr 5, 2012 12:42 am | .txt |
| David Wolfskill | Apr 5, 2012 4:19 am | .diffs |
| Luke Dean | Apr 28, 2012 11:03 am | |
| Chris Rees | Apr 28, 2012 11:12 am |
| Subject: | Re: Using TMPFS for /tmp and /var/run? | |
|---|---|---|
| From: | Adrian Chadd (adr...@freebsd.org) | |
| Date: | Mar 30, 2012 12:36:05 pm | |
| List: | org.freebsd.freebsd-current | |
Let me tell you a story.
Someone decided that ext4 could have a decent speed up if it implemented the posix standard for not flushing files on close(). After all, if you needed it to be guaranteed to be written to disk, you would call a flush routine first, before you called close().
So they did this.
Then people testing out ext4 discovered that upon crash, their kde/gnome profiles were corrupted.
Why? Because KDE/Gnome authors hadn't ever called flush before close(), and they weren't the only ones. They didn't read the standard, they only used the system and fixed bugs whenever their system behaved against their expectations. They didn't notice that the system was being different from the standard.
Guess what ext4 did? :)
Don't mis-estimate POLA.
Adrian
On 30 March 2012 10:56, Chris Rees <cre...@freebsd.org> wrote:
On 30 March 2012 17:31, C. P. Ghost <cpgh...@cordula.ws> wrote:
On Fri, Mar 30, 2012 at 3:18 PM, <sth...@nethelp.no> wrote:
However, if you always want to use tmpfs instead of stable storage,
please do not. Some people expect /tmp to be persistent. This is why /etc/defaults/rc.conf has clear_tmp_enable="NO". Changing this would break the POLA.
This is a mistake.
The default should be clear_tmp_enable="YES" if only to uncover those broken configurations that expect /tmp to be persistent.
If you want to break POLA and make a lot of people angry, sure. Otherwise no.
I couldn't agree more. Not clearing /tmp on reboot has been the norm for way too long and it is too late to change now. It's not just POLA, it also involves deleting data of unaware users, and that should be avoided.
Anyone willing to change policy w.r.t. /tmp can do so on their own machines. Nothing is preventing them from doing so. But by changing defaults, one should err on the side of caution and remain conservative, IMHO.
From man hier:
/tmp/ temporary files that are not guaranteed to persist across system reboots
This assumption that people often make 'People will be astonished by this'-- I would like to have someone speak up and actually say "Yes, I use *temporary* directories for long-term storage" rather than the assumption that they are around.
Software that assumes this should be fixed, and it won't be until the bug is exposed (I'll look at eaccelerator-- it probably should store its cache in /var/db).
Maintaining the status quo because of some hypothetical scenario isn't really productive.
Chris
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"