mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: trond.myklebust@fys.uio.no
Cc: linux-kernel@vger.kernel.org
Subject: [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch
Date: Fri, 11 Jan 2002 14:15:11 +0100	[thread overview]
Message-ID: <20020111131528.44F8613E6@shrek.lisa.de> (raw)

Hi Trond et al.,

after applying $subject and resolving the rej with 2.4.18-pre1, 
I found the following strangeness in my SuSE 7.3 based NFS diskless setup:

Trying to start openuniverse for the first time (ever), it complaint about
a missing config file. SuSE installed it's data at /usr/share/openuniverse 
with the config file conf/ou.conf symlinked to ../../../../etc/ou.conf (=> 
/etc/ou.conf), which was missing within my diskless setup.

The problem is, ls on the client side complains about an I/O error, when 
listing the conf/ dir.

After removing this symlink (within the server), ls is OK within
the client. Trying to copy servers /etc/ou.conf file to
/usr/share/openuniverse within the client, cp complains about to many levels 
of symlinks?!? (/usr is shared)

May be I missed/confused some patches. I could send you a plain
copy of the interresting modules, if you like. 

Somehow, the dir entry on the client survived the rm from the server.

Compiling/KDE 2.2.2 Desktop is working fine so far.

Any ideas?

Cheers,
Hans-Peter

             reply	other threads:[~2002-01-11 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 13:15 Hans-Peter Jansen [this message]
2002-01-11 15:07 ` Trond Myklebust
2002-01-11 19:17   ` Hans-Peter Jansen
2002-01-12  2:24     ` Trond Myklebust
2002-01-12 17:01       ` [NFS] some strangeness (at least) with linux-2.4.18-NFS_ALL patch Hans-Peter Jansen
2002-01-12 18:47       ` Trond Myklebust
2002-01-12 22:40         ` Hans-Peter Jansen
2002-01-13 12:37         ` Trond Myklebust
2002-01-12  2:04   ` [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch Trond Myklebust

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=20020111131528.44F8613E6@shrek.lisa.de \
    --to=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®