mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Alex Buell <alex.buell@tahallah.demon.co.uk>
Cc: Mailing List - Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Duplicate '..' in /lib
Date: Mon, 16 Jul 2001 01:07:12 -0400	[thread overview]
Message-ID: <20010716010712.B6609@visi.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0107160548400.3655-100000@tahallah.demon.co.uk>
In-Reply-To: <Pine.LNX.4.33.0107160548400.3655-100000@tahallah.demon.co.uk>; from alex.buell@tahallah.demon.co.uk on Mon, Jul 16, 2001 at 05:50:12AM +0100

On Mon, Jul 16, 2001 at 05:50:12AM +0100, Alex Buell wrote:
> I just found a pair of '..' directories in the /lib directory. e2fsck 1.19
> didn't even pick up on this!
> 
> /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.

ls -aQ


I bet that file has atleasy one space after the "..". The -Q makes ls
enclose the filename in double-quotes.

I'de be worried if this were actually the case, and check the contents
of that file. It's a common way for someone to "hide" files when they
crack a system.


Ben

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'

  reply	other threads:[~2001-07-16  5:07 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 [this message]
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
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=20010716010712.B6609@visi.net \
    --to=bcollins@debian.org \
    --cc=alex.buell@tahallah.demon.co.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 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®