public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Concerns about WIPE_TMP change
Date: Fri, 18 Jan 2008 21:12:36 -0500	[thread overview]
Message-ID: <20080119021236.GO10389@aerie.halcy0n.com> (raw)
In-Reply-To: <479156FF.5030508@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 2153 bytes --]

Stefan de Konink <skinkie@xs4all.nl> said:
> How stupid anyone could be that stores anything in /tmp. I think it is a
> problem to change the default behavior of a system that in essence will
> result in data loss.

I think this might just be a communication problem.  You seem to be
contradicting yourself here by saying how someone could be stupid for
storing something, and then defending people that are doing something
you are admitting to be stupid and not logical.

> As pointed out by others you should not use /tmp to store data, my
> return question is then, why are the other ./tmp directories not wiped?
> If any ./tmp on a partition was 'kernel' governed I could agree that a
> semi-ramdisk would be gone upon reboot, or after an application was done
> running. But it is not.

Because according to the FHS (and common sense), files or directories in
/tmp should not be considered to be preserved.  /var/tmp on the other
hand is specifically for temporary files that should be preserved
between reboots.


> In any case my request would be to put a message with bells and beeps in
> the ebuild that cause the /etc/conf.d/bootmisc change announcing that by
> then the default option for /tmp is deletion on boot. To be consistent,
> also delete /var/tmp. If anyone thinks wiping /var/tmp is evil, please
> reconsider /tmp too. In my opinion WIPE_TMP should be in the same state
> as RC_PARALLEL_STARTUP. Unless anyone can make sure a user knows what he
> is doing, disable it.

Please refer to my explanation above as to why /var/tmp is different
from /tmp.

Should an elog statement been put into the ebuild...maybe.
I leave that up to the maintainer to decide what is important enough to
be logged, and they clearly thought this wasn't in this case.  But
bringing it up on this mailing list is atleast the correct place to get
a discussion going on what should be mentioned when we change default
configurations if that is your intention.

Thanks,

-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-19  2:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19  1:48 [gentoo-dev] Concerns about WIPE_TMP change Stefan de Konink
2008-01-19  2:12 ` Mark Loeser [this message]
2008-01-19 12:55   ` Richard Freeman
2008-01-19 22:18     ` [gentoo-dev] " Duncan
2008-01-19 23:17       ` [gentoo-dev] Re: Concerns about WIPE_TMP change [offtopic] Stefan de Konink
2008-01-20  0:33         ` Alec Warner
2008-01-20  0:37           ` Stefan de Konink
2008-01-20  1:08         ` Duncan
2008-01-20 13:43         ` Richard Freeman
2008-01-22  1:34           ` Caleb Cushing
2008-01-22  2:54             ` Philip Webb
2008-01-24  7:06             ` Chris Gianelloni
2008-01-19 23:29       ` [gentoo-dev] Re: Concerns about WIPE_TMP change Olivier Galibert
2008-01-20  0:19         ` Ryan Hill
2008-01-20  1:23         ` Mike Frysinger
2008-01-20 13:47       ` Richard Freeman
2008-01-20 13:56         ` Fabian Groffen
2008-01-21  2:38         ` Donnie Berkholz
2008-01-21  5:05           ` Mike Frysinger
2008-01-21 21:42             ` Duncan
2008-01-19 11:05 ` [gentoo-dev] " Roy Marples
2008-01-19 20:54   ` Mike Frysinger
2008-01-19 21:03     ` Stefan de Konink
2008-01-19 21:26       ` Mike Frysinger
2008-01-19 21:33         ` Stefan de Konink

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=20080119021236.GO10389@aerie.halcy0n.com \
    --to=halcy0n@gentoo.org \
    --cc=gentoo-dev@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