1) tar up files
2) encrypt tarball
3) copy encrypted tarball with rcp, ftp, uucp, ...
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@free
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 u
On 19-5-2012 5:54, Tim Kientzle wrote:
>
> 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, tza...@it.teithe.gr wrote:
>>
Nice. What about curl over the HTTPS protocol?
>>>
>>> curl would be ok, exc
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, tza...@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 re
hi,
first of; grats on getting the project. very interesting.
> * Can you recommend a secure way of sending a report from a FreeBSD system
> to the Central Collector machine?
i don't know if the use of a gnu tool would conflict with FreeBSD
politics but you could use tar(1) or an equivalent and G
On 17-5-2012 14:53, Mateusz Guzik wrote:
> On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@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
On Wednesday, May 16, 2012 10:00:33 am Mateusz Guzik wrote:
> Are you going to support textdumps?
>
> I would like to note that some machines have swap space only for
> textdumps, so I think you should support these.
>
> ddb is equiped with a lot of cool commands that show various important
> deb
On Tuesday, May 15, 2012 5:30:20 pm tza...@it.teithe.gr wrote:
> Hello Community,
>
> I have the project "Automated Kernel Crash Reporting System" for this
> GSoC and I would like to discuss my plans about it before starting the
> coding on May 21.
>
> I have created a page in the FreeBSD Wik
On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote:
> Quoting Mateusz Guzik :
>
> >On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@it.teithe.gr wrote:
> >>Hello Community,
> >>
> >>I have the project "Automated Kernel Crash Reporting System" for
> >>this GSoC and I would like to
On Wed, May 16, 2012 at 02:45:24PM +0300, tza...@it.teithe.gr wrote:
> > In this case Apache is a good choice. I would however recommend using
> > www/nginx and PHP in FastCGI mode (FPM option in lang/php5 port). This
> > is a preffered setup for almost all Russian highloaded websites.
> > At the b
Quoting Fernando Apesteguía :
I wonder if it would be good to have a configuration file to specify
the amount of information (the type of, also) the system is going to
send.
Just my 2 cents.
This would be a useful feature.
This
Quoting Mateusz Guzik :
On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@it.teithe.gr wrote:
Hello Community,
I have the project "Automated Kernel Crash Reporting System" for
this GSoC and I would like to discuss my plans about it before
starting the coding on May 21.
Cogratulations. :)
I
On Tue, May 15, 2012 at 11:30 PM, wrote:
> Hello Community,
>
> I have the project "Automated Kernel Crash Reporting System" for this GSoC
> and I would like to discuss my plans about it before starting the coding on
> May 21.
>
> I have created a page in the FreeBSD Wiki
> (http://wiki.freebsd.o
On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@it.teithe.gr wrote:
> Hello Community,
>
> I have the project "Automated Kernel Crash Reporting System" for
> this GSoC and I would like to discuss my plans about it before
> starting the coding on May 21.
>
Cogratulations. :)
> I have created a
I'm interested in the server side of this project, as it's something we've been
working on here. We are developing an internal tool for our own crash reporting
that does analysis of backtraces and provides a pretty accurate synopsis of
what happened. I have a set of heuristics that can find vari
Quoting Ilya Bakulin :
On 15.05.12 23:30, tza...@it.teithe.gr wrote:
* The implementation of the kcrashreporter is planned to be done in
two shell scripts.
Are you really going to name your program "kcrashreporter"? I'd suggest
using a different name since everything matching "^k" is automatic
Quoting Ilya Bakulin :
On 15.05.12 23:30, tza...@it.teithe.gr wrote:
Hello Community,
I have the project "Automated Kernel Crash Reporting System" for this
GSoC and I would like to discuss my plans about it before starting the
coding on May 21.
* Can you recommend a secure way of sending a
Quoting Wojciech Puchar :
sorry if off topic but is today Google needed to do anything and
must supervise everything? Cannot people just write a code as they
always did?
I think that Google only suggests the 21st of May the starting date
for coding. If you start earlier, you will not face
On 15.05.12 23:30, tza...@it.teithe.gr wrote:
> * The implementation of the kcrashreporter is planned to be done in
> two shell scripts.
Are you really going to name your program "kcrashreporter"? I'd suggest
using a different name since everything matching "^k" is automatically
associated with KDE
On 15.05.12 23:30, tza...@it.teithe.gr wrote:
> Hello Community,
>
> I have the project "Automated Kernel Crash Reporting System" for this
> GSoC and I would like to discuss my plans about it before starting the
> coding on May 21.
> * Can you recommend a secure way of sending a report from a Free
sorry if off topic but is today Google needed to do anything and must
supervise everything? Cannot people just write a code as they always did?
I have created a page in the FreeBSD Wiki
(http://wiki.freebsd.org/SummerOfCode2012/AutomatedKernelCrashReportingSystem)
where I describe in details the
21 matches
Mail list logo
