Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 May 2012 20:11:03 +0200
From:      Ilya Bakulin <webmaster@kibab.com>
To:        Mel Flynn <rflynn@acsalaska.net>
Cc:        Mateusz Guzik <mjguzik@gmail.com>, tzabal@it.teithe.gr, freebsd-hackers@freebsd.org
Subject:   Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion
Message-ID:  <4FB933B7.5080004@kibab.com>
In-Reply-To: <4FB7FC55.2060905@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> <01A33A03-3068-46E8-958F-500216E4E912@kientzle.com> <4FB7FC55.2060905@acsalaska.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig79C04B0217AF2EF778BC1490
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 19.05.12 22:02, Mel Flynn wrote:
> As I read the original intent is to post crashdumps at a specified
> remote location through rc(8) using an sh(1) script on the next
> reboot. tar seemed appropriate. I'm only mentioning extending
> libfetch(3), because it will be easy for fetch(1) to pick it up, it
> benefits more than just this project and once integrated into fetch(1)
> can be used in said script above. Other than openssh we don't really
> have a good tool in the base system to put local files elsewhere
> securely. Also, if the BUGS section of fetch(3) is out of date, I'm
> happy to be corrected :)=20
I'm not going to make you happy...

=46rom lib/libfetch/http.c:
/*
 * Store a file by HTTP
 */
FILE *
fetchPutHTTP(struct url *URL __unused, const char *flags __unused)
{
        warnx("fetchPutHTTP(): not implemented");
        return (NULL);
}

Adding HTTP PUT support to libfetch would be cool, but I doubt that it's
worth wasting GSoC time for that. Most people use curl for that just
because Google tells them to. On the other hand, SSH is available in
FreeBSD system in 99% of use cases, and it would be quite easy to setup
secure file transfer.

The final decision should however be made by TS.

--=20
Regards,
Ilya Bakulin
http://kibab.com
xmpp://kibab612@jabber.ru



--------------enig79C04B0217AF2EF778BC1490
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+5M74ACgkQo9vlj1oadwhnRACgjZ5XYJiHHbWzhyD/xFBe0W5l
4AQAoKGiV/oSJYrmFdQ6b8NvlJJeR04P
=J8wF
-----END PGP SIGNATURE-----

--------------enig79C04B0217AF2EF778BC1490--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FB933B7.5080004>