Yes thats a valid file but its been my experience that ... files markers that gits who have used root kits (or some exploit you haven't patched) have been in your system.

So I'd avoid using it. The reason why that its a valid file is to do with the way inodes work on Unix. The '.' 'points' to the local directory and '..' to the parent directory. This works in a chain right up to '/'. Consider that as everything in Unix is essentially a file and that only those two files are considered special then what you have created is a dot file called '..'.

Of course because its a dot file you have to use 'ls -la' to normally see them. Hence why they are left about in user directories. Also a reason to avoid them.

Now if you didn't create that file - I'd be worried :P.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.