Unpacking the GPL source packages

[drewpuppy]

These files are given to us with .tar.bz2 extensions but bunzip2 tells me they're not really bzip2 files. I can partially unpack them with tar but I always see an error.

What schoolboy mistake am I making here?

Thanks in advance,
Andrew.

[omega]

Hi drewpuppy

just try this command and you'll get what you want:

tar xzf n5200_1.00.07_GPL.tar.bz2

Reason: Thecus was just using the wrong extension, it's a gzip compressed tar file and not a bzip2 one

Hint for the future (but not working on the N5200): try the file command (e.g. file n5200_1.00.07_GPL.tar.bz2) and it will tel you the data type.

Andreas

[drewpuppy]

Thanks Andreas, great info as always. That's actually what I tried first and all the tars (Linux and OS X) I tried all failed to completely unpack the file, which is odd. Mac StuffIt Expander did do the job though.

I've been ill over the last few days and I'm probably missing something dead obvious.

I wanted to take a look at the sources because it doesn't seem as if a module's update.sh script is actually being invoked and I want to find out why.

Andrew.

[omega]

Hi Andrew,

did you try to unpack one of the source tar files again and is it now working? Just curious....

The reason why you don't find the place where the update scripts is called is that there is no place where the update scripts is called...

I've told this already Thecus, they confirmed it and they told me that this feature is due to come.....

Andreas

[drewpuppy]

No, I can only unpack the sources with StuffIt on OS X and nothing else. This is good enough for me, so no worries.

I assumed that the update.sh script wasn't being run and thanks for confirming its an admitted bug. It's not a big deal for me. I suspect many N5200's won't even have a web connection available to them to use to check for updates anyway. My firewall prohibits any net connection of any kind to or from my N5200 and I'm not intending to change that in future.

Andrew.