Date: Fri, 18 May 2012 20:54:25 -0700 From: Tim Kientzle <tim@kientzle.com> To: Mel Flynn <rflynn@acsalaska.net> Cc: freebsd-hackers@freebsd.org, Mateusz Guzik <mjguzik@gmail.com>, tzabal@it.teithe.gr Subject: Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion Message-ID: <01A33A03-3068-46E8-958F-500216E4E912@kientzle.com> In-Reply-To: <4FB6620D.8060001@acsalaska.net> References: <20120516003020.82068pr8h9dyqjfw@webmail.teithe.gr> <20120516140033.GB2470@dft-labs.eu> <20120516233744.1314398bowqaykuw@webmail.teithe.gr> <20120517125348.GA26081@dft-labs.eu> <4FB6620D.8060001@acsalaska.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 18, 2012, at 7:51 AM, Mel Flynn wrote: > On 17-5-2012 14:53, Mateusz Guzik wrote: >> On Wed, May 16, 2012 at 11:37:44PM +0300, tzabal@it.teithe.gr wrote: > >>> Nice. What about curl over the HTTPS protocol? >>> >> >> curl would be ok, except it's not in the base system. > > For this reason, it's probably best to use tar(1) to package up multiple > files and implement http put support in libfetch(3). You may also need > to implement 305 Use Proxy support. Depends on where the files are coming from. If you have files on disk, then tar(1) might be a good choice. If you're going to have to construct the files, then you can maybe avoid writing them to disk by using libarchive(3) directly instead of going through the tar command-line interface. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01A33A03-3068-46E8-958F-500216E4E912>