Decklin Foster wrote: >Excerpts from David Bremner's message of Sat Aug 29 14:26:35 -0400 2009: >> Maybe it is just me, but it seems like the most common thing to do >> with mpd is run it on the same host, as the user on the console.
>Why? Seriously curious. So that I don't have to do anything special to arrange my music files in my home directory as my normal user. If I use the system daemon, I have to arrange it so that user mpd can read the files, and presumably write playlists. Or move all my files into /var and su to mpd to edit my music files? Let me turn the question around. Given I am the only (human) user on most of my machines, what are the advantages of running mpd as user mpd? Maybe if they are compelling, you could document them somewhere. >> (or using a different port, I guess). >I'm not sure what this means. If the system daemon is running, then another daemon can't listen on that port. >> Anyway, it would be nice if the initial install asked about running >> a system wide daemon. Or from my point of view (but maybe not >> everyone's) if the system daemon was disabled by default. >Turn off START_MPD in /etc/default/mpd. This is documented in >README.Debian. Yes, I understand that. Obviously we have a different idea about what the common case is. Since I have no data, I'll take your word for it that more users would be inconvenienced by answering a debconf question than by those that currently have to disable it (I agree disabling existing daemons would be met with howls of protest). Also, if you think it is not worth futzing with debconf for such a minor thing, then that is reasonable too. Thanks for packaging mpd, David -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
