Merty's Blog

I quit (sort of)

Last post on this blog. People will notice the lack of updates of this blog and my Synology pages, although they are updated from time-to-time.

The reason is simple; It takes too much time and I have too litle fun in return. Therefore, I decided to stop responding to email or forumposts and update stuff "when *I* want too" .... Let me try to explain...

When I just bought my first Synology NAS, recommended by a co-worker, I liked the small, simple design and also the software that comes along with it. We thought how nice it would be if something like SABnzbd would run on this, so we wouldn't have to have our PC's running all the time. At the same time, some DiskManager came with an update that will allow "packages" to be installed. By reverse-enginering those packages, peeking around in the firmware, dissecting the AJAX calls and Extjs, I was able to discover how things worked. In the past, I developed for embedded systems, like cash registers and ATM's, so I'm familiar with C, cross-compilers and the ARM environment. By combining NSLU2 feed, the right GNU-gcc cross compiler, Synology was a bit late providing these, and a lot of tinkering with python, perl and unix scripting, I was able to make SABnzbd run on my synology machine. With help from others, I was able to compile the stuff to other environments too. To learn how the packaging system and GUI worked on the DiskStation, I created a few simple packages, some tooling I missed myself. Not wanting to be selfish, I released the information to forums and also the Synology wiki.

So, all of this was just a way to waste time, hacking, tinkering, developing stuff. I never had and never will receive any money for it. It was never intended to be more then just a hobby project. The only reasons I did set-up my webpages and packaging server was - and is - :

Main reason for writing the packages in the first place was simple: I just wanted those things on my Synology machine and couldn't find an alternative, so I wrote my own.
I used Open Source and information gathered from everywhwere and I'm a huge advocate of this idea. If you use something that is open and free, share it under the same conditions. It is not a religion or weird thing to do, it is just courtesy to other - much better - developers out there working on these great products.
I have a great job, which pays well and really don't need a -renewed- career in software development. I'm to old for that. Therefore, there is no need to brag about, or to find investors, or to compete with others. I don't mind at all if people are copying my stuff or Making money out of it. I really don't care.
It was very rewarding exchanging information with other people, discovering things, having a simple "hey, thanks for the great software" mail every now and then.
I really hoped my information, code and packages would help others to create packages for Synology. It took a long time, but nowadays, a lot of groups are working together and creating cool packages and setting up package servers. Those packages and coding was better then mine, I would say..

So, at this moment, there isn't much left to do, other then just updating the packages, creating new ones, finding out what the new update of DiskManager broke this time and so on. But there isn't much fun it anymore, I have to admit.

Most of all, the enormous amount of email and not-realy-nice-encounters is a draw-back that keeps me from doing anything more then just update if something realy is broken.

It is not fun to receive 15 (!) voicemail messages on my mobile by a local salesman of Synology diskstations, who promised to a customer that SABnzbd package will work on the new released and diskstation, sell it to the customer who will complain later that it didn't. I never make such promisses, and I'm certainly not a company you can call 24-7 and demanding fixes.
When Synology releases a new -beta- software of DiskManager or there is a new SABnzbd version, I will notice it inmediatly: My mailbox will get 30 a 40 emails the same day, asking me about new packages. I don't mind, but people ranting on forums that there is no update for my packages the same day that the new - beta - DiskManager is released, is something I really don't like. Same thing goes for new DiskStation models. Even before they are released, people "demanding" that my packages works on them.
I really hoped developers did get in touch of me, or people helped me find bugs in my software, and some did, which I really appriciate. But....most of my email is something like "Hey, XXX package don't work. When do you fix it ?" .Tried setting up FAQ's on this website, Forums, pointing them in the right directions. Creating a log facility, better error reporting, but on the end I spend to much time trying to be a helpdesk-via-email figuring out what the h*ll was wrong and wondering if anyone actually read the information I left about it (oooh...I have to press *start* to start package...now you tell me !) So, I stopped responding to these emails, and I'm really sorry if your are one of those guys.
Another stream of emails is about requesting package X or Y for the synology diskstation, most of the times software that was close-sourced and only able to run on Windows. Please contact the makers of that software and not me.

In summary, a lot of email and forum posts are quite demanding. Somehow, people do tend to have the idea that they can receive full service support like they -might- have from any commercial software vendor. But I'm not. I don't receive, and want to receive, a dime for it. It's only me, having a hobby and sharing the stuff I do in my own free time.

