hi, just wondering if anyone can help me how to disassable the official firmware for modification? to create a new one.
i'm just puzzling around with chroot. after destroying the actual installtion of the box several times its now possible to start f.i. nfs-user-server. but starting the apps is a lot more tricky than i thought.
but up to now its the easiest way to add more functionality to the box.
if it sound intresting i will report furtheron.
Hi guys ive been having a play with the firmware image and I have a way of editing the root fs (on my ME1 at least ellion probably also)
On my ME1 I just managed to extract the root filesystem image, modify it (added a symlink, edited the hostname, added a test text file) rebuild the squashfs, the firmware image and re install it.
Now when I telnet in it says ME1 instead of Venus plus I have a symlink and an extra file so I think it might be possible to add additional components to the root fs and upload them as binary images.
One thing with this is that I didnt increase the hard disk image by much and there looks to only be 1MB or so free in the root FS before it would need increasing. Im gonna play a little more to see if I can increase the size, obviously we could always place some components outside the flash image if needed. Unfortunatly the root image has another image straight after it and im unsure where the file locations are set within this file.
I seriously doubt you can do these tricks in windows, ive used quite a few linux only tools to do this plus when you re squash the fs you need to keep the permissions intact otherwise it wont work.
Im going to try and add samba to the firmware image (using the ellion samba binary without netbios) but as I said im unsure weather I will have enough room but I will try ;)
but like the admin of this site stated at the download section, emprex and ellion uses a different type of firmware. i already searched for the signature of squashfs and lzma compression on the emtec firmware but I didn't find anything. so now i'm figuring out what kind of compression or filesystem the firmware is using :-/