Contest: Default PCDM Theme

Calling all creative PC-BSD users! The developers at PC-BSD would like your help in designing a brand new theme for the PCDM login manager. The winning entry will see their own customized skin as the default theme in the next official release of PC-BSD! In addition, we would like to present the winner and runner-ups with these awesome prizes:

1st Prize: A PC-BSD Isotope T-shirt, PC-BSD stickers, BSD wristbands, plus misc FreeBSD swag items.(Total ARV: $40)

Honorable mentions: PC-BSD schwag package (ARV: $15)

Contest start:11:00am PST on June 19th, 2013

Contest end:11:00am PST on July 8th, 2013

Please submit your entries in an email to the PC-BSD developers mailing list[1] along with your email contact information. The format we require is a *.tar.gz archive containing all the image files as well as *.theme file. Please title the subject heading “Entry for PCDM Theme Contest� in order to be considered.

A sample theme can be found on the PC-BSD GitHub account[2], with additional information about PCDM theming available on the PC-BSD wiki[3]. General icons should be 128 pixels square or smaller, with background images large enough to be automatically scaled/trimmed to the appropriate screen resolution where possible (for sample purposes consider 1024×768 to be the smallest supported screen resolution).

Have fun everyone, and good luck!

Standard disclaimers apply. iXsystems and PC-BSD team members are encouraged to submit entries, but will not be eligible for prizes. Void where prohibited.

[1] http://lists.pcbsd.org/mailman/listinfo/dev
[2] https://github.com/pcbsd/pcbsd/tree/master/src-qt4/PCDM/themes
[3] http://wiki.pcbsd.org/index.php/PCDM

BSDCan Trip Report: Florian Smeets

The next trip report is from Florian Smeets. He writes:

I arrived in Ottawa on Tuesday afternoon. In the evening I went to the Royal Oak to meet other fellow developers.

Wednesday was the first day of the Devsummit. The day started with a presentation about the FreeBSD.org security incident and about how Netflix is using FreeBSD for their CDN.

In the afternoon I attended the ports session where we saw presentations about features that were added to the ports tree in the last year and also about stuff that people will be working on during the next year.

On Thursday I went to the VM I/O Concurrency and Virtualization sessions. In the first session, we talked about all the performance work that is currently happening that should be in the 10.0 release. In the second session, there was a lot of talk about Bhyve and we saw a demo of Linux running in Bhyve.

In the evening I attended the Vendor summit, which I find quite interesting, as you get a picture of the needs of other people and also what they are working on.

Friday was the first day of the actual conference. After talks about dtrace and git, I attended a talk about benchmarking FreeBSD. One of the slides even showed results I posted some time ago.

The next talk I saw was switching from Linux to FreeBSD, which gave some interesting insights into the differences of the two systems from someone else. Which was quite interesting as I've been working for a Linux based company for the last 6 months.

After the FreeBSD Birth to Death talk, I attended the Mozilla on OpenBSD talk. Landry, the OpenBSD Mozilla maintainer, is an OpenBSD and Mozilla committer. He helped us in committing a lot of our patches upstream. At the social event in the evening, I finally had a chance to meet him in person. We talked for a long time and made plans. Now, 4 weeks after the conference, we have a mozilla-central buildbot running in a Bhyve, so we will be informed about breakages automatically from now on. This will be a huge help, as we can try to fix those kind of things before the releases and fix them with our own patches in the ports tree.

On the last day of the conference I attended a talk about using Puppet to manage FreeBSD and about the FreeBSD.org cluster refit. In the afternoon I didn't attend talks, but took the time and sat down with some other developers to discuss future projects.

As my flight was only leaving on Sunday evening, I went into town with a couple of other developers to do some sightseeing. In the evening, the long journey back home started and an eventful and exhaustive week came to an end.

Creating PBI’s with EasyPBI

Ken Moore has an article in the June issue of BSD Magazine which describes how to easily generate PBIs from existing FreeBSD ports. The article is on pages 26-30 and this issue of the magazine can be downloaded for free from here.

