From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: 1997s112@educ.disi.unige.it, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.2.17 bug found
Date: Thu, 9 Nov 2000 10:03:21 -0600 (CST) [thread overview]
Message-ID: <200011091603.KAA347653@tomcat.admin.navo.hpc.mil> (raw)
On Thu, Nov 09, 2000 at 05:20:22PM +0200, 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 !!)
> [/tmp/old] mkdir fff
> error: cannot write...
> [tmp/old] ls > fff
> error: cannot write...
> [/tmp/old] ls -la
> total 0 (?)
> [/tmp/old] cd ..
> [/tmp] ls -la
> ***************** ./
> ***************** ../
> ***************** new/
>
> Does anybody knew this bug?
Not a bug... possibly a typo though. The "[/tmp/old] mv . ../new" line
destroys the definition of "current directory". The "mkdir fff" can't work
since the current directory is no longer there, and is indicated by
the lines:
[/tmp/old] ls -la
total 0 (?)
There is nothing to take a directory of.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
-
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-11-09 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 16:03 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=200011091603.KAA347653@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--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