Asterix appended to the file name??

[Big Dan]

Hi Guys,

I just started a VPS account, what I did was ssh into my old account and tar each website separately; then I ssh'ed onto my new server wget-ed and untared.

On directory listing I'm getting an asterix appended to the end of almost all my files, I'm assuming it has something do with permissions but I've never seen this before even on my (linux) desktop. If it helps, I untarred as root.

One other question while I'm here why when using rm -r (recursive) to delete files am I having to use the -f (force) flag? If I don't I get asked to delete every file individually. I've never had to use the force flag when using debian. Is this just the way Red Hat based distros work?

Screenshot (http://img291.imageshack.us/img291/9091/screenshotmissioncontroldancafedannyou0.png)

Thanks in advance,
Dan

[Greg]

Well, one thing for certain, being root and working, in most cases, will affect the ability of the folder owner and public uses of files via permissions. I'm not an expert, but I think TAR will pass permissions propery if the files were archived with the proper permissions. So, I guess that is the question, were the proper permissions archived and passed or inherited.

Looking at your SS and testing in my account, The * seems to be only on executable files. I did this as root and got that result. As a user, I seem to get the same result.

I did a "man rm".


-f, --force
ignore nonexistent files, never prompt

-r, -R, --recursive
remove the contents of directories recursively

[Big Dan]

Executable seems to be the answer, I finally got Ubuntu to let me login as root and I see the same thing on executable files. It seems most things are done using su on debian based distro's. Using ls on my home box was done as a normal user, not showing the asterix because I wasn't root.

Forgot about the man command.. always ask the man. ;)

Thanks

[Greg]

Glad to here that info was helpful.

Have you checked out the servint vps forum? Good info there.

[Big Dan]

Yup I found my way over there.. That's how I figured out to get around the mysql max_packet_limit or something along those lines. :)