So, I decided to find other new fun projects to work on and not help nor respond to any email about my Synology packages. I will update when I think I need to update, because I still use my own packages. Nowadays, a lot of people are creating packages, including SABnzbd+ ones, so there is no need to stick around here...

I really hope you guys understand..

Regards,

Remco AKA "Merty"

Firmware 3.0 & sabhelper

Yup, still alive, but really busy with a lot of other non-syno related things. However, my mailbox is getting swamped by people who try to upload new versions of SABnzbd. I though that is strange, since the firmware didn't update or removed a lot my programs depended on..

Somehow the SABhelper program wasn't doing anything with the new firmware. Weird. Debugging with firebug shows there was no traffic at all going on...what the ...?

As it turns out, the new firmware came with an EXTJS library that was a little bit broken. For your information, EXT JS is the javascript "glue" that Synology uses for ther admin gui. It is a great API to work with, however, a pain-in-the-rear-end if something isn't right. So, as last resort I unpacked my "own" ext-js package on my diskstation, the one that I made for earlier diskmanagers that didn't ship with it, pointed everything to this directory and voila...it worked like before.

Soo.. of course you shouldn't be messing around on the command line replacing ext-js libs, so I think I will "update" my ext-js package to work with the SABnzbd to solve the problem.So, please wait till my page is downloaded please.

Also, please stop mailing me about 'normal' SABnzbd problems, I'm really, really not an helpdesk or do have time to help you all. Go to forums of Synology or SABnzbd..

Still Alive ...

Well, just an update to let you all know I'm still alive and still working with the Disk Stations. I do have 2 now: DS408 and a DS1010. I realize you might haven't heard from me last months, but that is because of my other activities that are more important, like reconstructing rooms of my house and a new job, being a manager and architect at once, managing a very busy department of 30 people doing various development projects en dealing with several supplier of even more people working abroad.

Anyway, back to Synology Disk Stations.

First: Yes, I'm aware there are problems with the new DSM3.0 beta version. I'll look into it as soon as I have installed it myself on one of my Disk Stations. Looks like ssl library don't play "nice" with python ssl library for one, but maybe more is changed...

Second: Please, stop emailing me - or posting comments on this blog - with very common or very unclear errors. If you really need help, I'm probably not the best person to contact. Place question or problem in either english or dutch Synology forum, and other might help to answer your question. I'll drop by on those forums as well to see if I can help. I'm sorry, but I don't have the time to answer all email.

So, what's in store for future, besides from fixes ? Well, I was working on getting Subversion server working on the Synology Diskstation. It is working (cross compiling all SVN stuff and solving all dependencies is a disaster, I can tell you know), but still need a GUI thingy for users to create new SVN repository and point to right logical volume. So, it might take some time...

A quick run into common questions:

Q1) Are you aware that sabnzbd+ doesn't work on DSM3.0 beta

A) Yup, I know, thank you telling me this (round about 60 persons emailed me about it..). I'm working on it..

Q2) When do you release with 5.3 version ?

A) Dunno, probably soon with fix for DSM3.0 bet. BUT YOU DON'T NEED TO WAIT ! You know, that is why I wrote the "SABnzbd+ helper" program, to upload the *sources* of SABnzbd+ and yourself, including the 5.3 version. You don't need a new package...

Q3) How do I update to 5.3 version ?

A) Use SABhelper. If the package is installed, press "reload" of your browser screen. In admin screen on the left you have a pane with different options/programs. One of it is called "3rd party software", under this folder you'll find "SABnzbd+ helper", click on it to start.

Q4) Can't upload new version

A) You are probably uploaded wrong version. You have to download the python sources of SABnzbd+ , nothing more or platform specific. To be correct, the file extension should be tar.gz or .tgz. Other files will give an error about not finding SABnzbd.py (extra check to prevent installing non-source code package). Download it from http://www.sabnzbd.org/download/ page, "Python source (linux etc.)" button.

Q5) Your program isn't working

A) To bad, however you didn't provide me any usefull information I can work with, starting with which program isn't working. Again give me more to work with, or better, try it again in one of the synology forums. I'm sorry, but if the only thing you can say is "it isn't working" without providing me about what you did, the version you use, what kind of DS you have, what you see in the "log" tab, I can't help you and don't have time for a long "try this" or "how about that" back-and-forth emailing scheme.

