From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Anthony Brock <brocka@sterlingcgi.com>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: SMP skas requirements
Date: Thu, 30 Mar 2006 23:29:59 +0200 [thread overview]
Message-ID: <200603302330.00256.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200603302304.00293.blaisorblade@yahoo.it>
On Thursday 30 March 2006 23:03, Blaisorblade wrote:
> On Wednesday 29 March 2006 22:38, Anthony Brock wrote:
> > Quoting Jeff Dike <jdike@addtoit.com>:
> > > On Wed, Mar 29, 2006 at 12:40:00AM +0200, Blaisorblade wrote:
> > >> Finally, I'd like to get devshm merged if there aren't problems with
> > >> the code.
(Jeff wrote):
> > That one needs to check if /dev/shm is present, and fall back to /tmp
> > if not.
I'd add that it needs to retry even if the PROT_EXEC test fails:
*) if TMP, TEMP or TMPDIR are set, use that and fail if the check fails,
abort, because the user wanted to use that but forgot to change permissions.
*) if instead we pick /dev/shm but it has not PROT_EXEC, we should switch
to /tmp and fail only then.
> > Are you proposing that virtual servers automatically using /dev/shm if
> > available and only falling back to the $TMP variable and /tmp directory
> > if not? Or would this keep the use of $TMP if present and fall back to
> > /dev/shm followed by /tmp?
> By looking at:
> http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.16/patches/devs
>hm
Sorry, forgot to finish. That patch keeps checking TMP,TMPDIR and TEMP (don't
remember the order), but if none is set, it switches the default from /tmp
to /dev/shm.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-30 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 4:36 [uml-devel] Re: SMP skas requirements Jeff Dike
2006-03-29 20:38 ` Anthony Brock
2006-03-30 21:03 ` Blaisorblade
2006-03-30 21:29 ` Blaisorblade [this message]
2006-03-31 6:54 ` Anthony Brock
[not found] <20060320210659.GB6474@ccure.user-mode-linux.org>
[not found] ` <200603280032.31190.blaisorblade@yahoo.it>
2006-03-28 19:45 ` Jeff Dike
[not found] ` <200603290040.01268.blaisorblade@yahoo.it>
[not found] ` <20060329004144.GB24121@ccure.user-mode-linux.org>
2006-03-29 2:47 ` Blaisorblade
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=200603302330.00256.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=brocka@sterlingcgi.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.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