From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: getcwd() returning -ENOENT???
Date: Thu, 7 Dec 2000 15:03:10 +0000 (GMT) [thread overview]
Message-ID: <200012071503.eB7F3AS11880@flint.arm.linux.org.uk> (raw)
Hi,
Can someone explain why I'm seeing the following on test12-pre7:
bash# /bin/pwd
/bin/pwd: cannot get current directory: No such file or directory
bash# vdir /proc/self/.
...
lrwxrwxrwx 1 root root 0 Dec 7 14:52 cwd -> /net/raistlin/raistlin-v2.4/linux-ebsa285 (deleted)
...
lrwxrwxrwx 1 root root 0 Dec 7 14:52 root -> /
...
bash# vdir
... <complete listing of directory> ...
bash# cat /proc/mounts
/dev/root / ext2 rw,noatime 0 0
/proc /proc proc rw 0 0
/dev/hda3 /var ext2 rw,nodiratime 0 0
/dev/hda5 /usr ext2 rw,noatime 0 0
/dev/hda6 /home ext2 rw 0 0
none /dev/pts devpts rw 0 0
none /dev/shm shm rw 0 0
automount(pid482) /net/flint autofs rw 0 0
automount(pid499) /net/raistlin autofs rw 0 0
raistlin:/usr/src/v2.4 /net/raistlin/raistlin-v2.4 nfs rw,v2,rsize=4096,wsize=4096,hard,udp,lock,addr=raistlin 0 0
Rebooting the machine and trying again caused this weirdness to disappear.
First time around, the network wasn't initially available when autofs
started.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-07 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 15:03 Russell King [this message]
2000-12-07 15:31 ` getcwd() returning -ENOENT??? Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2004-02-07 21:38 -rb (Robert T. Brown)
2004-02-07 22:34 ` Marcus Alanen
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=200012071503.eB7F3AS11880@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@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 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.