In looking at the various ftp sites i see way to much variation on how
the file tree sets up. How does one pull a single set of rpms from
a site without having to walk the entire tree?? (by hand, for an example
the rpms needed to use audacity)
Also in doing Rsync i would think that if more than a "dozen rpms" are
going to be changed during an update The Drakes should drop a
.FireStorm file into the tree and if an Rsync sees that file present it
should abort with the message "Fire Storm in file tree update aborted"
then you don't waste 3 gigabytes of bandwidth just to do the same again
(and again and again and..).
Please note sometimes one needs rpms to fix a broken install (due to
driver issues or bad kernel rpms or..)
- Re: [Cooker] question on ftp sites Robert L Martin
- Re: [Cooker] question on ftp sites Greg Meyer
- Re: [Cooker] question on ftp sites Levi Ramsey
- Re: [Cooker] question on ftp sites Jesse Wagner
- Re: [Cooker] question on ftp sites Buchan Milne
- [Cooker] Clearing out old Bugs? Neal Pitts
- Re: [Cooker] Clearing out old Bugs? John Keller
- Re: [Cooker] Clearing out old Bu... Neal Pitts
- Re: [Cooker] question on ftp sites Dale Huckeby
