[N4100+] Modules won't be enabled!

[Dr_Dan]

Hello,

I just tried to install the SSH 4.0.0 module.

I modified the install.rdf to cope with the thecus N4100+ repacked the files and installed it.
But when i want to enable it, the module refused to start.
When i tried to remove it, it refuses to be removed.

Could someone help me on this ?

Thanks,

Dan.

[Stefan Huebner]

While repacking mostly the error occurs...

Have a look at: http://onbeat.dk/thecus/index.php/N2...ing_the_Module

If you have a trailing slash behind the path it doesn't work - I had the same problem yesterday... When unpacking on a desktop machine evrything seems fine. I dunno what Thecus changed in the tar-source, but it happened to evryone who tried changing a module 8=(

[Dr_Dan]

Thanks again for your help Stefan.
I forgot the leading ./ when i packed the module.

I can login into the box.

[Stefan Huebner]

great

Don't get too diappointed when finding out how small the abilities of the busybox inside are ... I just rewrote/changed a script for the third time because on my linux box @home it works, but not on a thecus...

They didn't even compile "stat" in. Now it's workaround-time

[omega]

Even more worse Thecus is still using an outdated buggy version of BusyBox.

I've told them to fix this about 10 month ago but without any success.....

Andreas

[Stefan Huebner]

has anyone actually tried to compile an own firmware version abusing the http frontend only?

[omega]

The compilation of a own new firmware version isn't the problem - the firmware files are encrypted and no one knows the key.

I've already examined the code but I don't have enough time to crack it, although I've some ideas...

Andreas

[Dr_Dan]

great

Don't get too diappointed when finding out how small the abilities of the busybox inside are ... I just rewrote/changed a script for the third time because on my linux box @home it works, but not on a thecus...

They didn't even compile "stat" in. Now it's workaround-time

As these devices were designed as file server and not as multi-purpose server, i expected what's inside the box.

[Stefan Huebner]

As these devices were designed as file server and not as multi-purpose server, i expected what's inside the box.

Well, but as a file server I'd at least expect a few features like "cp -u" (update a file), or that ash does this correctly:

for file in "${source}/*" ; do
    makesumthing $file
done

But if there are spaces in the path, it won't work correctly although enclosed in <">. My dash @ maincomputer does, tho... (gentoo doesn't offer ash from inside portage anymore...). But I guess I'm just expecting too much from shell scripts ...

[omega]

Hi Stefan,

I think you're code is wrong. What's about this:

for file in ${source}/* ; do
    makesomething "$file"
done

Andreas

[Stefan Huebner]

... also doesn't work, that's why I changed

 for file in $source/* ; do

to

 for file in "${source}/*" ; do

... I wanted to make it perfectly secure by that, but it still didn't work. What needs to be done is: replace all spaces in $source to escaped spaces. Haven't had time to try it, yet, but I guess that'd work. BTW.: how would that be done?

newsource=`echo $source | sed -e 's/ /\ '`

???

and I just saw a typo: the <makesumthing "$file"> was what I meant.

[omega]

Hi Stefan,

this code

for file in "${source}/*" ; do

will never work as the shell won't expand the start because it is inside double quotes. At least in every normal shell it will be like this.

And your idea escaping spaces looks really weird.....

What did you tell is the name of the crappy shell? ash? what version?

Maybe I have a better idea:

for file in $(/bin/ls -1A "$source/") ; do

Andreas

P.S. I'm really happy the N5200 having at least a reasonable shell. What we're discussing about doesn't apply to the N5200 at all

[Stefan Huebner]

great idea. Thanks for the hint. I'll look into it after the weekend.