XMMS in Tiny Core 3.5 - Cannot save playlist (permission denied)

[KingBongo]

Hi there (again)! I have an old Pentium 1 with Tiny Core 3.5 installed. When trying to save a playlist in XMMS I get the error message "permission denied". I am guessing that there is a problem with missing root permissions. How to resolve this issue?   

[Jason W]

Where are you trying to save it to?  You need read/write permissions in the directory you are trying to save it in.

[KingBongo]

Jason W:
Hmmm. I didn't think about that. I'll check and then get back to you. By the way, do I have to change permissions from the Terminal, or is it possible to do it from the GUI?

[Jason W]

I would save to /home/tc, or whatever user name you are using.

Otherwise, if it is on usb or HD storage, change the ownership if you want to save there.

Example:
sudo chown -R /mnt/sda1/music

File managers each have their own gui way of changing permissions on files and directories, but that is the command line way.

[KingBongo]

Jason W:
Thank you! It works great, but you already knew that, didn't you

By the way, you forgot to add USER to the "chown" command. I better show people reading this what it should look like. In my case the correct command was

sudo chown -R tc /mnt/sda2/playlist (Or was it "hda2"? Can't remember.)

where "tc" is the USER (tc of course stands for "tiny core").

[Jason W]

Oops, yeah the command should have been

sudo chown -R tc:staff /mnt/sda1/music

and substitute tc with the current user if other than tc.

[KingBongo]

Jason W:
Hey! That's interesting. What does "staff" in "tc:staff" mean? I didn't use "staff" and it seems to work anyway.

[gerald_clark]

staff is the group.  Please get a book on basic Linux.

[maro]

I didn't use "staff" and it seems to work anyway.

That is probably due to the fact that the file in question was already belonging to the 'staff' group.

Nevertheless it is probably considered to best practice to typically use 'chmod USER:GROUP FILE' (i.e. specify ownership as well as the group), unless specific (and well understood) reasons suggest to use "only" 'chmod USER FILE'