Working on Bluetooth Coexistence

I decided to bite the bullet and start hacking on bluetooth coexistence on these Atheros NICs. It's a bit of a rabbit hole.

I'll write up a bit more documentation on this when I'm not overly tired, but the general overview is pretty simple: "It's all done in software."

The bluetooth and wifi stacks need to speak to each other to know when is an appropriate time to prefer wifi traffic or bluetooth traffic. When pairing, bluetooth should be preferred. When scanning, associating, authenticating and rekeying, wifi should be preferred. When different profiles are active (eg A2DP audio), the bluetooth traffic should be periodically given preference so the A2DP frames can go out reliably. This has to be controlled in software.

So to make this work well on FreeBSD, I'll have to teach the wifi and bluetooth stacks to interface with each other somehow so this can be synchronised.

I have basic (static) coexistence working with the AR9285+AR3011 combo NIC. That's now in -HEAD.

I'm working on basic (static) coexistence on the AR9485+AR3012 combo NIC, however my NIC has an older BT part which requires quite a bit of dancing to make work. I'll have to teach ath3kfw how to load the config and firmware image for the required NIC. It's going to take some time but it'll be worth it.

I was hoping that FreeBSD would have basic A2DP support but it currently doesn't. I'd love to see that happen as it'd simplify a lot of my development/testing - as I can then do audio stream testing both playing and recording audio, then stream that over wifi.

Oh well. Another day of hacking!

So long, and thanks for all the fish!

After 18 months at Qualcomm Atheros, I decided I needed a bit of a change.

This is what I sent out to the open source community:

Hi all,

This Friday will be my last day at Qualcomm Atheros. I've enjoyed working with the extremely bright and driven engineers and designers that make the wireless chips and SoCs that people everywhere take for granted. I've achieved a bunch of goals both with their internal product development and open source. But now it's time to move onto different things.

I'd especially like to thank Luis Rodriguez for introducing me to the QCA folk and helping me get access to the Atheros open source project, as well as the follow-up discussions that led to me being hired. The open source wireless community has been driving innovation in a lot of areas for a number of years. I'd like to hope that I've had a small, positive effect on that. I wish you all the best of luck in pushing forward and continuing to innovate.

Now, I'm still NDA-enabled and I quite like hacking on this wireless stuff so I won't be quitting hacking on things. I will just have other things on my mind.

Good luck to you all!

Now, this generated a flurry of private emails asking me what happened and where I'm going to.

So, the summary - I accepted a job at Netflix, as part of their OpenConnect CDN team.

They've built a world-wide CDN using FreeBSD and they're looking to continue growing and improving it. They've committed to improving FreeBSD's network, storage and VM layer to facilitate moving tens of gigabits of Netflix video traffic per server. And, they're going to open source the bulk of it. They realise that the best benefit from open source comes from working with open source - and that's exactly what they've done. They've contributed back their improvements and fixes.

I've enjoyed my time at Qualcomm Atheros. The people are brilliant, the hardware is excellent and it was a great learning experience. I got to experience what it was like working at a silicon company during chip design, validation and bring-up - both the good and the bad bits. But when it came down to it, I couldn't contribute to and improve the process in any meaningful way. I was one engineer in a very large, diverse organisation - and like large organisations, things move slowly.

So, I hope to continue to maintain close ties with the hardware and software people at Qualcomm Atheros. I hope to continue hacking on the FreeBSD wireless stack in my spare time, as I have been to date. I wish I could've contributed more positively to their evolving hardware and software strategy. But there's only so much an engineer in an established company can do, and that engineer wasn't going to be me.

FreeBSD 8.4-RELEASE Available

FreeBSD  8.4-RELEASE is now available. Please be sure to check the Release Notes (detailed version) and Release Errata before installation for any late-breaking news and/or issues with 8.4. More information about FreeBSD releases can be found on the Release Information page.

Conversion to new options: done

