From: steve <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] /tmp dissappearance
Date: Sun, 20 May 2012 21:34:06 +0100 [thread overview]
Message-ID: <C3F9021A-83C4-431F-AC83-5458C64542BA@quintile.net> (raw)
In-Reply-To: <37EF8425-F607-4662-B628-A46C0D5AF2E8@9srv.net>
a simpler way might be to:
mount -c /srv/fossil /n/fossil
mkdir /n/fossil/tmp
always assuming you are using fossil and you have write permission in /
which probably means you must be hostowner.
-Steve
On 20 May 2012, at 07:04 PM, Anthony Sorace <a@9srv.net> wrote:
> On May 20, 2012, at 13:29 , David du Colombier wrote:
>
>> echo fsys main create /tmp sys sys d775 >>/srv/fscons
>
> turn that "/tmp" into "/active/tmp" i think, no?
>
> also, for the original question: as a quick hack to get around
> this, i believe you could run mntgen on / so that /tmp magically
> shows up when you bind to it.
>
> the "mounted directory forbids creation" sounds suspect, though.
> trying to bind onto a non-existent target should yield a simple
> "file does not exist".
>
> and, of course, that doesn't address why it went away.
> anthony
>
next prev parent reply other threads:[~2012-05-20 20:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM8pOuNE-CK41emPuCngMPRqye194i8C-tbDZRK0vSXZHfDe7Q@mail.gmail.c>
2012-05-20 16:59 ` erik quanstrom
2012-05-20 17:10 ` Burton Samograd
2012-05-20 17:15 ` Burton Samograd
2012-05-20 17:21 ` andrew zerger
2012-05-20 17:31 ` Burton Samograd
2012-05-20 17:29 ` David du Colombier
2012-05-20 18:04 ` Anthony Sorace
2012-05-20 18:27 ` David du Colombier
2012-05-20 20:34 ` steve [this message]
2012-05-21 0:46 ` erik quanstrom
2012-05-20 16:56 Burton Samograd
2012-05-20 20:36 ` Rudolf Sykora
2012-05-20 20:49 ` andrew zerger
2012-05-20 20:59 ` Charles Forsyth
2012-05-20 21:16 ` Burton Samograd
2012-05-20 21:21 ` Burton Samograd
2012-05-20 21:33 ` Ethan Grammatikidis
2012-05-20 21:42 ` cinap_lenrek
2012-05-21 5:05 ` kokamoto
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=C3F9021A-83C4-431F-AC83-5458C64542BA@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).