From: Daiane Angolini <daiane.angolini@freescale.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: fatal error while init the repo on a nfs mounted drive
Date: Fri, 7 Jun 2013 09:29:45 -0300 [thread overview]
Message-ID: <51B1D239.5010105@freescale.com> (raw)
In-Reply-To: <CAP9ODKryjzaHVG5tNM54UMH85Q7DhYm1HSWYYdGm5R3SrL26ug@mail.gmail.com>
On 06/07/2013 09:11 AM, Otavio Salvador wrote:
>
>
>
> On Fri, Jun 7, 2013 at 6:25 AM, Thanassis Silis <djnass_18@hotmail.com
> <mailto:djnass_18@hotmail.com>> 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 -uhttps://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 never tried this setup; I use sstate in NFS in some customers but not
> full build system.
I have never tried it as well, but error -13 from NFS when mounting
rootfs is usually associated with missing 'sudo
/etc/init.d/nfs-serverXXXX restart'
Double check your /etc/export configuration
--
Daiane
next prev parent reply other threads:[~2013-06-07 12:31 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 [this message]
2013-06-07 12:48 ` Gary Thomas
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=51B1D239.5010105@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.