public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS mounting - SOLVED
Date: Thu, 05 Dec 2024 01:53:27 +0000	[thread overview]
Message-ID: <4942673.GXAFRqVoOG@cube> (raw)
In-Reply-To: <10573703.nUPlyArG6x@rogueboard>

On Monday 2 December 2024 17:56:38 GMT Michael wrote:
> On Tuesday 26 November 2024 16:13:01 GMT Peter Humphrey wrote:
> > Greetings,
> > 
> > [New readers start here...   :) ]
> > 
> > I've spent several days-worth of my time over the last few weeks in trying
> > to get my i5 box to export its portage tree and packages directory to a
> > chroot on my M9 machine. I read all the docs, I thought about the help
> > that
> > was offered here, I changed file systems and partitions around -
> > everything
> > I could think of.
> > 
> > The answer was simple, and I stumbled over it in a post on Stack Exchange:
> > the behaviour of NFS mount calls changed in NFS v4. I didn't need to
> > change
> > /etc/ exports on the i5, but the NFS-mount call on the M9 did need to
> > change.
> 
> Can you please share the link?

https://unix.stackexchange.com/questions/388410/nfs-mount-failed-reason-given-by-server-no-such-file-or-directory

It's comment 15.

I found this after I gave up running ~amd64 and reverted to a backup from 12 
days ago.

-- 
Regards,
Peter.





  parent reply	other threads:[~2024-12-05  1:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 16:13 [gentoo-user] NFS mounting - SOLVED Peter Humphrey
2024-12-02 17:56 ` Michael
2024-12-03 11:29   ` Peter Humphrey
2024-12-03 11:44     ` Michael
2024-12-03 11:48       ` Peter Humphrey
2024-12-05  1:53   ` Peter Humphrey [this message]
2024-12-03 13:08 ` Matt Jolly
2024-12-03 13:28   ` Peter Humphrey
2024-12-04  2:20     ` Peter Humphrey
2024-12-05  0:55       ` Gentoo wiki [was: Re: [gentoo-user] NFS mounting - SOLVED] Alexis
2024-12-05  1:21         ` Peter Humphrey

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=4942673.GXAFRqVoOG@cube \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox