From: "Kevin N. Carpenter" <kevinc@seaplace.org>
To: Paul de Vrieze <gentoo-user@devrieze.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /var/tmp world rwx?
Date: Fri, 03 Jan 2003 17:04:56 -0600 [thread overview]
Message-ID: <3E161718.3060806@seaplace.org> (raw)
In-Reply-To: <200301032350.35573.gentoo-user@devrieze.net>
Thats cool. Easy enough to mount both /tmp and /var/tmp as tmpfs with
my noexec,nosuid,nodev options.
Mounting /var/tmp/portage with just "nosuid, nodev" requires the mount
point to exist, which it won't as a freshly mounted tmpfs filesystem.
Still, easy enough to fix in local.start.
Thanks!
Kevin C.
Paul de Vrieze wrote:
>
>It's a standard temporary directory so yes. It should be open for the public.
>This doesn't hold for /var/tmp/portage though. You also might want to use an
>extra tmpfs or a bind mount or a change in make.conf as emerge has some
>issues with symlinked paths.
>
>Paul
>
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-03 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 22:42 [gentoo-dev] /var/tmp world rwx? Kevin N. Carpenter
2003-01-03 22:50 ` Paul de Vrieze
2003-01-03 23:04 ` Kevin N. Carpenter [this message]
2003-01-04 9:23 ` Sven Vermeulen
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=3E161718.3060806@seaplace.org \
--to=kevinc@seaplace.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@devrieze.net \
/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