It took a year but at least it is done! Huge thanks to all people involved in the new Option Framework.

So now what we have:

  • A consisten way to set options in make.conf (OPTIONS_SET, OPTIONS_UNSET, ${UNIQUENAME}_SET, ${UNIQUENAME}_UNSET )
  • 0-1 options
  • only 1 options
  • 0 or N options
  • 1 or N options
  • helpers to sanely create slaves (OPTIONS_SLAVE aand OPTIONS_EXCLUDE)

What still needs to be done:

  • Stop popping the dialog only for global options
  • Fix the very old bug about OPTIONSFILE name dansing (PKGNAMEPREFIX changing)
  • Convert NOPORTEXAMPLES, NOPORTDOCS and WITHOUT_NLS to options.

With the previous done, my 2 main priorities for FreeBSD now are:

  • Get pkg 1.1.0 released
  • Introduce the next big and long awaited change to the ports tree: stage directory

BSDCan Trip Report: Warren Block

The next trip report is from Warren Block. He writes:

A two-day developer summit was held before BSDCan itself began.  On Wednesday, there were presentations to the whole group on the security incident last year and how NetFlix uses FreeBSD.  It's interesting to note that somewhere around 20% of North American internet traffic is served by NetFlix systems running FreeBSD.  Individual group meetings began in the afternoon, and I attended the UEFI boot session.  Beyond the topic of UEFI booting and FreeBSD, I found some people to help with creating a man page for gptboot.

That night, we had our first session of the "doc lounge" proposed last year by Dru Lavigne.  The concept was for a doc sprint, but also to be available for users and other developers who either wanted to see a specific correction to the documentation, or to have an introduction to start working on documentation themselves.

Thursday morning, I met with Peter N. M. Hansteen, author of the famous "Book of PF".  Several years ago, he submitted a patch to include a PF tutorial in the Handbook.  He mentioned it to me at BSDCan last year, and this year, we completed integrating it.  It will be committed to the Handbook after the upcoming release of FreeBSD 8.4.

That afternoon, the doc developer summit was held.  The biggest issue was ongoing work on a new print version of the Handbook.  Dru has done a tremendous amount of good work on this so far.  There is more to be done, and technical and social issues to address.  On other subjects, we also talked about important FreeBSD killer features that have not been well-documented or publicized in the Handbook or other documentation. Also mentioned were the need for more doc people and more translators.

On Friday and Saturday, the BSDCan presentations were given.  As usual, there is always a conflict with scheduling where multiple talks are held at the same time. Fortunately, the slides are online.  Even better, the good people of FOSSLC again recorded the talks, and they will be showing up on Youtube.  If you could not attend in person, this is the next best thing.

All the talks were good, but two in particular stood out for me.  The first was Allan Jude's talk on using Puppet to manage multiple FreeBSD systems.  Even if you are a fan of CFEngine or Chef, it's worth seeing for comparison.  If you aren't already using one of these automation systems, it's a great introduction.

The second talk that really made an impression was a summary by Justin Gibbs of what the FreeBSD Foundation has planned for the future.  Besides the phenomenal success of their fundraising in 2012, he detailed plans for the Foundation's expansion with more staff and more projects.  One point that I had not really understood before was what they meant when they said individual donations were needed, no matter the amount.  A few large corporate donors are fine if it's just about the total amount of money needed.  But the number of individual donors is also a way to tell hardware vendors the relative popularity of FreeBSD.  That's why every FreeBSD user should donate to the Foundation, even if it's just $5. Half-joking, I stood near the Foundation table and reminded people walking past without the "I donated" sticker that they should donate. To my surprise, every single person I talked to actually did stop and donate.  There was actually a sort of traffic jam at one point.  The Efika ARM notebook running FreeBSD--another Foundation-funded project--also attracted a crowd to the table.

The Friday night doc lounge was canceled due to a scheduling conflict with a BSDCan social event, but we had another session on Saturday night.  For me, that was the most successful.  Again, we had people with no experience with FreeBSD documentation show up.  The level of interest and the dedication shown was very interesting.  Clearly, people care, and we need to make it as easy as possible to contribute new content or patches for existing documents.

