Hi,

I have an * asterisk (spelling? <---) after some file names. Can you tell me what this means?

Example:
04-AudioTrack\ 04.mp3*

Thanks,

"ls -F" puts indicator characters at the end of filenames it lists for certain types of files:
* = regular file has executable permission
/ = directory
@ = symlink
| = pipe
= = socket
> = doors

If you're using ls with the -F option it means that the file in question is executable.

edit: D'oh beaten to it!

Okay,

In response to that. I was trying to make this directory of songs play on a shoutcast server. I have never had these crazy extensions on here before (of what i remember), and usually , I don't recall have mp3's executable.

I was having problems with shoutcast not able to open the file. I was assuming that perhaps this was the reason why.

Any way for me to undo this so they are just files sitting in a directory like they should be, so I can test to see if this is the problem?

And furthermore, I'm just doing a regular ls. They are all showing up green too, which I know means executable on this system.

Thanks,

Most people have their ls alias'ed to "ls -F --color=auto" or some crap like that, so it shows up in color with other stuff. Check your aliases.

Use "ls -l" to look at the permissions of stuff.

Thanks guys,

I figured out my problem after all. It turns out the playlist file can't have spaces in it. So it sucks to be me because almost all of my songs have spaces in it..... as when I ripped them I put regular windows names in there.

I understand how things have color, and the various other commands that go with ls, but ls -F is a new one.

I just never have seen this asterisk thing after file names, let alone making a mp3 executable like a program or such. I usually only see files executable when they are scripts or binaries.

Thanks for the advice though, I'll check on that and let you guys know what i figure out.

If you want to get rid of the spaces, you could try something like:
This will replace the spaces with underscores.

sweet. I will totaly be trying that out.

No problem. Also, if you want to try to get rid of the execute permissions, you can do:

This doesn't work here, but the following does:

umm how about

I wasn't even familiar with the rename utility. The manpage for mine indicates that it should take a perl regexp and a number of file names for that purpose.