From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Wed, 6 Dec 2017 16:12:25 +0000 [thread overview]
Message-ID: <5A2816E9.1010102@youngman.org.uk> (raw)
In-Reply-To: <a98b6467-c692-86ab-4759-d40cb04b21b4@gmail.com>
On 06/12/17 15:34, Alan McKinnon wrote:
> Those guidelines you mention about what /tmp and /var/tmp are "for" are
> probably from the FHS. On the whole, I tend to agree they are good ideas
> but the proper wording is more like this (from memory, being far too
> lazy after a day's work to actually look something up):
>
> - contents of /tmp are not expected to survive the invocation of the
> program that created them
http://www.pathname.com/fhs/pub/fhs-2.3.html#TMPTEMPORARYFILES
> - contents of /var/tmp are not expected to survive a reboot
>
http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE
> Which is different from what you said.
Except that /var/tmp is exactly the opposite of what you said :-)
Not surprisingly, if you follow
> that through, you can run rm -rf /tmp/* in a cron every minute and
> nothing should ever break. Or, every file in /tmp can be anonymous (just
> an inode without a dentry giving it a name)
Cheers,
Wol
next prev parent reply other threads:[~2017-12-06 16:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 6:52 [gentoo-user] is multi-core really worth it? Raffaele Belardi
2017-11-22 7:21 ` R0b0t1
2017-11-22 7:26 ` Jeremi Piotrowski
2017-11-22 8:23 ` Neil Bothwick
2017-11-22 8:34 ` David Haller
2017-11-22 10:07 ` [gentoo-user] " Martin Vaeth
2017-11-22 11:26 ` David Haller
2017-11-23 22:47 ` Martin Vaeth
2017-11-22 13:12 ` [gentoo-user] " Raffaele Belardi
2017-11-22 13:23 ` J. Roeleveld
2017-11-22 14:11 ` Tsukasa Mcp_Reznor
2017-11-22 14:34 ` Wols Lists
2017-11-22 16:27 ` J. Roeleveld
2017-12-05 4:11 ` Taiidan
2017-12-05 4:17 ` R0b0t1
2017-12-05 10:09 ` Peter Humphrey
2017-12-05 10:46 ` Wols Lists
2017-12-05 11:13 ` Raffaele Belardi
2017-12-05 11:39 ` Mick
2017-12-05 13:07 ` Peter Humphrey
2017-12-05 13:57 ` Wols Lists
2017-12-05 14:13 ` Peter Humphrey
2017-12-05 21:56 ` Neil Bothwick
2017-12-06 13:29 ` Wols Lists
2017-12-06 15:34 ` Alan McKinnon
2017-12-06 16:07 ` Wols Lists
2017-12-06 23:51 ` [gentoo-user] " Ian Zimmerman
2017-12-06 16:12 ` Wols Lists [this message]
2017-12-06 17:24 ` [gentoo-user] " Kai Peter
2017-11-22 7:48 ` David Haller
2017-11-22 8:32 ` J. Roeleveld
2017-11-22 8:57 ` David Haller
2017-11-22 12:16 ` Peter Humphrey
2017-11-22 16:36 ` Neil Bothwick
2017-11-28 10:07 ` [gentoo-user] " Raffaele Belardi
2017-12-01 10:39 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A2816E9.1010102@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox