| cooloney | who smb` | 00:21 |
|---|---|---|
| === lag` is now known as lag | ||
| === amitk is now known as amitk-afk | ||
| === amitk-afk is now known as amitk | ||
| _d4vid | when come 3.8.10 to kernel mainline ppa? | 11:40 |
| _d4vid | and 3.9 | 11:41 |
| zequence | apw: So, linux-lowlatency development release maintenance? How does that work? | 11:46 |
| zequence | apw: I suppose I'd prepare the source the same way, but how do I keep track of when to do it? | 11:48 |
| zequence | I'm going to try get some upload rights this cycle. How difficult might that be for linux-lowlatency? I'm focusing on Ubuntu Studio packages first, but I suppose if I were to become a MOTU, I'd be able to upload linux-lowlatency as well | 11:49 |
| zequence | To begin with, I'm going to focus on getting upload right for the Ubuntu Studio package set first, but -lowlatency is seemingly not a part of that group of packagesd | 11:50 |
| hallyn | apw: do you know whether macvlan/macvtap over wifi is supposed to ever work? (been googling for awhile, and looking at the src, all i know is it doesn't in fact work :) | 13:57 |
| === kentb-out is now known as kentb | ||
| DeaconDesperado | greets... | 14:34 |
| DeaconDesperado | I have a kernel bug to report in ubuntu, but it's on a friends comp and he's pretty lost running the reporter on terminal | 14:34 |
| DeaconDesperado | I have output from hardinfo and screencaps of the crash | 14:35 |
| DeaconDesperado | where to submit? | 14:35 |
| dobey | DeaconDesperado: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug | 14:52 |
| === chris234 is now known as RAOF | ||
| DeaconDesperado | dobey: thanks | 15:39 |
| === smb` is now known as smb | ||
| === chuck_ is now known as zul | ||
| melkor | What happened to the -extras in the mainline kernel? | 21:36 |
| melkor | This 3.9 kernel is tiny. | 21:37 |
| Sarvatt | 42MB is the same size as the old image/extras combo, it just got condensed into one | 21:44 |
| === kentb is now known as kentb-ou | ||
| === kentb-ou is now known as kentb-out | ||
| infinity | apw: The 3.9 kernel appears to fail to autoload overlayfs.ko when I schroot for the first time. | 22:53 |
| infinity | apw: Manually modprobing it works fine. | 22:53 |
| apw | infinity, i would expect that to be modprobe'd by mount ? | 23:40 |
| infinity | apw: You'd think, right? | 23:40 |
| apw | infinity, though ... as you are in a chroot (right?) it would not be there to probe | 23:41 |
| infinity | apw: No, this is on bare metal. | 23:41 |
| apw | "autoload overlayfs.ko when I schroot" | 23:41 |
| apw | what does that mean | 23:41 |
| infinity | apw: It means schroot fails and vomits something about overlayfs being an unknown filesystem type. | 23:43 |
| infinity | apw: And when I modprobe the module first, it works fine. | 23:43 |
| * apw is expecting the schroot to use mount, hmmm | 23:43 | |
| infinity | E: 10mount: mount: unknown filesystem type 'overlayfs' | 23:43 |
| infinity | It is. | 23:43 |
| apw | and the same version booted to the raring kernel works i assume | 23:44 |
| infinity | Yep. | 23:44 |
| xnox | infinity: and that's on a nexus or normal desktop?! | 23:44 |
| xnox | ah, never mind me if it works on raring. | 23:44 |
| apw | infinity, very odd ... | 23:51 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!