From: David Luyer <david_luyer@pacific.net.au>
To: Alexander Viro <viro@math.psu.edu>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>, Adam <adam@eax.com>,
Alex Buell <alex.buell@tahallah.demon.co.uk>,
Mailing List - Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Duplicate '..' in /lib
Date: Mon, 16 Jul 2001 15:55:22 +1000 [thread overview]
Message-ID: <200107160555.f6G5tMtK019295@typhaon.pacific.net.au> (raw)
In-Reply-To: Message from Alexander Viro <viro@math.psu.edu> of "Mon, 16 Jul 2001 01:38:40 EDT." <Pine.GSO.4.21.0107160128320.26491-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0107160128320.26491-100000@weyl.math.psu.edu>
> On Mon, 16 Jul 2001, Albert D. Cahalan wrote:
>
> > Adam writes:
> >
> > >> /lib
> > >> 4 drwxr-xr-x 19 root root 4096 Jun 9 16:06 ..
> > >> 4 -rw-rw-r-- 1 root root 27 Jun 9 15:55 ..
> > >>
> > >> How can I get rid of this? I'm on kernel 2.2.19, running on sparc-linux.
> > >
> > > first it is not a pair directories, but a directory and a file.
> > >
> > > second, are you sure both of the mare just ".." for example
> >
> > I don't think so! Look at the "4" on the left. If that is the
> > inode number from "ls -lia /lib", his disk is seriously messed up.
> > The inode number for "/lib/.." should be 2, and an inode may not
> > be shared between a file and a directory.
>
> Erm... It _can't_ be an inode number. Something is very fishy there.
I'd say that's a 'ls -las'; both the small file and the directory above take
up a 4k block.
The second is, say, ".. " and the first is just "..".
Nothing interesting at all.
David.
--
David Luyer Phone: +61 3 9674 7525
Engineering Projects Manager P A C I F I C Fax: +61 3 9699 8693
Pacific Internet (Australia) I N T E R N E T Mobile: +61 4 1111 2983
http://www.pacific.net.au/ NASDAQ: PCNTF
next prev parent reply other threads:[~2001-07-16 5:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 4:50 Alex Buell
2001-07-16 5:07 ` Ben Collins
2001-07-16 5:08 ` Ignacio Vazquez-Abrams
2001-07-16 5:11 ` Adam
2001-07-16 5:16 ` Albert D. Cahalan
2001-07-16 5:38 ` Alexander Viro
2001-07-16 5:55 ` David Luyer [this message]
2001-07-16 6:30 ` Alex Buell
2001-07-16 8:07 ` Wichert Akkerman
2001-07-16 8:16 ` J Troy Piper
2001-07-17 2:22 ` Michael H. Warfield
2001-07-17 10:26 ` Alex Buell
2001-07-17 12:33 ` Michael H. Warfield
2001-07-17 12:44 ` Alex Buell
2001-07-17 12:58 ` Michael H. Warfield
2001-07-17 13:00 ` Large memory oops/odd behaviour Linux 2.2, seeking recommendations Mr. James W. Laferriere
2001-07-16 5:32 ` Duplicate '..' in /lib Alex Buell
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=200107160555.f6G5tMtK019295@typhaon.pacific.net.au \
--to=david_luyer@pacific.net.au \
--cc=acahalan@cs.uml.edu \
--cc=adam@eax.com \
--cc=alex.buell@tahallah.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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®