From: Adriano Verardo <a.verardo@tecmav.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Questions about FreeBSD p9p
Date: Wed, 7 Feb 2007 19:31:49 +0100 [thread overview]
Message-ID: <45CA1B15.4000505@tecmav.com> (raw)
In-Reply-To: <ee9e417a0702070935m445c7a95j2e45ae6d3492fc30@mail.gmail.com>
Russ Cox wrote:
>> Q.1
>> duke% export NAMESPACE=/home/adriano/NS
>> duke% factotum
>> duke% 9fs milagro
>> duke% 9 mount NS/milagro mil
>> factotoum ok, with/without secstore.
>> mount ok.
>
>
> When you run 9fs, you should be prompted for
> a user name and password to use. Are you being prompted?
>
Yes, only the first time, for p9sk1. As expected.
Setting env $secstore to point milagro, duke's factotum asks for the
secstore password. Again, as expected.
>> duke% echo ciaociao > mil/usr/adriano/ciao
>> bash: mil/usr/adriano/ciao: Permissione denied
>
>
> try:
>
> echo hi | 9p write milagro/usr/adriano/ciao
>
Yes, the first test I done. 9p works ok in all situations.
My problem is that I would like to exploit the backup capability
of milagro for developers working on BSD boxes.
No problem, they will create files using 9p.
> that will cut FUSE out of the loop, just to make things
> a little simpler.
>
>> Q.2
>>
>> duke% 9p -a milagro -A main/archive <cmd>
>>
>> Ok for all <cmd>s, I see, read etc milagro's archive.
>>
>> How can I mount main/{archive,snapshot} on a duke's directory ?
>> In P9P doc I've not found how to issue a command like
>> "mount /srv/fossil /n/arc main/archive".
>> My mistake or feature intentionally not implemented (or not implemented
>> yet)?
>
>
> Just not implemented. It should be, it isn't.
> You can use this as a workaround:
>
> srv -a -A main/archive milagro milagro-dump
> 9 mount `namespace`/milagro-dump /dump
>
OK ! I can ls, diff, and view archived files.
The hist(1) cmd looks for /n/dump/duke root. Correct ?
Mounting milagro-dump onto duke's /dump/duke instead of /dump,
hist(1) displays only the first line and not the whole story
as Plan9's history(1) do on the same file. Why ?
>> Q.3
>>
>> All tests done using the raw char console (no X)
>> produce the expected network traffic.
>>
>> Under X + KDE there is a continuous, unsolicited, net activity
>> which stops dismounting the Plan9 file server (milagro)
>> or stopping X without dimounting milagro.
>> This is independent on the environment from which milagro has been
>> mounted (char console or X-KDE).
>> I tried all command sequences to have both milagro mounted and KDE
>> running, but the final behaviour is always the same.
>>
>> Where/what am I mistaking ?
>
>
> There is probably some KDE daemon running in the background
> that is excited about a new drive being mounted and is scanning it.
> ("Modern" X window managers like KDE and GNOME just do this
> sort of thing, ostensibly to make your life better, though that's
> rarely the effect.) You might try running
>
> lsof | grep mil/
>
> to find out which programs are holding open references to milagro.
> You might also be able use "umount -f" to force an unmount.
>
> Russ
>
>
Ah, I'll try to find the (probably useless) deamon.
From "ps ax" I see all 9pserve and 9pfuse tasks eating a lot of cpu.
Thank you very much, Russ.
Adriano
next prev parent reply other threads:[~2007-02-07 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:14 Adriano Verardo
2007-02-07 17:35 ` Russ Cox
2007-02-07 18:31 ` Adriano Verardo [this message]
2007-02-07 18:52 ` Russ Cox
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=45CA1B15.4000505@tecmav.com \
--to=a.verardo@tecmav.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).