The Linux kernel, how it is developed, and how we stay sane doing it
voicerepublic.com
voicerepublic.com
I tried to search youtube, but no luck so far. If anyone has a better recording, please share.
Edit: Since it seems there are no slides anyway and others are having problems with the site, if it doesn't work in your browser, you can try http://voicerepublic.com/vrmedia/982-clean.m4a with a media player, vlc works for me. still doesn't change a thing about the quality of the recording though.
All talks have unique URLs, so when you click the link from HN, you shouldn't find yourself at another talk. If you can reproduce that problem, I would be very interested in a detailed bug report, though.
However, we have multiple talks on Openstack[1], if you were interested(;
is the URL I get, and that isn't Greg speaking
The talk at the URL is about something at CERN for me in both browsers. Its an interesting talk, but I don't think its what I'm supposed to be listening too... although maybe thats the joke and this is how they stay sane developing the kernel.
Everything says "Linux kernel" but I get the Openstack talk. Which, well, I'm interested in what they do at CERN too but is definitely not the kernel.
Also big thanks to all reporters in this thread! Your constructive help is much appreciated!
Original Post:
My deepest apologies. The conference LinuxTag (where both talks had been held) had a couple of unannounced room changes. These two talks must have been switched in that fashion.
LinuxTag had six tracks[1], we are currently searching for the right talk to correct this mess!
That's a little snarky. Chrome on Linux doesn't have automatic updating and I tend to forget to update. Here's a mirror:
http://webcache.googleusercontent.com/search?q=cache:LWDDNOb...
Sorry for coming off snarky. We develop and run VR using Debian Stable which ships Chromium 33 right now.
We are a very small team building voicerepublic.com and did launch just last week. To offer a perfect experience, we only allow browsers that we actually could test. Whence the team grows, we certainly will test and support more browser versions.
After about 4000 hits from HN, about 1% of visitors have a browser older than:
* Chrome/Chromium 30
* Safari 7
* Firefox 24
* IE 10
Instead, you should prompt the user and warn them that their browser has not been tested and is not supported, but they may continue.
(ah, well according to you yes, they are now on 28). But is there a reason it shouldn't work? I mean, I understand not supporting I.E6 but it wasn't that long ago I installed this. Or else time is running together on me.
Just a tip from a user perspective. If you can avoid forced browser upgrades it's a good idea. I generally don't go any further unless I really really want to see the content.
Still, I didn't identify any change would prevent the site from working so I'm just curious. Anyone care to shed some light on this?
Thank you for the feedback. We just launched VR last week and are actively improving it. I will put a volume control in the Backlog(;
I was so annoyed I didn't even listen to the audio and immediately shut down the page.
For instance, if I have Gmail open in the background, there's no reason that adjusting the volume of whatever's in the foreground should also force me to change the volume of incoming chat notifications.