Q6) Can you make <name or program> for Disk Station ?

A) Nope, can do, no time besides other reasons why it isn't working at all, see previous posts.

Q7) SABNZBD+has a bug

A) if it isn't platform related, please bug the SABnzbd+ developers about it..

More errors

Talking about errors... In the 2.3 firmware, the S97apache-user script (the script to start/stop user webserver) overwrites php.ini file with default values, making my WebShare Enabler program worthless. Fixed it, new version can be downloaded. Uninstall previous one.

Firmware 2.3, errors and questions

Well, firmware 2.3 is out and I like the new features. However, there is a downside: several people report memory problems, not only with SABnzbd+ but almost all programs that needs memory from time-to-time. I think one of the new changes in the 2.3 firmware is leaking memory as hell... I don't see any strange memory usage when using SABnzbd+ on the 2.3 firmware - and why should it, it worked without problems under 2.2 and even beta). Hope Synology will fix this, in mean time, when you have memory problems, the only way to get rid of it is to reboot your Synology nas again. Also, try to prevent indexing of video/audio files, also a "usual" suspect of resource problems.

Further on, I do receive a lot - In the range of 20-30 messages a day - questions. It is hard for me to answer them all properly, I do have a normal day job, you know ;) . Also, a lot of questions do popping up in this blog. I urge everyone who has a technical problem to post it in the synology forums. Or better yet, check if this question has been answered already. I regarly check the international and dutch Synology forum. Doing this, there is better hope for an answer, if not from me it would be from somebody else and by doing this, you help others who might have the same question..

Oh, and talking about errors I do feel responsible for: yes, SABnzbdHelper can't fix strange characters in directorynames (yet)...

0.5.0 Final

Right, 0.5.0 Final. Although everyone should be able to just upload it via Sabhelper, lot of people still requested it. So, there you have it. I few minor fixes:

* Old firmware didn't have unzip, unrar, so included it in package for "old" Syno's. Although SAPhelper might not work, SABnzbd+ should work now.

* Open new page when clicking on SABnzbd+ instead of opening in frame (thans for the tip Robbert!)

* Somehow, I managed to pack 2 SABhelpers in previous, old & new version...whoops.. This time the real, last one. Hopes it fixes some "not working" issues.

Short guide SABnzbd+ install & configuration for dummies:

1. download package (zip). Some Mac programs and Safari browser are a bit to eager to unpack *everything*, including contents of package itself. So, when on mac, use Firefox to download

2. unzip it, extract the *.spk out of it

3. Go to packagemanager, click install (no, not upgrade) , point to package, choose a nice volume ...

4. After installation, click on the sab2 row. Click "run" button

5. Click on link that appears (or go to http://your-adress-of-your-nas:9200/)

6. Follow instructions to configure:

- don't check 'I want SABnzbd to be viewable from my pc only.' (checking this would block any browser on the network to sabnzbd+ page)

- don't use "launch internet browser when..." (wouldn't work anyway, starting a browser on your nas)

7. WAIT before downloading anything: default configuration isn't right

8. configure filepermissions: 777 (read-write for everyone)

9. Go to SABnzbd+ helper, in your admin menu, bottom left, "3rd party software". Click on it

10. Choose share you want to have the SABnzbd+ on it

11. Press save configuration

12. Go back to SABnzbd+, configuration of folders should be changed to the "real" directories of the share you choose.

Have fun.

Remco

Complete new version of SABnzbd+ package with SABnzbd+ 0.5RC3 - or whatever version you like

Finally ! At the moment, I'm uploading new packages for all recent diskstations (DSx06 and later) including the DS1010+ . As a happy owner of a brandnew DS1010+ I had to compile for this version to, of course. I will update download page tomorrow, but to give you an inside of what is changed:

* Included 3th party "SABhelper" this program wil help you with:

Upload the version of SABnzbd+ you want: just grab the sources tar.gz file and upload it via SABhelper ! Now you dont have to wait 'till I have a new update version, just upgrade when SABnzbd+ is released !
Setting the right download directory/share, just click on what share you want your SABnzbd+ on.
Strange characters in filenames that prevents deleting or using the file
Setting file and directory permissions to everyone on all downloaded files and directories