In many ways, I found the doc lounge to be the most valuable and educational part of the trip.  Trying to help a new person get the doc tools installed and working showed places where there is room for improvement, and there is always important feedback when working with people trying to use those tools for the first time.  There is also the "what's that?" factor, where one user sees another using a tool or technique they had not known about before.

BSDCan 2013 was hectic and packed full of content.  As always, it was well worth the trip.

People and groups to thank:

The FreeBSD Foundation, sponsors of my attendance at BSDCan this year.

Dan Langille, the person responsible for BSDCan.

Peter N. M. Hansteen, for his patience and help in getting the PF tutorial section for the Handbook completed.

FOSSLC  and Andrew Ross for their recording of presentations so those who could not be present have a chance to see them.

And finally, thanks to all the great people who attended.

BSDCan Trip Report: Renato Botelho

The next trip report is from Renato Botelho. He writes:

I arrived Tuesday morning after a long trip with 2 more friends, Luiz Otavio O Souza and André Oliveira. While waiting the bus, we met John Hixson, from ixSystems. After checking into the Residence, I used the afternoon to walk a bit in the city. At the end of the afternoon I went to the Royal Oak and met Diane Bruce and other developers.

The first session Wednesday morning was about the security incident from last year. It was really nice to hear what happened and what has been done since then to improve security on the FreeBSD cluster. After that, it was time for Netflix and FreeBSD, by Scott Long. It was really interesting to hear what is happening with FreeBSD inside Netflix.

In the afternoon, I attended the Ports and Packages working group. There were a lot of topics about what is being and what needs to be done to improve ports. The hot topic was cross-building ports.

In the evening I attended the Vendor Summit. It was another interesting series of discussions as there is a bunch of things to be done. The devsummit was really different from last time I attended in 2010, and it seems to be much more organized and productive the way it is now.

On Thursday morning I attended the Beyond Buildworld working group. The subject of cross-building was in evidence again, with other topics and volunteers for making the tasks. Other interesting topics included Crochet and Source Tinderbox Redport, besides other tools to make a developer's life easier and help to keep the stability of the code.

In the afternoon I atteded the ATF working group. I hardly knew anything about ATF until this talk and started to play a bit with it after that. It's a great testing framework and it would be really useful to have it integrated into src.

Friday was the BSDCan start day and the opening session was amazing. Eric Allman shared his experiences of having his own company based on an opensource product. It was a great time to hear from such an experienced guy and learn a lot about his experiences.

I also attended Kirk Mckusick's talk about Security in the FreeBSD Kernel and the talk about NetBSD-based Radar, and after that MCLinker, which seems to be a promising project to replace current linker.

Day #2 started with Bob Beck telling about buffer cache in OpenBSD, and the future of wireless networking, by Adrian Chadd. After lunch, Henning Brauer told us the history of trouble they experienced with overcomplicated checksum on OpenBSD network stack. After that I was presented to newbus by Warner Losh, one of the best speakers of the conference in my opinion.

It was really good but was close to the end. The Closing Session was as cool as it was the last time I attended and we had a great time.

Sadly I didn't go to tourist things on Sunday since I was not feeling that good. I spent Sunday doing not much and left for the airport in the afternoon for the long trip back home. It was a great time as I met other ports committers and had nice talks. I also met other pfSense developers and users, and my coworkers from BSD Perimeter.

I would like to thank the FreeBSD Foundation and BSD Perimeter for sponsoring this trip and making it possible to meet other developers and hear such high-level talks. Hope to see you all in Ottawa next year.

Foundation at SouthEast LinuxFest

SouthEast LinuxFest will be held at the Blake Hotel in Charlotte, North Carolina from Friday June 7 to Sunday June 9. Registration is required, but free, for this event.

