2014-02-25, 22:34
@vbat99
Sure, I actually had that in the beginning, but corruption was an issue back then so I deleted it.
Probably need --no-check-certificate and I´ll make a shortened url as well, but I still want to keep it separate from the XBMC update though.
@alphatech69
Cheers.
The "real" work has nothing to do with me though, popcornmix and team XBMC are the real heroes. And Sam of course for providing an excellent distro.
I am still sort of a Linux n00b myself, so don´t ask to much of me.
@popcornmix
Regarding the "issue" I reported earlier, I believe I am to stupid to follow my own advice. Running the old build was better, but I believe I have found the issue and it´s not related to any commits or builds.
Will wait a while though before I feel certain, I tend to report issues or fixes to fast. Apologies...
Another thing, when fetching firmware via SSH, do you think it´s a good idea to run 'sync'?
Sure, I actually had that in the beginning, but corruption was an issue back then so I deleted it.
Probably need --no-check-certificate and I´ll make a shortened url as well, but I still want to keep it separate from the XBMC update though.
@alphatech69
Cheers.
The "real" work has nothing to do with me though, popcornmix and team XBMC are the real heroes. And Sam of course for providing an excellent distro.
I am still sort of a Linux n00b myself, so don´t ask to much of me.
@popcornmix
Regarding the "issue" I reported earlier, I believe I am to stupid to follow my own advice. Running the old build was better, but I believe I have found the issue and it´s not related to any commits or builds.
Will wait a while though before I feel certain, I tend to report issues or fixes to fast. Apologies...
Another thing, when fetching firmware via SSH, do you think it´s a good idea to run 'sync'?