Readynas

news

I apologize for the lack of recent updates. The main reason is that I moved, or better, split up, currently into three different places: My new flat, my old flat (which still takes care of a lot of my equipment), and a new home for electronic devices, called “waldobjekt”. The waldobjekt is a place which finally has enough space for all of my projects (and much more). >260 m² of space for storage, working and having fun!

Compiling a ReadyNAS kernel...

I’ve struggled a day or so with this, so let me summarize: Infrant loves replacing their kernel every now and then with a different version, without changing the filename. Be sure to not use the RAIDiator 2.0 release. It’s buggy and misses stuff (so much for “GPL compliance”). The 3.0 (md5sum of .tar.bz2: d7da0363a6d4da912907dd03385d6f7a) is ok. You need to use gcc-2.95.3 to compile the kernel. I’ve spent half a day to fix the kernel to compile with a recent gcc-3.

Running own code on the Infrant ReadyNAS

The Infrant ReadyNAS NV is a Sparc (Leon) powered NAS. It’s not really cheap, but, well, I’ve got it somehow cheap. It featueres 4 SATA channels and Gigabit ethernet, unfortunately it runs a heavily modified Linux Version. Now, Infrant (of course!) complies to the GPL by releasing a 2.4.20-based kernel every now and then, of course every time with an undocumented set of changes under the same filename. Did I forget to tell you that some kernel releases are missing important files (lp_code, lp_data for example was missing in the “2.