All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, Olaf Kirch <okir@suse.de>
Subject: Re: nfsprog support
Date: Mon, 3 May 2004 01:27:15 +0200	[thread overview]
Message-ID: <200405030127.24709.bernd-schubert@web.de> (raw)
In-Reply-To: <1082065434.7141.48.camel@lade.trondhjem.org>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Hi Trond,

sorry for the late response, but as usual I was busy with my main work.

>
> What you are describing sounds like a bug in "mount". In the case where
> the user specifies both "port" and "nfsvers", there is no need
> whatsoever to consult the portmapper.
>
> I just do not see this as a kernel bug, or as any form of justification
> for adding support for the nfsprog hack.
>

It seems I was chasing a phantom *hrmmph*. 
After you told me, it might be a bug in "mount", I immedeately checked the 
util-linux mount source and didn't find anything wrong. 
Today I tried again finding the source of the problem, but now I don't see a 
problem at all. Mounting on different ports just works fine, even with the 
same nfsversion.
I really have no idea why it didn't work all the time, but now suddenly works.

Sorry for wasting your time,
	Bernd


[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-05-02 23:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 15:50 nfsprog support Bernd Schubert
2004-04-15 17:51 ` Olaf Kirch
2004-04-15 18:39   ` Bernd Schubert
2004-04-15 19:39     ` Trond Myklebust
2004-04-15 21:31       ` Bernd Schubert
2004-04-15 21:43         ` Trond Myklebust
2004-05-02 23:27           ` Bernd Schubert [this message]

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=200405030127.24709.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    --cc=trond.myklebust@fys.uio.no \
    /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.