Hi,

 

So installpkg is back in beta2, but i get this message when trying to install unrar and bwm-ng:

 

root@NAS_Serup:~# installpkg /boot/Customizations/bwm-ng/bwm-ng.tgz
Cannot install /boot/Customizations/bwm-ng/bwm-ng.tgz: package is corrupt (failed 'gzip -l /boot/Customizations/bwm-ng/bwm-ng.tgz')

root@NAS_Serup:~# installpkg /boot/Customizations/unrar/unrar-3.7.5-i486-1.tgz
Cannot install /boot/Customizations/unrar/unrar-3.7.5-i486-1.tgz: package is corrupt (failed 'gzip -l /boot/Customizations/unrar/unrar-3.7.5-i486-1.tgz')

 

I have used thise packages in v4.2.3, so should not be corrupt.

 

Anyone got at clue to this error?

 

Thanks,

Søren

 

 

Missing gzip 

 

A bit of explanation: in moving to latest linux kernel, we also upgraded to slackware 12 in order to pick up the latest packages.  But in order to keep the unRAID OS root file system as small as possible, we're very selective in which packages are included & that is a big reason we dribble out a set of beta releases - so that packages used in custom configurations but missing in our release get identified.

installpkg and gzip should be standard for any release.

 

I think with the cost of ram these days, and now the ability to use more of it.

We have the ability to have more packages.

 

----

 

I had an idea recently.

Ever consider having a local filesystem mounted via loopback from the /boot flash?

Maybe some customized programs could be stored there in readonly fashion thereby not taking up valuable root/ram space.

 

I've been toying with this idea, only the emhttp binary exists in /usr/local/bin.

so I would be forced to mount over it.

 

I'm thinking along the same lines as a swapfile mounted on loopback, but rather a filesystem mounted via loopback.