francois wrote:And what was wrong with my last trial? Have I done something wrong according to your expertise? ... Is my recap of your procedure on first page is exact?
Can't tell, but seems like you have corrupted awk_distro file.
Is removing all the files and folder other than the four above mentioned files between runs will be enough in addition to:
Code: Select all
root@porteus:~/pak# source pakfuncs.sh
to reuse the resolver?
Once you are clean, quite the contrary. Just start a new terminal/tab.
francois wrote:How do I reset /pak anew without having to replace all files?
Am keeping permanent copy of 'pak' directory on real file system and running like so:
Code: Select all
cp -a p10/Por/PakOrg/apak .
At end of run if haven't made mess of things, updating thus:
Start from scratch with a clean slate.Your download rate is multiple of mine. Here we are looking at most a 100 text files of about 20K each=100x20K=2000k=2 MB. Downloaded in a couple of seconds! After all, quite a bit of computing is about speed through superfluousness. Doing things needlessly in order to get the job done quicker in RL. :wink:
francois wrote:Is it possible to automate some of the procedures, like do you want default choice ask the way?
Unfortunately this is an intelligence driven procedure. Just replaces what you would do manually if going through pkgs.org.
Objections to Automation
- Сhange of package name. If name does not match it could be a devel/test package. Therefore filtered out. Need to check out package by browsing. Automation might mean not remaining in same distro, when no need to change.
- Change to something fundamental like gclibs or gcclibs or similar by going to too low a level of dependency, resultant module could crash the whole system!
Files are all there in first post. Just follow each setup step carefully. Try out the building-blocks approach as suggested in 4(b) of previous post
, and see how you go.
P.S. @francois please define bnsdr