Tiny Core Base > Release Candidate Testing
tinycore_v2.9rc1
roberts:
--- Quote from: gerald_clark on January 31, 2010, 03:36:32 PM ---The AppsAudit 'Display All NotDepended On' works great, and found old extensions that could be removed.
Thanks.
Is there a reason that 'losetup' limits its output to the first 10 loop devices?
Have tested TC and MC with no problems.
Great job.
--- End quote ---
Thanks!
re: losetup
Likely because it is a busybox applet. I will have to check. I am planning a busybox upgrade.
bmarkus:
It is not really a 2.9 issue but an AppBrowser feature request. When a download is not finished, a partial file left in /tce/optional with an md5.txt file. Of course, extension is not registered in /usr/local/tce.installed but next time if you want to install there is a HTTP 416 error, requested range can't be satisfied, etc... wget message is not informative and doesn't help to find out what is real cause. Solution is to delete partial download manually.
Proposal:
lets AppBrowser check the download dir and if it exist with not matching md5 delete it before downloading. Maybe asking for confirmation.
Jason W:
The -c option was added to the wget call in tce-load a while back to prevent an aborted transfer from causing issue. That helps with interrupted downloads of large extensions as the download simply continues from where it left off. But I see the error message you do related to the download of the md5 file, and when the md5.txt is deleted, the appbrowser then succesfully finishes the installation.
It appears to be an issue with busybox wget and the continue option. Simply returns the 416 error when the file has already been completely downloaded instead of staying quiet.
bmarkus:
Thanks for the info. There can be different solutions, but it has to fixed somehow. It caused me some headache trying to install extensions with no luck. Guess was not alone :)
helander:
You are not alone :)
/Lars
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version