From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: fatal error while init the repo on a nfs mounted drive
Date: Fri, 07 Jun 2013 06:48:59 -0600 [thread overview]
Message-ID: <51B1D6BB.7060707@mlbassoc.com> (raw)
In-Reply-To: <DUB116-W63A0CE6D93EFFE2757EB4C98990@phx.gbl>
On 2013-06-07 03:25, Thanassis Silis wrote:
> i am trying to initialize a repo (for yocto development - but it seems to be using the same infrastructure as android).
> since I lack space on the OS drive, I nfs mounted another disk (filesystem is ext4 but that probably is irrelevant on the mount-client side).
> I try to initialize the repo with the command
>
> |./repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan
> |
>
> and get the error
>
> |fatal: unable to start /mnt/lvm/public/.repo/repo/main.py
> fatal: [Errno 13] Permission denied
> |
>
> Permissions are fine on the disk. manually I can do file operations without a problem.
> Is it impossible to have the repo on an nfs drive (even at the penalty of slower processing)?
> Thank you for your help
I just tried this and it worked fine.
When you say permissions are fine, did you check it from the
NFS client side? The error you are getting says that they are
not. Also, are you running selinux? If so, make sure that's
set up properly as well.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-06-07 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 9:25 fatal error while init the repo on a nfs mounted drive Thanassis Silis
2013-06-07 12:11 ` Otavio Salvador
2013-06-07 12:29 ` Daiane Angolini
2013-06-07 12:48 ` Gary Thomas [this message]
2013-06-07 13:37 ` Thanassis Silis
2013-06-07 15:12 ` Thanassis Silis
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=51B1D6BB.7060707@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.