On 8/27/07, <b class="gmail_sendername">Jeremy Katz</b> <<a href="mailto:katzj@redhat.com">katzj@redhat.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 2007-08-24 at 18:09 -0400, Colin Walters wrote:<br>> Ok just to repost - here's the current delta to livecd-creator that I<br>> can't live without.<br>><br>> The first part is answering "Why is my network pegged?" (though does
<br>> anyone know if there's a nice way to use something like Wireshark to<br>> get this info?)<br><br>Don't know of a good way. But like I said with the first time you<br>posted this, I'd much rather just one line per download rather than
<br>multiple. It's more inline with what yum, etc do and it also means less<br>logs to slog through.</blockquote><div><br>Ok, done.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> The second is defaulting to a persistent cache for downloads. This is<br>> not protected against concurrent execution - should we go ahead and<br>> add a --nocache option for those people who have a local fedora
<br>> mirror?<br><br>Given the fact that concurrent operations will cause problems here and<br>there's no real clean-up policy, I still think that a shared cache by<br>default isn't the best idea. I'd be up for a cachedir that can then be
<br>pointed to a shared location if you as the person running know that you<br>want to; but for the general case, I think it's a little too risky as it<br>stands[1]</blockquote><div><br>Ok.<br><br>I have patches in <a href="http://submind.verbum.org/~walters/livecd.git/">
http://submind.verbum.org/~walters/livecd.git/</a><br>(which I rebuilt because I got confused by cherrypicking)<br><br>I also attached the patches manually.<br></div></div>