From: Claudia Neumann <dr.claudia.neumann@gmx.de>
To: linux-msdos@vger.kernel.org
Subject: Re: are there any limitations to use drive c on nfs volumes?
Date: Sun, 26 Sep 2004 09:27:04 +0200 [thread overview]
Message-ID: <200409260927.04830.dr.claudia.neumann@gmx.de> (raw)
In-Reply-To: <200409251027.26691.Christian.Fischer@fischundfischer.com>
Hi Christian!
Am Samstag, 25. September 2004 10:27 schrieben Sie:
> Somethig goes completely wrong, i don't know how to trace it on the fly.
> Note: directories and files have identical user and group and right
> permissions. And not all directories of the same type of user:group (and
> the same permissions) are affected, only some one. I can't see any
> differences.
>
I hope you have read
http://resmedicinae.sourceforge.net/manuals/apw_linux/ch06s06.html. Sorry,
only in german.
First of all, did you export with the right permissions?
[exported directory say /opt] [hostname or IP-number of client](rw,sync)
Then: biggest problem:
user-name on client must be identical to user-name on server
user-id on client must be identical to user-id on server
group-name on client must be identical to group-name on server
group-id on client must be identical to group-id on server
Otherwise you can't do anything on server.
Beware: SUSe begins with user-ids 500, Debian begins with user-ids 1000.
Sometimes you will find program-gids intermangled with group-ids, so that you
get effective user:group 1020:1021. If server has 1020:1020, it won't work.
HTH
Claudia
next prev parent reply other threads:[~2004-09-26 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 9:57 are there any limitations to use drive c on nfs volumes? Christian Fischer
2004-09-24 11:20 ` Christian Fischer
2004-09-24 12:14 ` Claudia Neumann
2004-09-24 13:13 ` Christian Fischer
2004-09-25 8:27 ` Christian Fischer
2004-09-26 7:27 ` Claudia Neumann [this message]
2004-10-03 3:42 ` Ryan Underwood
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=200409260927.04830.dr.claudia.neumann@gmx.de \
--to=dr.claudia.neumann@gmx.de \
--cc=linux-msdos@vger.kernel.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