You'd be crazy to miss FSOSS 2014 Thu, Oct 2. 2014
The Free Software and Open Source Symposium (FSOSS) 2014 is around the corner, and it's shaping up to be the best in years. We have well over 30 talks spread over 2 days, covering just about every corner of open source from new and upcoming technologies through business models. We have a keynote from my colleague David Humphrey examining the implications of Heartbleed, as well as keynotes from Chris Aniszczyk (Twitter) and Bob Young (Lulu/Red Hat/TiCats). There are speakers from Canada, the US, Hungary, the UK, Cuba, and India, representing open source communities, academia, entrepreneurs, startups, and companies such as Mozilla, Cisco, AMD, Red Hat, and Rackspace.
Until October 10, registration for this event is just $40 (or, for students and faculty of any school, $20), which includes access to all of the keynotes, talks, and workshops, two lunches, a wine/beer/soft drink reception, a t-shirt, and swag.
Full details can be found at fsoss.ca -- see you October 23/24!
Acessing the armv6hl Koji Buildsystem Mon, Feb 11. 2013
The Seneca CDOT OSTEP project has been operating a Koji buildsystem for the Fedora ARM Secondary Architecture project, for the armv5tel and armv7hl architectures. These architectures are going to shift to the Fedora Phoenix datacentre Real Soon Now(tm) now that true enterprise-grade ARM server hardware is available.The armv5tel architecture has hit EOL with Fedora 18, but will be supported with updates until a month after the release of Fedora 20; we (the Fedora ARM group) is working towards Primary Architecture status for armv7hl by the Fedora 20 release.
We (Seneca OSTEP) are now also operating a second Koji buildsystem, for the armv6hl architecture. This architecture is really of interest only for the Pidora project for the Raspberry Pi at this point in time. This buildsystem is accessible on the web at http://koji.pidora.ca
However, to access the armv6hl buildsystem using the Koji command-line tools, using a Fedora client certificate, a bit of a dance is required. This post outlines the steps...
1. Set up your Fedora packager environment, if you haven't already done so.
2. Add this text to the end of your ~/.fedora-server-ca.cert file:
3. Place this text in /etc/koji/armv6-config:
;configuration for koji cli tool
;url of XMLRPC server
server = http://japan.proximity.on.ca/kojihub
;url of web interface
weburl = http://japan.proximity.on.ca/koji
;url of package download site
topurl = http://japan.proximity.on.ca/
;configuration for SSL athentication
cert = ~/.fedora.cert
;certificate of the CA that issued the client certificate
ca = ~/.fedora-upload-ca.cert
;certificate of the CA that issued the HTTP server certificate
serverca = ~/.fedora-server-ca.cert</code>
4. Execute this command: sudo ln -s /usr/bin/arm-koji /usr/local/bin/armv6-koji
5. Ping someone on the OSTEP team via irc://irc.freenode.net/seneca to add your FAS2 username to the Koji instance.
6. Profit! -- You should now be able to issue commands to the armv6hl koji system by typing: armv6-koji command
In due course, we'll get this configured as a standard secondary-arch Koji instance, and you can skip the steps above -- but in the meantime, if you want to help with the armv6hl effort, those are the steps required.
SBR600 - Winter 2013 Mon, Dec 17. 2012
The SBR600 Software Build & Release course provides a unique opportunity for Seneca CTY students to get involved with an open source community. However, for the Winter 2013 semester, we opened the course late, so not very many students are aware that it's available.
If you're interested in taking SBR600, or know anyone who is: SBR600 is available for the Winter 2013 semester through SIRIS.
The OSTEP Team Wed, Nov 28. 2012
The Open Source Technology for Emerging Platforms (OSTEP) team at Seneca consists of four research assistants who work with me on projects related to enabling Linux and related open source technologies on emerging ARM systems - specifically working with the Fedora ARM Secondary Architecture initiative.
Since I haven't had an opportunity to introduce the team recently, I thought I would (very briefly) do so here.
Andrew Green (agreene) is our repo guru and is currently composing and testing the Raspberry Pi Fedora Remix 18. He is working part time with the OSTEP team while completing the CTY program at Seneca.
Dmitry Kozunov (DarthJava) works full-time with OSTEP. His main area of responsibility is the Fedora ARM buildsystem infrastructure, which means he wrestles heroically on a daily basis with unstable dev boards and multi-terabyte backups. He will be continuing his studies in the Seneca IFS program in January.
Jon Chiappetta (fossjon) is working full-time on a zippy armv6hl optimized build for the Raspberry Pi, and simultaneously experimenting with alternate approaches to koji queueing for secondary architectures. Jon is a graduate of our IFS program and our resident Python pro.
Jordan Cwang (frojoe) is a graduate of the Seneca CTY program and works part-time with the OSTEP team on infrastructure issues. He's is our bcfg2 whiz and is currently working on several infrastructure projects including improving security with measures such as two-factor authentication.
Interested in buying a Raspberry Pi? Mon, Sep 10. 2012
Measuring the Raspberry Pi's Current Consumption Wed, Jun 20. 2012
The Raspberry Pi has a micro-USB jack for power input. This can be used with any recent mobile phone adapter. If you use a two-part adapter, with a plug-in AC-DC converter and a USB A to micro-USB A cable, it's easy to measure the current drawn by the Pi.
To do this, you'll need a USB A male to USB A female extension cord and an ammeter or multimeter with a 1A or 10A range.
1. Remove the outer insulation in the middle of the USB extension cable. Peel back the shielding (silver braid and/or foil) to one side.
2. Cut the 5V supply wire (usually coloured red).
3. Connect your ammeter or multimeter to the cut 5V line.
4. Insert this cable between your AC-DC converter and the USB cable going to your Raspberry Pi.
So, how much current does the Raspberry Pi draw?
It looks like the Pi can draw anywhere from 250 to 500 mA in normal operation, though I did see smaller values in the early stages of startup. When idle, my Pi draws 320-380 mA; with a basic Logitech keyboard and mouse attached and in use, and with the CPU and GPU fairly active, it comes close to 500 mA.
Update: Powering the Pi from a Laptop
The fact that the Pi's current consumption is reliably under 500 mA means that it is actually safe to power from the USB port of another system. This is convenient for developers on the go: for example, I'm in an air-conditioned library escaping the current Toronto heatwave, and have my Pi connected to the back of my laptop with a micro-USB cable for power and a crossover ethernet cable for data.