FYI, this yum deltarpm support, is based on that same deltarpm package that is made by suse. This suse package can create new rpms from drpm + (either ondisk files, or old rpm). Either way, a new rpm is created, then installed. Never does it replace files directly. Not sure why this would be bad security wise Hey, why do emails appear to come from the sender, not the FI list. I always hit reply, and end up replying to the original author only! :) <div>On 1/13/07, Toshio Kuratomi <<a href="mailto:a.badger@gmail.com">a.badger@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Sat, 2007-01-13 at 19:42 +0200, Ahmed Kamal wrote: > not sure I understand your question, but they way things should go is, > the client downloads the drpm, client side code combines client side > files from older rpm + the drpm into a new rpm. Then that new rpm is > installed. The required bandwidth should drop to 20%, the numbers need > some testing ofcourse, but I can imagine such savings. > SuSE did a lot of work on distributing the files as less than a whole rpm. Their original tool works as you say, with an "rpm patch file" that combines with an rpm on the client's system which is then installed. The newer tool that they were pushing a couple years ago was also able to upgrade files on the filesystem rather than going through the intermediate step of creating an rpm. I consider this method to be less desirable from a security standpoint than the first. -Toshio </blockquote></div>