There will be a FreeBSD booth in the Expo area, all three days. We will be giving out PC-BSD DVDs, FreeNAS CDs, and other cool swag, as well as accepting donations to the FreeBSD Foundation.

PC-BSD at SouthEast LinuxFest

SouthEast LinuxFest will be held at the Blake Hotel in Charlotte, North Carolina from Friday June 7 to Sunday June 9. Registration is required, but free, for this event.

There will be a BSD booth in the Expo area, all three days. Several members of the PC-BSD team will be giving out PC-BSD DVDs, FreeNAS CDs, and other cool swag, as well as accepting donations to the FreeBSD Foundation.

Kris Moore will present “Automating the deployment of FreeBSD & PC-BSD systems” at 16:00 on June 7. Dru Lavigne will present “A Sneak Peek at FreeNAS 9.1″ at 14:45 on June 8. Ken Moore will present “Getting Started with PC-BSD” at 14:45 on June 9.

The BSDA certification exam will be held at 11:00 on June 9. The cost for the exam is $75.

rodrigc 2013-05-30 07:53:27

For previous post, see Setting up a VM for doing GSoC work

Since Neeraj is using a Windows 7 machine, where FreeBSD is in a VM, I asked him to install the following programs under Windows:

In the FreeBSD VM, I asked him to add this to /etc/rc.conf :

sshd_enable=”YES”

and this to /etc/ssh/sshd_config :

PermitRootLogin yes

This allowed him to (1) log into the VM via SSH using Putty, (2) transfer some files to and from the VM using WinSCP

Configuring sshd is documented in the FreeBSD Handbook here:
http://www.freebsd.org/doc/en/books/handbook/openssh.html
http://www.freebsd.org/doc/en/books/handbook/configtuning-rcd.html

 

One point of confusion for Neeraj was that some config files are located in /usr/local/etc (for certain ports),but the certain config files are under /etc.  For example, the  sshd config files are under /etc/ssh/  (and not /usr/local/etc/ssh/).  Depending on the Linux distribution, on Linux there is generally no /usr/local directory, and all config files go under /etc.  This is one slight point of confusion for users moving from Linux to FreeBSD.  Nothing too difficult, but something worth noting.

bsdtalk227 – ZFS with Matt Ahrens

Interview with Matt Ahrens from Delphix during BSDCan 2013.  Matt was part of the original team that developed ZFS.

File info: 32Min, 15MB.

Ogg link: http://cis01.uma.edu/~wbackman/bsdtalk/bsdtalk227.ogg

Craig Rodrigues, FreeBSD developer 2013-05-24 20:40:41

On June 17, 2013, Stanford University is offering a free online course on coursera:

https://www.coursera.org/course/startup

 

===============================================================================================

About the Course

Spiritual sequel to Peter Thiel’s CS183 course on startups. Bridges the gap between academic computer science and production software engineering. Fast-paced introduction to key tools and techniques (command line, dotfiles, text editor, distributed version control, debugging, testing, documentation, reading code, deployments), featuring guest appearances by senior engineers from successful startups and large-scale academic projects. Over the course of the class, students will build a command line application, expose it as a web service, and then link other students’ applications and services together to build an HTML5 mobile app. General principles are illustrated through modern Javascript and the latest web technologies, including Node, Backbone, Coffeescript, Bootstrap, Git, and Github.
===============================================================================================
The notes for this course are also available here:  http://startup.stanford.edu/
This course is quite interesting, because it really shows how a lot of startups in Silicon Valley are rapidly bootstrapped at a technology level.  These days a lot of these startups use Linux out of the box, and don’t even bother looking at the alternatives.
Obviously, I like FreeBSD a lot, and think FreeBSD is a great platform for startups.
What are the things that we as a FreeBSD community can do to improve the FreeBSD platform,
and make it a no-brainer decision for startups to use it for their new companies?
The startups of today become the billion dollar companies of tomorrow, so it is important that FreeBSD is a part
of that.
I’d love to hear the ideas of people in the FreeBSD community for how to make FreeBSD better for startups!