Before too long, Voyager owners (both of them) should once again have full support for their beloved architecture in the mainline kernel.
Is there a reason why those interested in supporting blob-dependent hardware can't make a release that includes those blobs?
<Bryce1> my knoppix install is stuck on 76% <Bryce1> any suggestions?
Could you please explain this in something that does not try to compete with German sentences in length?
This document describes a protocol (IKE) using part of Oakley and part of SKEME in conjunction with ISAKMP to obtain authenticated keying material for use with ISAKMP, and for other security associations such as AH and ESP for the IETF IPSec DOI.
Don't advertise for collaboration, just do it.
With regards to unstable, testing is a step backward.
<sECuRE> forget rapid prototyping, we have rapid bugfixing ;)
I did design a 27 instructions, 4 bit microprocessor with microcode, so I get what firmware is.
NM currently doesn't test candidates technical level, it tests their patience threshold.
If Debian or whoever else have these concernes and want to rip the firmware out, it is one hundred percent their problem to patch things out of the kernel tree they use.
I don't care at all about the argument from that camp.
You know that when you run out of questions, you don't just run out of answers. You run out of hope.
So, what's the process to get rid of the Project Secretary?
Keep away from Wikipedia contributors, they're all maniacs.
<dholbach> Last day of https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in
34 minutes in #ubuntu-classroom on irc.feenode.net
* ScottK hands dholbach an "r".
<Rhonda> Are they fundraising again?
Being the richest man in the cemetery doesn't matter to me... Going to bed at night saying we've done something wonderful... that's what matters to me.
If user space depended on old behavior, we don't change behavior.
Discussions with Jörg produce nice quotes.
I know, I'm being *so* unfair; I'm expecting application programmers to be competent...