any actual
code, but an overview of the whole project (specification) and a plan
on how I will work on it.
It can be found in this address:
http://aetos.it.teithe.gr/~tzabal/gsoc/akcrs.html
Any comments are more than welcome.
Thank you in advance,
Tzanetos
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.org/SummerOfCode2012/AutomatedKernelCrashReporting
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
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 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 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
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
7 matches
Mail list logo
