From: "J . A . Magallon" <jamagallon@able.es>
To: Andrea Pintori <1997s112@educ.disi.unige.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.2.17 bug found
Date: Thu, 9 Nov 2000 23:55:59 +0100 [thread overview]
Message-ID: <20001109235559.A747@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.3.91.1001109171915.5142B-100000@aries>
In-Reply-To: <Pine.LNX.3.91.1001109171915.5142B-100000@aries>; from 1997s112@educ.disi.unige.it on Thu, Nov 09, 2000 at 16:20:22 +0100
On Thu, 09 Nov 2000 16:20:22 Andrea Pintori wrote:
> I've a Debian dist, Kernel 2.2.17, no patches, all packages are stable.
>
> here what I found:
>
> [/tmp] mkdir old
> [/tmp] chdir old
> [/tmp/old] mv . ../new
> [/tmp/old] (should be /tmp/new !!)
No, bash cwd is still "/tmp/old".
> [/tmp/old] mkdir fff
> error: cannot write...
> [tmp/old] ls > fff
> error: cannot write...
> [/tmp/old] ls -la
> total 0 (?)
Right, "/tmp/old" does not exist, so nothing can be done with it.
> [/tmp/old] cd ..
> [/tmp] ls -la
> ***************** ./
> ***************** ../
> ***************** new/
>
> Does anybody knew this bug?
Is not a bug, I have also seen that int SGI IRIX. Try it in an NFS mounted
disk. I don't remember exactly, but even you can ls it. Things on file
system caches and so on...
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
-
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 prev parent reply other threads:[~2000-11-09 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 15:20 Kernel 2.2.17 bug found Andrea Pintori
2000-11-09 15:43 ` Tim Waugh
2000-11-09 15:47 ` Michael Rothwell
2000-11-09 15:49 ` Thomas Köhler
2000-11-09 16:00 ` Richard B. Johnson
2000-11-09 22:55 ` J . A . Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 16:03 Jesse Pollard
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=20001109235559.A747@werewolf.able.es \
--to=jamagallon@able.es \
--cc=1997s112@educ.disi.unige.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox