|
Post by kniteowl on May 24, 2007 1:40:39 GMT 7
As I look at the current modules that we currently have out there, one of the key items that keeps coming back is the inability to add or change items to the ReadOnly section. Sometimes, it is minor and a workaround can be done, but to keep the system clean, sometimes it would be nice to just change one or two files.
Had anyone created a custom firmware from the Sources that you can get from Thecus? I don't want to start from scratch, and try to get everything working, just want to be able to modify a few items.
Secondly, if no one has it yet, anybody know now to create a build environment to make the firmware, I have been looking at the source and it seems that there are items that are missing, I understand that Thecus does not have to include anything that is not GNU license and I am OK with that, but if I am changing my system only, I am sure that I can copy some of the missing files from my own machine, minus the build scripts of course.
Here is kind of what I was thinking, let me know if I am missing something in my logic:
Create a folder say "CustomFirmware" Decompress the source into this folder Copy any missing files from the live N5200 to this folder CHROOT and test to see how things work, if things seems to be fine, start to build a build script to do it automated.
I just want to be able to add, remove, change the admin web page to include my own stuff, etc..
Teng
|
|
|
Post by omega on May 24, 2007 15:27:23 GMT 7
Hi Teng, your idea is not really new..... I've had this idea right from the start as I wanted to fix some of the obvious bugs in the Thecus software. To overcome the read-only issue for the dir tree below /img/.... I've create the IMGDU module which just copies the /img tree to some place on the RAID and replacs the original /img dir by a symbolic link to there. Unfortunately there are still some minor quirks dealing with the IMGDUP module, mainly when trying to stop/reboot the system. But basically it works. The main problem with the idea building a modified "firmware" (we might better call it modified loop images) is the fact that the images are encrypted and nobody yet knows the passwords. Thecus has augmented the cloop filesystem driver by that encryption feature and of course that code isn't part of the source code they provide. I've already started to disassemble the cloop driver some (long) time ago but it'll take me too much time to crack it although it won't be to hard. Andreas
|
|