How in the name of all that is holy, can you release something and not make it clear what the root password is? Once it's on my system, I want control of it… Period, not debatable…

It took a while to even find the pi/raspberry login, since the directions are more than a bit unclear… So, why not follow a very simple suggestion? Stick the passwords in a .txt file in the .rar and be done with it… And choose a user/password scheme once and for all, and stick with it, I found multiple variations from other RC's…

So… What is the root pass for RC2? And for 1.0 beta? Not amused… However, the system looks nice enough…

admin said

Tweety, in the beginning I thought you were only unpolite, now that I better read what you wrote I realize that you're simple not familiar with Linux, open source and/or human communication patterns.
As all other RaspyFi users did, you may have better read the quick start guide, the .txt on Sourceforge or the download page.
Then, if you wish to comply your right to control your system, well, could sound silly but
sudo su
could make your day.

Actually, no… You got that right the first time, then… I wasn't in any way aiming to be polite… I was ticked off by a lack of logical communication from your end…

And your post just clarified that you completely missed the point of what I said, the reason for it, and attributed it to me being unfamiliar with "open source and/or human communication patterns"… Ie, simply passing the blame, and on top of that implying in a rather blunt way that I'm less intelligent than the rest of your users… Which in itself constitutes to you being impolite, if we are pointing fingers… So… Pot, meet kettle…

OK, now that we got that out of the way, how about I formulate my question a bit better, and you address the issue in the same way?

You have a download link pointing to a single file, through various ways (like to download, direct and so on)… That file in itself contains no additional info what-so-ever… This is on some level is just fine, since being more than enough familiar with what to do, I knew how to prepare the image for use without any information… I also knew how to setup a client on iPhone/android/Win/Linux without help… So I didn't need to go looking for any information at that point…

What I did do, was take a guess that you had set up the mpd to have no password for connecting the client… Which was correct… So, without looking for or needing any instructions what-so-ever, I had the Raspberry set up as a "RaspyFi", seeing the music on a USB drive… But since I have no USB DAC that works with this, and the one I have ordered haven't arrived yet, I ended up running into the little glitch that the onboard analog output was disabled by default, contrary to what the obvious information on the site stated…

So I start searching for info… And finding the info scattered around, I fixed that issue pretty quickly, although after a little trial and error there, I got annoyed with it and wanted to do other things as well… Ie, going to root was more convenient than sudo… type in "su", and get a promt for root password… fine… Go looking for that… And I find no obvious link to the information, so I use Google site search, and I get the password "raspy", which doesn't work… I try the obvious one's like "raspberry", and a few other combinations… None work… Until I leave it blank… Which works… Meaning you are sending out the image with no root password set, which is a big security no-no… And no, since that is a non-no, trying that isn't exactly obvious either…

So, in this situation the part from your end is this… No info included with the downloaded file… No obvious link to a "start here info" on the site at first glance… And no, documentation -> howto and then going down the list isn't "obvious"… Either stick it on the top of the page, or make it an top-level link in the menu itself… I'd say that this information is more basic/pertinent to have as a top-level link than "Compatible DAC's" which is more than obvious… Then you have more than one combination of username/passwords to be found when searching… Now, don't even try to tell me that this is a common thing with "with Linux, open source and/or human communication patterns", because that is plain and simple bullshit, nothing else…

You fumbled the ball… You have incorrect information posted in obvious places, with the needed/correct info buried where you either need to read a lot of back and fort Q&A to get to it, or search for it… Plain and simple bad practice in documentation, nothing else… Yeah, I realize this is a one man job, and I'll say without any reservation that it's impressive, and I'm grateful for the work you have done… But, still… It doesn't take 5 minutes to correct the info on your top-level post saying that this and that doesn't work, look here to fix it… It would lessen the annoyance a fair bit…

Yes sure, I should have realized that I could go to Sourceforge and look for an additional file to know which password was actually the valid one for the RC2 image, and yes, it is "correct" to put that information in a separate file like that… But with a download link giving me the single file, I still maintain that it would be a lot better to have that .txt included in the archive as well in the first place…

End result… Annoyed, and not entirely polite, since the information needed is placed in not so obvious places, and incomplete, faulty or just missing…

But, to soften the blow… Again, thanks for the work… Once my DAC (took you DIY recommendation) shows up, and I have built a suitable PSU, I'll free up an 8GB card and try the 1.0 beta…

admin said

Markus, in order to avoid wasting mine and yours braincells, next time just say: hey, please stick user and password somewhere clear and start documenting this project properly. It's easy and works.

Sure… I can do that…

Dammit… I hate arguing with people that are too similar to myself… I just end up getting answers that are logical and reasonable… It ruins my rants…