From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Octopus installation on Plan9
Date: Tue, 8 Jul 2008 17:41:31 +0200 [thread overview]
Message-ID: <8ccc8ba40807080841t2a476665of2a80ba966b4c23@mail.gmail.com> (raw)
In-Reply-To: <20080708153509.GH29253@hermes.my.domain>
probably just /dis/* and /dis/*/*
It would be safe to add usr/octopus/lib/*.{sh, rc}
I'll try to reproduce what's happening to you here and fix
the install.
On Tue, Jul 8, 2008 at 5:35 PM, Christian Kellermann
<Christian.Kellermann@nefkom.net> wrote:
> * Francisco J Ballesteros <nemo@lsub.org> [080708 17:30]:
>> Has the setup.sh execute permissions?
>> Is /usr/octopus unpacked correctly under inferno, so that
>> it might be something like /usr/inferno/usr/octopus on the
>> Plan 9 system?
>>
>> I think all the problem is that the files are being extracted
>> without execute permissions. This did not happen when we
>> used tar instead of zip. Anyway, you can either give the
>> execute permissions to /dis/... yourself or wait a little until
>> I fix the install script to make sure this does not happen again.
>
> Thanks for your help. Just to make sure we are both talking about
> the same thing:
>
> I create a /usr/octopus on plan9, unzip the o.zip there which already
> contains inferno and a octopus inferno user in ./usr/octopus. I
> need to chmod +x the files in /dis/* also somewhere else?
>
> Kind regards,
>
> Christian
>
> --
> You may use my gpg key for replies:
> pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
>
next prev parent reply other threads:[~2008-07-08 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 11:22 Christian Kellermann
2008-07-08 15:26 ` Francisco J Ballesteros
2008-07-08 15:35 ` Christian Kellermann
2008-07-08 15:41 ` Francisco J Ballesteros [this message]
2008-07-08 18:15 ` Tony Lainson
2008-07-08 22:46 ` Francisco J Ballesteros
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=8ccc8ba40807080841t2a476665of2a80ba966b4c23@mail.gmail.com \
--to=nemo@lsub.org \
--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).