public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan de Konink <skinkie@xs4all.nl>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Concerns about WIPE_TMP change
Date: Sat, 19 Jan 2008 02:48:47 +0100	[thread overview]
Message-ID: <479156FF.5030508@xs4all.nl> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,


I joined this mailinglist because of my concern pointed in:

http://bugs.gentoo.org/show_bug.cgi?id=206604


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.

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.


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.



Yours Sincerely,

Stefan de Konink

ps. No I did not have data loss, like any good admin I read before I
apply. And yes I prefer to store anything that will not cause harm, such
as extracted sources for gdb use in /tmp.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHkVb/YH1+F2Rqwn0RCsK4AJ4wEQPC5MrCrZdIEzKIjJkh+pKNoQCfX1BG
alIrUmXiM2kulk3p635PiZk=
=57tK
-----END PGP SIGNATURE-----
-- 
gentoo-dev@lists.gentoo.org mailing list



             reply	other threads:[~2008-01-19  1:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19  1:48 Stefan de Konink [this message]
2008-01-19  2:12 ` [gentoo-dev] Concerns about WIPE_TMP change Mark Loeser
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=479156FF.5030508@xs4all.nl \
    --to=skinkie@xs4all.nl \
    --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