-bash: cddownloadsfile: command not found
that is a little odd. i have been a novice unix/linux user for a long time, and i cannot recall a time when the "file" command was not installed in any unix/Linux type OS as a basic shell command, as a part of bash or any other modern shell. i would guess it should already be installed in your Linux OS, though perhaps i am mistaken on this. i use the command from time to time to double-check that i am not about to attempt to edit a binary file by mistake.
for example, on a current linux system, i can type:
which file
and the answer comes back as /usr/bin/file, meaning that the "file" command executable file is installed in /usr/bin, and of course /usr/bin is in my path environment variable. i can check the latter by typing:
echo $PATH
which shows me all the directories listed in my bash environment variable PATH, including /usr/bin. Perhaps your PATH variable does not include the relevant absolute path to the folder in which the file "file" exists?
i can type:
file /usr/bin/file
and the file command returns a description saying that the file "/usr/bin/file" is an ELF 64-bit executable file etc.
i can type:
file someprog.f
and the answer from the file command says that someprog.f is a fortran ASCII text file.
which variant of Linux are you using, and does your $PATH variable include all of the usual /bin, /usr/bin etc.? if $PATH does not, then you would have to find where the "file" command executable is installed on your Linux variant, and either add that location to your $PATH by modifying your .bashrc file in your home directory, or else type
/usr/bin/file somemusic.flac or
/usr/bin/file someothermusic.mp3 each time you wanted to use it (assuming "file" is located in /usr/bin in this example).
If for example, the "file" command file is located in /usr/bin, and /usr/bin is not yet in your PATH variable, then use a text editor like vi to add the following line (without extra blank spaces) to your ".bashrc" file in your home directory:
export PATH=$PATH:/usr/bin