* python upgraded to version 2.5.4 (no, don't wanna use 2.6 there is no benefit in this)

* ionice included (only supported on DSM firmware with kernel 2.6.13 or higher)

* The Synology versions of unrar & zip that comes along with latest firmware version will be used.

* SABnzbd+0.5.0RC3 is included in package (and of course, you can always up- or downgrade it via SABhelper)

* Admin URL in packagemanager will go directy to SABnzbd url. No need for redirect script or specially crafted URLS. Even port configuration change will update admin url.

* New chipset: Intel Atom. It's good to see Synology pushing out a new crosscompiler kit that fast for the new DS1010+ and DS710 ..

* Much improved & speeded up start and stop of services. Will not interfere with any other python processes

If you don't trust this new package yet, you can always use the "old" one, even next to eachother. Just beware that by default, they share the same portnumber: 9200. So, make sure only one of them is running at the same time, or configure one of them on another port then 9200 (9201).

For those who can't wait, these are the download links to different version (check wiki or links in my download page if you don't know what kind of CPU you have and which file to download):

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-arm88f5281-40-spk.zip

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-arm88f6281-40-spk.zip

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-ppc8241-40-spk.zip

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-ppc8543-40-spk.zip

..and finally, the DS1010+ version:

http://www.xs4all.nl/~merty/syno/SABnzbd-0.5RC3-x86d510-40-spk.zip

Have fun..

Beta

Just a quick update: working hard on new SABnzbd+ package and a "sabhelper" package. Still in progress. Will not help if you accidently remove your development directories . Anyway, for all people asking me about the alpha-beta version of SABnzbd+, here is an update package to try out beta version of SABnzbd+ (mind you, its still only an "update" of my "old" package):

http://www.xs4all.nl/~merty/syno/SABnzbd-UpdateTo0.5-beta6-All-24-spk.zip

New DSx10j models

Ok, A small update. I really get 1 email per hour now because of the new DS210 models. At the moment there is the DS110j, DS210j and DS410j as far as I can see. They all have the same CPU/environment as the DSx09 model (without 'j' or '+').I've updated the downloadlinks for this models. Also, everything is zipped now. Some pesky browsers or operating systems did had the nasty habbit of 'recognizing' the spk format as tar.gz and unpacking it after download. So, to prevent this, all SPK files are zipped...

In the mean time, I'm working on a .psk package as an answer to all those people who are "misfortunate" to not read my instructions to CONFIGURE THE DOWNLOAD DIRECTORIES TO AN ACCESSIBLE SHARE BEFORE DOWNLOADING SOMETHING. Some people don't understand telnet or ssh and I'm realy not in the mood for linux-commandline-tutorial-writing. So, this program should move the files into an accessible share and will "clean up" problems with read/write rights and strange characters in filenames. At the moment, I only have the AJAX part working (progress bars in Extjs are cool, you know), now the real stuff....

License

When browsing on the web looking for Synology info, I came accross this german wiki page "http://www.synology-wiki.de/index.php/%C3%9Cbersicht_%C3%BCber_verf%C3%BCgbare_3rd-Party-Apps_aus_unserer_Community". Besides from packages I didn't know about, it mentioned an interesting footnote: "Wenn es ihm gefällt, kann er als Urheber morgen sagen: "April, April ... ab jetzt dürft ihr nur noch damit spielen, wenn ihr bei mir eine Lizenz kauft." GLP schiebt einer solche Willkür einen Riegel vor ...". Well, my German is not that good, but what - I think - it says it that although I said it is free to use, I still have te ability to change the license of my packages and start asking licensemoney for it. Although I would never, never do such a thing and it will be questionable in court if I start asking money what I was previously giving away for free, the poster had a valid point.

So, thats why I will "changing" the license to an well-known opensoure one. I was thinking about GPL, but I think that is a bit to restrictive. I don't mind if someone alters my packages and rebrand them "closed source" or ask money for it (good luck !, doubt you will make any profit out of it if my version is still free). Actually, I don't mind at all what you will be doing with the stuff I provide, as long as you don't drag me into court because it is not doing exactly what you think it was. Therefore, I choosed the less-restricted "BSD" license.

In the next coming updates of all packages, I will include this license into the programs. This will change not that much for you as end-user, but will give you the guarantee that I will keep this open source and will prevent me from nasty liability accusations..