From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] /tmp in "ram disk"
Date: Thu, 31 May 2007 12:07:46 -0700 [thread overview]
Message-ID: <13426df10705311207u68ec4c38g9cf2a17eeda3e23@mail.gmail.com> (raw)
In-Reply-To: <88a7b6a7cf96a89ffe11600ae7ca0d62@hamnavoe.com>
On 5/31/07, Richard Miller <9fans@hamnavoe.com> wrote:
> > i.e. where in the
> > pccpu
> > or whatever would I put an entry such that I get a
> > /tmp
> > directory when it comes up?
>
> /sys/src/9/port/devroot.c:94,107
>
>
I sleazed out and put an addrootdir("tmp") in devroot.c. It was the
easiest way out,
and that seems to be how it's done.
What I've got is a very limited node, security not an issue. I need a
ramfs, but I want a /tmp there for it. Simple stuff.
thanks
ron
next prev parent reply other threads:[~2007-05-31 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 18:54 ron minnich
2007-05-31 18:59 ` erik quanstrom
2007-05-31 19:02 ` Richard Miller
2007-05-31 19:07 ` ron minnich [this message]
2007-05-31 19:10 ` andrey mirtchovski
2007-05-31 19:14 ` ron minnich
2007-05-31 19:58 ` Richard Miller
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=13426df10705311207u68ec4c38g9cf2a17eeda3e23@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).