Re: FreeBSD + Google Code-In 2014 = we need ideas.
On Mon, Nov 10, 2014 at 01:56:27PM -0700, Alan Somers wrote: On Sun, Nov 9, 2014 at 8:59 PM, Wojciech A. Koszek wkos...@freebsd.org wrote: Hello, BTW, FYI: We didn't make it this year. Judging by the GSoC 2014 Reunion, there is a lot of seasoned Orgs which treat GCIN very seriously, so I think if we plan to participate, it'll be a lot of effort to compete with them Anyway: thanks for the tasks which were submitted. I will put them in Wiki for the reference, Wojciech This year we'd like to participate in the Google Code-In 2014. This is Google Summer of Code, but for younger people: age range is 13--17. If you're one of them, we highly encourage you to apply! ***This year coding tasks are possible, so feel free to add those*** To submit idea which you'd like to see done in GCI, visit: http://bit.ly/FreeBSD_GCIN2014 Regardless of who you are, please use the form to submit ideas. Don't add stuff via Wiki, since this year we'll do direct import of all ideas from Google Forms. To see tasks from previous year that are yet to be copied to Google Forms: https://wiki.freebsd.org/GoogleCodeIn/2014Tasks Thanks to GCI in the previous years, we gained one more FreeBSD developer. We'd like to partcipate this year too. We need: 1) ideas. How about converting various utility functions to use libxo? I think that's within the grasp of a high-schooler. 2) mentors 3) participants. Just like in previous years we'll decide whether we're ready. Deadlines: --- November 12, 2014 - The 10-12 Mentoring organizations are announced for Google Code-in 2014 and the orgs can start entering their tasks into the Google system (the tasks will not be viewable to students until the contest opens on Dec 1). December 1, 2014 17:00 UTC - Google Code-in 2014 contest opens for students January 19, 2015 17:00 UTC - Google Code-in 2014 student work ends --- MORE INFO: [0] http://www.google-melange.com/gci/homepage/google/gci2014 [1] gci-ment...@googlegroups.com [2] https://developers.google.com/open-source/gci/resources/mentor-and-orgadmin-info -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD + Google Code-In 2014 = we need ideas.
On Mon, Nov 10, 2014 at 01:56:27PM -0700, Alan Somers wrote: On Sun, Nov 9, 2014 at 8:59 PM, Wojciech A. Koszek wkos...@freebsd.org wrote: Hello, This year we'd like to participate in the Google Code-In 2014. This is Google Summer of Code, but for younger people: age range is 13--17. If you're one of them, we highly encourage you to apply! ***This year coding tasks are possible, so feel free to add those*** To submit idea which you'd like to see done in GCI, visit: http://bit.ly/FreeBSD_GCIN2014 Regardless of who you are, please use the form to submit ideas. Don't add stuff via Wiki, since this year we'll do direct import of all ideas from Google Forms. To see tasks from previous year that are yet to be copied to Google Forms: https://wiki.freebsd.org/GoogleCodeIn/2014Tasks Thanks to GCI in the previous years, we gained one more FreeBSD developer. We'd like to partcipate this year too. We need: 1) ideas. How about converting various utility functions to use libxo? I think that's within the grasp of a high-schooler. This sounds good. Feel free to add 1 task for each such utility. Wojciech 2) mentors 3) participants. Just like in previous years we'll decide whether we're ready. Deadlines: --- November 12, 2014 - The 10-12 Mentoring organizations are announced for Google Code-in 2014 and the orgs can start entering their tasks into the Google system (the tasks will not be viewable to students until the contest opens on Dec 1). December 1, 2014 17:00 UTC - Google Code-in 2014 contest opens for students January 19, 2015 17:00 UTC - Google Code-in 2014 student work ends --- MORE INFO: [0] http://www.google-melange.com/gci/homepage/google/gci2014 [1] gci-ment...@googlegroups.com [2] https://developers.google.com/open-source/gci/resources/mentor-and-orgadmin-info -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD + Google Code-In 2014 = we need ideas.
Hello, This year we'd like to participate in the Google Code-In 2014. This is Google Summer of Code, but for younger people: age range is 13--17. If you're one of them, we highly encourage you to apply! ***This year coding tasks are possible, so feel free to add those*** To submit idea which you'd like to see done in GCI, visit: http://bit.ly/FreeBSD_GCIN2014 Regardless of who you are, please use the form to submit ideas. Don't add stuff via Wiki, since this year we'll do direct import of all ideas from Google Forms. To see tasks from previous year that are yet to be copied to Google Forms: https://wiki.freebsd.org/GoogleCodeIn/2014Tasks Thanks to GCI in the previous years, we gained one more FreeBSD developer. We'd like to partcipate this year too. We need: 1) ideas. 2) mentors 3) participants. Just like in previous years we'll decide whether we're ready. Deadlines: --- November 12, 2014 - The 10-12 Mentoring organizations are announced for Google Code-in 2014 and the orgs can start entering their tasks into the Google system (the tasks will not be viewable to students until the contest opens on Dec 1). December 1, 2014 17:00 UTC - Google Code-in 2014 contest opens for students January 19, 2015 17:00 UTC - Google Code-in 2014 student work ends --- MORE INFO: [0] http://www.google-melange.com/gci/homepage/google/gci2014 [1] gci-ment...@googlegroups.com [2] https://developers.google.com/open-source/gci/resources/mentor-and-orgadmin-info -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] ASLR, PIE, and segvguard on 11-current and 10-stable
On Fri, May 23, 2014 at 08:35:25PM -0400, Shawn Webb wrote: On May 23, 2014 07:53 PM +, Wojciech A. Koszek wrote: On Wed, May 14, 2014 at 09:58:52AM -0400, Shawn Webb wrote: Hey All, [NOTE: crossposting between freebsd-current@, freebsd-security@, and freebsd-stable@. Please forgive me if crossposting is frowned upon.] Address Space Layout Randomization, or ASLR for short, is an exploit mitigation technology. It helps secure applications against low-level exploits. A popular secure implementation is known as PaX ASLR, which is a third-party patch for Linux. Our implementation is based off of PaX's. Oliver Pinter, Danilo Egea, and I have been working hard to bring more features and robust stability to our ASLR patches. We've done extensive testing on amd64. We'd like to get as many people testing these patches. Given the nature of them, we'd also like as many eyeballs reviewing the code as well. I have a Raspberry Pi and have noticed a few bugs. On ARM (at least, on the RPI), when a parent forks a child, and the child gracefully exits, the parent segfaults with the pc register pointing to 0xc000. That address is always the same, no matter the application. If anyone knows the ARM architecture well, and how FreeBSD ties into it, I'd like a little guidance. I also have a sparc64 box, but I'm having trouble getting a vanilla 11-current system to be stable on it. I ought to file a few PRs. You can find links to the patches below. Patch for 11-current: http://www.crysys.hu/~op/freebsd/patches/20140514091132-freebsd-current-aslr-segvguard-SNAPSHOT.diff Patch for 10-stable: http://www.crysys.hu/~op/freebsd/patches/20140514091132-freebsd-stable-10-aslr-segvguard-SNAPSHOT.diff Shawn I appreciate you working on this. We must have this in FreeBSD. I looked at the patch and I read, but not run it. Comments below. My personal opinion is that kern_pax.c should be compiled in by default. If it adds a lot of size, it'd be better to provide empty stub calls instead of #ifdef'ing everything. But security is very important especially in embeddded systems, so you can imagine you're writing the code that everybody wants and must have enabled for decent level of security. All modern systems run with ASLR turned on. I skipped user-space stuff. I don't think it's necessary in this commit and should be separated. There's a lot of lines of code for status showing. Not sure if we care that much: ASLR is either on or off. Not sure about more granularity. More below. We provide the level of granularity because there are a lot of applications that might exhibit weird behaviors or even crash if we randomize too many bits. We provide sane defaults, but allow each user to choose the level of security versus the level of stability they desire. I'm OK with it being more granular if that's the case. But Linux/MacOSX all have ASLR. If we have programs in ports/ that run on Linux, it's likely they'll just work. If they break, we'll just marked them as broken and to be fixed by the maintainer. Can you run GNOME or KDE with your patch? Or node.js? Node.js uses JIT engine for Javascript. If it works, it's quite likely other will work. kern_jail.c: something looks wrong here. Sounds like you need pr-pax. But I don't understand why you need to have these pr_* values here. It seems unnecessary. I've made it possible to have per-jail ASLR settings. If you have an application that misbehaves, you can jail it with ASLR turned off just for that jail. My BSDCan presentation talks about this. The recording isn't up, yet, though. I don't get it. If there's a program that is broken but you want to run it in jail, our rc.d jail startup script should earn a NOPIE function maybe. I believed PIE/NOPIE is per-process setting on whether to use PIE or not. In this case we'd be able to do: /usr/sbin/jail .. /usr/sbin/nopax program ... In Linux you can do it with personalities. I don't know what it would translate in the FreeBSD to. I guess this could be achieved with simple per-process SYSCTL. nopax would disable ASLR, fork and exec(). I can imagine we won't want ASLR only temporarily, for ports which break and must be fixed. So we probably just need per-process ASLR on/off switch and a wrapper which could be used like: aslr off program So we have right now an addition to mac_bsdextended(4)/ugidfw(8) that does this exact thing. We also plan on adding FS extended attribute support soon, too. Also, per-jail ASLR settings. If you can already do it with MAC layer, it should be enough. Touching jail(8) will require lots of people to review this patch and analyze it in a great details, which typically slows things down a lot. The debug stuff I'd remove too. We could have additional CTR stubs used there, if necessary. Oliver
Re: [CFT] ASLR, PIE, and segvguard on 11-current and 10-stable
On Wed, May 14, 2014 at 09:58:52AM -0400, Shawn Webb wrote: Hey All, [NOTE: crossposting between freebsd-current@, freebsd-security@, and freebsd-stable@. Please forgive me if crossposting is frowned upon.] Address Space Layout Randomization, or ASLR for short, is an exploit mitigation technology. It helps secure applications against low-level exploits. A popular secure implementation is known as PaX ASLR, which is a third-party patch for Linux. Our implementation is based off of PaX's. Oliver Pinter, Danilo Egea, and I have been working hard to bring more features and robust stability to our ASLR patches. We've done extensive testing on amd64. We'd like to get as many people testing these patches. Given the nature of them, we'd also like as many eyeballs reviewing the code as well. I have a Raspberry Pi and have noticed a few bugs. On ARM (at least, on the RPI), when a parent forks a child, and the child gracefully exits, the parent segfaults with the pc register pointing to 0xc000. That address is always the same, no matter the application. If anyone knows the ARM architecture well, and how FreeBSD ties into it, I'd like a little guidance. I also have a sparc64 box, but I'm having trouble getting a vanilla 11-current system to be stable on it. I ought to file a few PRs. You can find links to the patches below. Patch for 11-current: http://www.crysys.hu/~op/freebsd/patches/20140514091132-freebsd-current-aslr-segvguard-SNAPSHOT.diff Patch for 10-stable: http://www.crysys.hu/~op/freebsd/patches/20140514091132-freebsd-stable-10-aslr-segvguard-SNAPSHOT.diff Shawn I appreciate you working on this. We must have this in FreeBSD. I looked at the patch and I read, but not run it. Comments below. My personal opinion is that kern_pax.c should be compiled in by default. If it adds a lot of size, it'd be better to provide empty stub calls instead of #ifdef'ing everything. But security is very important especially in embeddded systems, so you can imagine you're writing the code that everybody wants and must have enabled for decent level of security. All modern systems run with ASLR turned on. I skipped user-space stuff. I don't think it's necessary in this commit and should be separated. There's a lot of lines of code for status showing. Not sure if we care that much: ASLR is either on or off. Not sure about more granularity. More below. Lots of files: You conditionally make .sv_pax_aslr_init method point to something else. I'd assume PAX function _pax_aslr_init32() always gets called and based on whether ASLR is on or not, it does something or not. This will simplify the code a lot, and the difference probably won't be measurable. You have: int a; int b; instead of: int a, b; And you miss spaces around = sometimes. kern_jail.c: something looks wrong here. Sounds like you need pr-pax. But I don't understand why you need to have these pr_* values here. It seems unnecessary. kern_pax.c: I can't quickly tell what locking is using. Some ASSERTS() in pax_ function would help. pax_aslr_active(): I don't see why you need to pass td and proc (I looked at usage: you pass proc only once). I think you could always pass proc to it, with td-td_proc passed typically. kern_pax_*: There's so many SYSCTLs I think people will have problem configuring it. Pick reasonable value for all values and let users change them via SYSCTL_INT (static sysctls) only for debugging. I can imagine we won't want ASLR only temporarily, for ports which break and must be fixed. So we probably just need per-process ASLR on/off switch and a wrapper which could be used like: aslr off program The debug stuff I'd remove too. We could have additional CTR stubs used there, if necessary. segvguard part I didn't understand. Why do you keep a list of programs that failed? There was no ASSERTs, thus it was hard to understand the locking too. I'm trying to understand if randomization is done correctly. Do you think you could post the results? Program: http://pastebin.com/XTRHLhMg Results: cat aslr.c paste gcc aslr.c -o aslr echo 1 2 3 4 5 | xargs -I % -n 1 echo ./aslr aslr.% | sh paste aslr.[12345] | column -t Linux with ASLR: http://pastebin.com/UuwW1JMN MacOSX: http://pastebin.com/kuQnYS4e Thanks, -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD GSOC proposal in 2014
On Wed, Mar 19, 2014 at 01:08:58PM -0400, yan cui wrote: Any comments for this thread? There is only three days left for application. If the proposed idea should not be considered in this year, it should be removed from the GSoC idea list and I will submit a different proposal about the CPU hot plug problem in the FreeBSD kernel. Yan, Please submit all possible ideas you have. We'll carefully look into them and judge which one is the most interesting from the FreeBSD point of view. If you were to stay with locking work, given that the work on pthreads was finished, we'd have to look into whether there's anything else to do in this domain. It still can be valuable to perform some improvements, but somebody else with expertise would have to judge. Thanks, Wojciech 2014-03-18 15:39 GMT-04:00 yan cui ccuiy...@gmail.com: Really? Maybe I can download his code from previous GSoC. Actually, before applying for this idea, I did not scan the projects in previous years and just pick up one which I like. Are there any possibilities to improve on this part (or this idea should not be considered any more)? Yan 2014-03-18 14:26 GMT-04:00 John Baldwin j...@freebsd.org: On Friday, March 14, 2014 3:02:18 am Wojciech A. Koszek wrote: On Thu, Mar 13, 2014 at 09:56:35PM -0400, yan cui wrote: Hi all, I write this mail to make my question clear. I know witness can be used to detect wrong lock order in the kernel. However, can it be used to do lock profiling (what I mean is to report the information such as which locks are most contended and print some related statistics such as calling graph, etc)? In other words, is it enough to finish the task by porting witness to the pthread library? Yan, To my knowledge WITNESS is the only tool for lock order verification. For lock profiling in the FreeBSD kernel there's a KTR subsystem. KTR mechanism is basically like syslog() in the user-space, but for the kernel. KTR subsystem will receive messages from KTR API that is placed in the FreeBSD kernel. Messages get stored on the list of some sort. List can be exported to a file. File you can later analyze. Jeff wrote a Python app which can be used for pre-processing the KTR logs from scheduler and protting them visually. Link: http://svnweb.freebsd.org/base/head/tools/sched/schedgraph.py Instead of porting witness to pthreads, maybe we could evaluate expanding WITNESS to cover kern_umtx? This could prove to be more universal. Wojciech There is a dedicated lock profiler (LOCK_PROFILING) in the kernel. A previous GSoC student from an earlier year has already re-implemented both LOCK_PROFILING and WITNESS for pthreads. -- John Baldwin -- Think big; Dream impossible; Make it happen. -- Think big; Dream impossible; Make it happen. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD GSOC proposal in 2014
On Thu, Mar 13, 2014 at 09:56:35PM -0400, yan cui wrote: Hi all, I write this mail to make my question clear. I know witness can be used to detect wrong lock order in the kernel. However, can it be used to do lock profiling (what I mean is to report the information such as which locks are most contended and print some related statistics such as calling graph, etc)? In other words, is it enough to finish the task by porting witness to the pthread library? Yan, To my knowledge WITNESS is the only tool for lock order verification. For lock profiling in the FreeBSD kernel there's a KTR subsystem. KTR mechanism is basically like syslog() in the user-space, but for the kernel. KTR subsystem will receive messages from KTR API that is placed in the FreeBSD kernel. Messages get stored on the list of some sort. List can be exported to a file. File you can later analyze. Jeff wrote a Python app which can be used for pre-processing the KTR logs from scheduler and protting them visually. Link: http://svnweb.freebsd.org/base/head/tools/sched/schedgraph.py Instead of porting witness to pthreads, maybe we could evaluate expanding WITNESS to cover kern_umtx? This could prove to be more universal. Wojciech 2014-03-13 19:19 GMT-04:00 yan cui ccuiy...@gmail.com: Hi all, I have downloaded the newest FreeBSD-release kernel and scanned some codes. Wonder to know whether the lock order verification and lock profiling tool mentioned in the GSoC idea list is witness? Are there any other tools that needs to look at in the FreeBSD kernel? Thanks, Yan 2014-03-09 15:46 GMT-04:00 yan cui ccuiy...@gmail.com: Hi All, I am a student in Columbia University (Yan Cui), and want to join the FreeBSD GSOC 2014. After scanned the idea list posted online, I think I am interested in the idea titled user space pthread mutex lock contention profiling and lock order verification tools. I have several year experiences in kernel and user locking and believe I can complete the task in time. Currently, I wonder to know, before submitting an application on GSOC home page, do I need to submit some documents in the community (to review?) Best Wishes! Yan -- Think big; Dream impossible; Make it happen. -- Think big; Dream impossible; Make it happen. -- Think big; Dream impossible; Make it happen. ___ soc-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/soc-status To unsubscribe, send any mail to soc-status-unsubscr...@freebsd.org -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD GSOC proposal in 2014
On Fri, Mar 14, 2014 at 01:07:48PM -0400, yan cui wrote: Thanks for the reply! I will get more information about KTR subsystem. You can also look here: http://people.freebsd.org/~kris/scaling/Help_my_system_is_slow.pdf Wojciech 2014-03-14 3:02 GMT-04:00 Wojciech A. Koszek wkos...@freebsd.org: On Thu, Mar 13, 2014 at 09:56:35PM -0400, yan cui wrote: Hi all, I write this mail to make my question clear. I know witness can be used to detect wrong lock order in the kernel. However, can it be used to do lock profiling (what I mean is to report the information such as which locks are most contended and print some related statistics such as calling graph, etc)? In other words, is it enough to finish the task by porting witness to the pthread library? Yan, To my knowledge WITNESS is the only tool for lock order verification. For lock profiling in the FreeBSD kernel there's a KTR subsystem. KTR mechanism is basically like syslog() in the user-space, but for the kernel. KTR subsystem will receive messages from KTR API that is placed in the FreeBSD kernel. Messages get stored on the list of some sort. List can be exported to a file. File you can later analyze. Jeff wrote a Python app which can be used for pre-processing the KTR logs from scheduler and protting them visually. Link: http://svnweb.freebsd.org/base/head/tools/sched/schedgraph.py Instead of porting witness to pthreads, maybe we could evaluate expanding WITNESS to cover kern_umtx? This could prove to be more universal. Wojciech 2014-03-13 19:19 GMT-04:00 yan cui ccuiy...@gmail.com: Hi all, I have downloaded the newest FreeBSD-release kernel and scanned some codes. Wonder to know whether the lock order verification and lock profiling tool mentioned in the GSoC idea list is witness? Are there any other tools that needs to look at in the FreeBSD kernel? Thanks, Yan 2014-03-09 15:46 GMT-04:00 yan cui ccuiy...@gmail.com: Hi All, I am a student in Columbia University (Yan Cui), and want to join the FreeBSD GSOC 2014. After scanned the idea list posted online, I think I am interested in the idea titled user space pthread mutex lock contention profiling and lock order verification tools. I have several year experiences in kernel and user locking and believe I can complete the task in time. Currently, I wonder to know, before submitting an application on GSOC home page, do I need to submit some documents in the community (to review?) Best Wishes! Yan -- Think big; Dream impossible; Make it happen. -- Think big; Dream impossible; Make it happen. -- Think big; Dream impossible; Make it happen. ___ soc-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/soc-status To unsubscribe, send any mail to soc-status-unsubscr...@freebsd.org -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ -- Think big; Dream impossible; Make it happen. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD in GSoC 2014! (mentors wanted)
(cross-posted message; keep discussion on hackers@ only) Hello, So we're in GSOC 2014! Our logo is featured on the main website: http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Everybody can submit ideas through a web form: http://tinyurl.com/FreeBSD-GSOC2014 To help, please add/review/revisit ideas from the FreeBSD Wiki and provide mentorship! https://wiki.freebsd.org/SummerOfCode2014 There are ideas without mentors and ideas with only 1 mentor, as well as tasks which haven't been reviewed.. Help would be appreciated, Thanks, -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
BSD XXI Manifesto
get tied to FreeBSD forums, so that people who help others a lot also get credits. There's a simple 'acceptance' formula: above X credits you get privileges A, B, C within FreeBSD.org. - FreeBSD development can happen entirely online, via BSDCould. Users and developers can edit files via WWW browser and do it the same way. They compile the system and boot it in VM and later, on the real hardware. - Upon making a change, I select 'users who have device X' and users who marked the checkbox 'Willing to test'. They get the VM which I used for testing available and can clone the VM's configuration to their system with 1 click, boot on their hardware and report the results. - Donation process gets modified so that users who care about certain devices a lot can send their hardware to BSDCloud. Hardware would get plugged in the physical hardware and since then regression tests testing this piece of hardware would be run on each commit. Expensive hardware can get linked with BSDCloud so that the machine stays on the owners side. This box is available via VPN just like any other BSDCloud box, and as long as it's available, regression suite is run on it as well. VPN works across firewall and proxies, so specialized platforms behind the corporate walls can also get tested. - On each commit set of benchmarks is run and visualized in the browser. The configuration can include the VM configurations, but can also involve hardware. So before performing a change, developer can see the impact of the change on the system performance. - On each commit set of power benchmarks is run. Couple of real hardware setups have power measurement attached to them and are able to export power profiling information upon commit. This is crucial for cell phones, which FreeBSD can run. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD GSOC 2014: call for ideas!
(cross-posted message; keep discussion on hackers@ only) Hello, We want to participate in GSOC 2014. We need more ideas for students, who can be new to FreeBSD and Open Source. Submit your ideas here: http://tinyurl.com/FreeBSD-GSOC2014 If you make them attractive and clearly explained, there should be a bigger chance of getting them picked by somebody. All submitted ideas upon review will be put here: https://wiki.freebsd.org/SummerOfCode2014 If you have a Wiki access, please just copy the skeleton from the top of this page and use it for your task. Thanks, -- Wojciech A. Koszek wkos...@freebsd.org http://www.koszek.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[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 for youngest open-source hackers in 13-17yr age range: http://www.google-melange.com/gci/homepage/google/gci2012 It was successful. We gained one more FreeBSD developer thanks to that (Isabell Long) We're pondering participating in the contest this year as well. For now we only have 25 ideas. We need at least 100. I felt all members of the FreeBSD community should help, so please submit your own Google Code-In 2012 ideas here: http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 Examples of previously completed tasks: http://wiki.freebsd.org/GoogleCodeIn/2011Tasks Those of you who have Wiki access, please spent 2 more minutes and submit straight to Wiki: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks I plan to send out next e-mail if there's any progress on this project. Help will be appreciated. Hello, This is last call for action. As for now, we won't qualify. I suggest doc@ and ports@ and www@ and src@ teams to try to come up with some ideas and add them to Wiki. Most of the ideas which we have so far are more GSOC-alike. Unless we have at least 80 tasks of the easy/medium type, we'll have to postpone participating in Code-In for next year. Thanks, Hello, We didn't make it this year. I want to thank all the people who submitted (and keep submitting) ideas for our Google Code-In wiki page: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks In total I got 61 ideas over e-mail from the web form (lessons learnt: for GSOC, we should also have a web form) All of them should be on the Wiki now. I suggest we keep collecting good ideas and try to make sure this years GSOC will be successful. On the other note--NetBSD guys are in Google Code-In.. Thanks, -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
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-melange.com/gci/homepage/google/gci2012 It was successful. We gained one more FreeBSD developer thanks to that (Isabell Long) We're pondering participating in the contest this year as well. For now we only have 25 ideas. We need at least 100. I felt all members of the FreeBSD community should help, so please submit your own Google Code-In 2012 ideas here: http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 Examples of previously completed tasks: http://wiki.freebsd.org/GoogleCodeIn/2011Tasks Those of you who have Wiki access, please spent 2 more minutes and submit straight to Wiki: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks I plan to send out next e-mail if there's any progress on this project. Help will be appreciated. Hello, This is last call for action. As for now, we won't qualify. I suggest doc@ and ports@ and www@ and src@ teams to try to come up with some ideas and add them to Wiki. Most of the ideas which we have so far are more GSOC-alike. Unless we have at least 80 tasks of the easy/medium type, we'll have to postpone participating in Code-In for next year. Thanks, -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD in Google Code-In 2012? You can help too!
Dnia 23-10-2012 o 14:05:43 Adrian Chadd adr...@freebsd.org napisał(a): Right, lots of PHP coding. Attractive to a student. Nobody prevents students from serving FreeBSD by writing stuff in attractive, well documented (books, translations) technologies. We just need to craft a task list around things which people consider attractive. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
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-melange.com/gci/homepage/google/gci2012 It was successful. We gained one more FreeBSD developer thanks to that (Isabell Long) We're pondering participating in the contest this year as well. For now we only have 25 ideas. We need at least 100. I felt all members of the FreeBSD community should help, so please submit your own Google Code-In 2012 ideas here: http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 Examples of previously completed tasks: http://wiki.freebsd.org/GoogleCodeIn/2011Tasks Those of you who have Wiki access, please spent 2 more minutes and submit straight to Wiki: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks I plan to send out next e-mail if there's any progress on this project. Help will be appreciated. Update: It looks pretty bad so far. Page: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks Has 38 tasks so far out of which: ~30 would qualify. Consider this e-mail to be the last call for action. Otherwise we'll have to pull back and concentrate our efforts on GSOC instead. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD in Google Code-In 2012? You can help too!
On Mon, Oct 22, 2012 at 11:46:21AM -0700, Adrian Chadd wrote: That wiki site has a distinct lack of help about: * what is required from us; * what the target is (kids, right?) * some examples of good and bad projects. Right now I have absolutely no idea what would constitute a good 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD in Google Code-In 2012? You can help too!
(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-melange.com/gci/homepage/google/gci2012 It was successful. We gained one more FreeBSD developer thanks to that (Isabell Long) We're pondering participating in the contest this year as well. For now we only have 25 ideas. We need at least 100. I felt all members of the FreeBSD community should help, so please submit your own Google Code-In 2012 ideas here: http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 Examples of previously completed tasks: http://wiki.freebsd.org/GoogleCodeIn/2011Tasks Those of you who have Wiki access, please spent 2 more minutes and submit straight to Wiki: http://wiki.freebsd.org/GoogleCodeIn/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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
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-melange.com/gci/homepage/google/gci2012 It was successful. We gained one more FreeBSD developer thanks to that (Isabell Long) We're pondering participating in the contest this year as well. For now we only have 25 ideas. We need at least 100. I felt all members of the FreeBSD community should help, so please submit your own Google Code-In 2012 ideas here: http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 Examples of previously completed tasks: http://wiki.freebsd.org/GoogleCodeIn/2011Tasks Those of you who have Wiki access, please spent 2 more minutes and submit straight to Wiki: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks I plan to send out next e-mail if there's any progress on this project. Help will be appreciated. Hi, (cross-posted message; please keep discussion on freebsd-hackers@) I made a mistake -- the web form didn't have Contributor's name, thus I don't know who of you guys contributed first 9 ideas; e-mail me which ideas are yours, so that your name can be mentioned on Wiki: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks I made slight adjustments to the form to make some fields more precise: http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 Sorry and thanks, -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Enhancing the user experience with tcsh
On czw, lut 09, 2012 at 11:50:06 -0700, Warren Block wrote: On Fri, 10 Feb 2012, Gonzalo Nemmi wrote: ` On Thu, Feb 9, 2012 at 9:52 PM, Eitan Adler li...@eitanadler.com wrote: In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689) there has been some discussion about changing the default cshrc file. In the same line that Wojciech on the PR .cshrc should be updated for modern hardware I always set this ones on /usr/share/skel/dot.cshrc bindkey \e[1~ beginning-of-line #make Home key work; bindkey \e[2~ overwrite-mode #make Ins key work; bindkey \e[3~ delete-char #make Delete key work; bindkey \e[4~ end-of-line #make End key work; Besides that I add an if [ -d $HOME/bin ] and add it to $PATH if it exists, but that has nothing to do with .cshrc should be updated for modern hardware ... it jsut comes in really handy. The question becomes how much is too much? For example, ever since a thread in the forums showed examples of csh/tcsh autocompletion, I've thought the default .cshrc should be stuffed with them. Not for typing reduction so much as self-documenting commands like complete chown'p/1/u/' complete man 'C/*/c/' complete service 'n/*/`service -l`/' 'service' autocompletes with a list of services--it helps the user by showing valid choices. Same with 'chown', it gives a list of users. Then there's this, which probably isn't quite right but has been useful to me (thanks to forum members for help with it): complete make 'n@*@`make -pn | sed -n -E /^[#_.\/[:blank:]]+/d; /=/d; s/[[:blank:]]*:.*//gp;`@' That completes with all lower-case make targets for the current directory. Package operations are easier when the package names autocomplete: complete pkg_delete 'c/-/(i v D n p d f G x X r)/' \ 'n@*@`ls /var/db/pkg`@' complete pkg_info 'c/-/(a b v p q Q c d D f g i I j k K r R m L s o G O x X e E l t V P)/' \ 'n@*@`\ls -1 /var/db/pkg | sed s%/var/db/pkg/%%`@' There's lots more that could be done. Are they appropriate for a stock .cshrc? Maybe now is the time. One of the solutions for this problem would be to have: source /usr/share//csh/autocomplete.csh in .cshrc. I don't know what the shell speed impact might be, however. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Enhancing the user experience with tcsh
On Fri, Feb 10, 2012 at 05:53:09PM +0200, Volodymyr Kostyrko wrote: Eitan Adler wrote: set filec - set history = 100 - set savehist = 100 + set history = 1 + set savehist = 1 Just why not (1 merge)? + set autolist + # Use history to aid expansion + set autoexpand set mail = (/var/mail/$USER) if ( $?tcsh ) then bindkey ^W backward-delete-word bindkey -k up history-search-backward bindkey -k down history-search-forward endif + set prompt = [%n@%m]%c04%# + set promptchars = %# endif I'm fully against changing promptchars, that's pointless. Including more useful data in prompt is good anyway, but why any [] around? I think everything should be just a little more descriptive, like: set prompt = %n@%m %c04%m%# Agreed. Try to make it as short as possible, but not shorter. Remember to check whatever you've done on 80x25 screen. Eatting 25% of the width for the prompt isn't practical. -- Wojciech A. Koszek wkos...@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Google Code-In 2011 is over; 56 tasks got completed for FreeBSD!
Hello, (This is cross-posted message between current@, stable@ and hackers@; for eventual discussion, please use hackers@ mailing list.) I am glad to announce that we've successfully reached the end of Google Code-In 2011 Contest! FreeBSD participated first time, and in my personal opinion GCIN has proven to be a big success. I want to thank all the participants for their time, cooperation and dedication. Here's the list of this years participants: Alex Rucker, Andrey Sinitsyn, Anikan, Astha Sethi, Bebacz, Bharath Mohan, doctorkohaku, Eric Newberry, GarrettF, Isabell Long (issyl0), mpaloski, Violet Lin (n00l3), Nagato Yuki, Nathan, passstab, Reid Anderson, Robin, Roger, Rushil Paul, Thomas Turney, Utkarsh Pant, Zacharias Mitzelos I would like to point out Isabell Long (issyl0) completed 13 tasks for us and holds this years record. Some other numbers... We've had 19 mentors. I send special thanks to those who offered their help in mentoring/administration, since accepting/reviewing/judging tasks has proven to be challenging. We've had 78 tasks published. 56 tasks got completed, leading to ~72% successful completions. 1 task was claimed at the time of hitting the deadline, 10 tasks were claimed, but never finished, thus got reopened. 12 of tasks were never claimed. List of tasks, together with their outcome (uploaded results) are present here: http://www.google-melange.com/gci/org/google/gci2011/freebsd It would be my wish to have the work done in GCIN commited to FreeBSD with: Submitted by: Name email (Google Code-In 2011) header or similar, clearly stating work comes from GCIN 2011. The hardest expectations for mentors was short response time. For students I think it was meeting FreeBSD's standards, however I'm positively surprised by the quality of submitted work. The complaint which I've heard is: Not enough coding tasks. We should fix it next time, since most of the tasks were related with documentation and outreach/promotion. I think GCIN should become an integral part 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
The FreeBSD Project in the Google Code-In 2011 contest
Hello, (cross-posted message; please keep eventual comments on freebsd-hackers@) The FreeBSD project has been accepted to the Google Code-In 2011 contest. http://google-opensource.blogspot.com/2011/11/google-code-in-2011-participating.html We have proposed 50 tasks so far, and more are still coming! This is an event similar to the Google Summer of Code, but is targetted to people in the 13-17 age range. Young people will be working on FreeBSD-related tasks for the next weeks. If you know any potential candidates, feel free to forward this message. Brief summary: T-shirts and possibility of earning some $$$ for participants. The best participants get a chance to see the Google complex in Mountain View, Silicon Valley, California, USA. FreeBSD tasks are here: http://wiki.freebsd.org/GoogleCodeIn/2011 Ideas page can be extended till December, 16th! Contest's home page: http://www.google-melange.com/gci/homepage/google/gci2011 After you create an account, you can acquire tasks which you're interested in (if any of them are left!) Start date: November, 21st (tomorrow) Official communication channels: IRC (EFNet):#freebsd-soc Q/A:wkos...@freebsd.org, jc...@freebsd.org, ead...@freebsd.org wkoszek, jceel, eadler on IRC Mailing list: freebsd-hackers@ Please coordinate communication with your mentor. 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
