[Not this year] Re: FreeBSD in Google Code-In 2012? You can help too!

On Fri, Nov 02, 2012 at 08:13:18PM +, Wojciech A. Koszek wrote: On Tue, Oct 16, 2012 at 10:19:57AM +, Wojciech A. Koszek wrote: (cross-posted message; please keep discussion on freebsd-hackers@) Hello, Last year FreeBSD qualified for Google Code-In 2011 event--contest

Re: FreeBSD in Google Code-In 2012? You can help too!

On Tue, Oct 16, 2012 at 10:19:57AM +, Wojciech A. Koszek wrote: (cross-posted message; please keep discussion on freebsd-hackers@) Hello, Last year FreeBSD qualified for Google Code-In 2011 event--contest for youngest open-source hackers in 13-17yr age range: http://www.google

Re: FreeBSD in Google Code-In 2012? You can help too!

around things which people consider attractive. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any

Re: FreeBSD in Google Code-In 2012? You can help too!

On Tue, Oct 16, 2012 at 10:19:57AM +, Wojciech A. Koszek wrote: (cross-posted message; please keep discussion on freebsd-hackers@) Hello, Last year FreeBSD qualified for Google Code-In 2011 event--contest for youngest open-source hackers in 13-17yr age range: http://www.google

Re: FreeBSD in Google Code-In 2012? You can help too!

or bad coding project. :/ I updated the Wiki with Sample ideas section: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-stable@freebsd.org mailing list http

FreeBSD in Google Code-In 2012? You can help too!

/2012Tasks I plan to send out next e-mail if there's any progress on this project. Help will be appreciated. Thanks, -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-stable@freebsd.org mailing list http

Re: FreeBSD in Google Code-In 2012? You can help too!

On Tue, Oct 16, 2012 at 10:19:57AM +, Wojciech A. Koszek wrote: (cross-posted message; please keep discussion on freebsd-hackers@) Hello, Last year FreeBSD qualified for Google Code-In 2011 event--contest for youngest open-source hackers in 13-17yr age range: http://www.google

Google Code-In 2011 is over; 56 tasks got completed for FreeBSD!

of the FreeBSD involvement in promotion of the Open Source software. Thank you. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable

The FreeBSD Project in the Google Code-In 2011 contest

. Include '[GCIN]' header when posting to freebsd-hackers@ In case of potential task candidates, ideas and suggestions, feel free to contact me. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-stable

Re: (Possible fix for sbp(4)) Re: Comment out sbp driver from GENERIC

Dnia 18-10-2011 o 14:12:56 Alberto Villa avi...@freebsd.org napisał(a): On Tue, Oct 18, 2011 at 1:48 PM, Wojciech A. Koszek wkos...@freebsd.czest.pl wrote: Commenting a driver out is almost always a bad idea and should be done as a last step. Well, few weeks prior to -RELEASE can

(Possible fix for sbp(4)) Re: Comment out sbp driver from GENERIC

://lists.freebsd.org/pipermail/freebsd-current/2007-December/081411.html And please let me know if a fix explained in this thread works for you. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-stable

Re: bug in mdconfig -l (does not list all devices)

related with proper mdconfig(8) interface to -CURRENT, but I'm not able to test them on RELENG_6 right now. Please let me know if anyone is willing to test such changes on RELENG_6. -- Wojciech A. Koszek [EMAIL PROTECTED] http://FreeBSD.czest.pl/dunstan

Re: bug in mdconfig -l (does not list all devices)

correctly on current but fails on stable. On RELENG_6, we still use old mdconfig(8) API and this limitation is known. In -CURRENT, such limitation doesn't exist. -- Wojciech A. Koszek [EMAIL PROTECTED] http://FreeBSD.czest.pl/dunstan/ ___ freebsd-stable

Re: Possible memory leak?

): vmstat -m vmstat -z -- Wojciech A. Koszek [EMAIL PROTECTED] http://FreeBSD.czest.pl/dunstan/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL

Re: Reverting to 6.2-RELEASE

a configuration of a running kernel via sysctl (kern.conftxt for now) and via config(8) form the kernel file. Hopefully this work will get more review soon. Thanks, -- Wojciech A. Koszek [EMAIL PROTECTED] http://FreeBSD.czest.pl/dunstan/ ___ freebsd-stable

Re: Reverting to 6.2-RELEASE

On Mon, Mar 19, 2007 at 02:32:48PM -, Steven Hartland wrote: - Original Message - From: Wojciech A. Koszek [EMAIL PROTECTED] I did some work in this area, as several system administrators I've met also seem to have problem with kernel configuration recovery. In my case I came

Re: Reverting to 6.2-RELEASE

On Mon, Mar 19, 2007 at 10:23:53PM +0800, LI Xin wrote: Wojciech A. Koszek wrote: [..] I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we should add it to DEFAULTS some day... I did some work in this area, as several system administrators I've met also seem to have

Re: Mounting OpenBSD partitions

to read files from Solaris label. [1] Solaris fsck(8) wasn't able to handle such serious brokeness, even after specifying alternative, backup superblock. -- Wojciech A. Koszek [EMAIL PROTECTED] http://FreeBSD.czest.pl/dunstan/ ___ freebsd-stable

Re: Crash with FreeBSD 6.1 STABLE of today

likely to happen, or facilitates it happening on non-SMP systems. Wojciech Koszek has recently been looking into devfs-related races that trigger for pty's, which could be relevant to what you're seeing, so I've CC'd him. Robert, Thanks for CCing me, even with wrong address ;-) I'll look

Re: missing dependency - crypto.ko to zlib.ko

:47 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SERVER i386 Last cvsup'd at 2006-03-03 04:07:00 EST. Please let me know if there is a better way to fix this. Any input would be appreciated. Will be fixed ASAP. Thanks ! -- Wojciech A. Koszek [EMAIL PROTECTED] http