WEBVTT

99:59:59.999 --> 99:59:59.999
Hello, you probably all know what OpenWRT is


99:59:59.999 --> 99:59:59.999
nbd's one of the main developers (Felix Fietkau)

99:59:59.999 --> 99:59:59.999
He's here to tell you about the last 10 years of OpenWRT

99:59:59.999 --> 99:59:59.999
Felix: Yes, thank you.
<i>applause</i>

99:59:59.999 --> 99:59:59.999
The OpenWRT project was started a bit over 10 years ago

99:59:59.999 --> 99:59:59.999
I'd like to take this opportunity to reflect back on

99:59:59.999 --> 99:59:59.999
where the whole project came from

99:59:59.999 --> 99:59:59.999
and how much it has changed and evolved over time,

99:59:59.999 --> 99:59:59.999
based on the progress we have made

99:59:59.999 --> 99:59:59.999
So first I'd like to tell you a bit about what happened in the early days

99:59:59.999 --> 99:59:59.999
As many of you know and as the name OpenWRT
still implies

99:59:59.999 --> 99:59:59.999
it started out pretty much as a firmware for the old WRT54G

99:59:59.999 --> 99:59:59.999
The effort to create this firmware started when

99:59:59.999 --> 99:59:59.999
basically it was discovered that this device, using a Broadcom chip,

99:59:59.999 --> 99:59:59.999
was using Linux as its base operating system

99:59:59.999 --> 99:59:59.999
initially it was a pretty huge GPL violation

99:59:59.999 --> 99:59:59.999
because Linksys didn't release 
any source code for the device

99:59:59.999 --> 99:59:59.999
but that of course didn't stop interested people from trying to hack it by looking into the inner workings of the firmware

99:59:59.999 --> 99:59:59.999
discovering the limitations of it,

99:59:59.999 --> 99:59:59.999
then starting to create a replacement for that firmware

99:59:59.999 --> 99:59:59.999
and this was done in the early days based on the uclibc buildroot

99:59:59.999 --> 99:59:59.999
which was a pretty small and flexible 
environment to quickly bring up code 
for a new target

99:59:59.999 --> 99:59:59.999
and uclibc had the advantage of being much smaller than glibc which I think the initial device used

99:59:59.999 --> 99:59:59.999
it started out by basically taking the Linksys GPL tarball once it was released

99:59:59.999 --> 99:59:59.999
which only happened because many people, many of were members of the Linux kernel community

99:59:59.999 --> 99:59:59.999
actively fought for the source code being released

99:59:59.999 --> 99:59:59.999
and there was a lot of GPL compliance engineering involved in that effort as well