=== gerald is now known as Guest31900 === gerald is now known as Guest85601 === gerald is now known as Guest59084 === gerald is now known as Guest19541 [11:45] hi all [11:45] this question is more kernel module related but im working on ubuntu nonetheless - ive just got a new kernel module working and am wondering what are the ways to get this module activated after reboot. I know about /etc/modules but lets say i dont want to expose the module in this file, what other method is available? [11:49] austin, you really have /etc/modules, an init job which modprobes it, or a udev rule pointing to an alais on it [11:50] ok makes sense apw [12:22] if my module doesn't have dependencies, do i need to run it? [12:22] do i need to run depmod i mean [12:28] austin, depmod tells module init tools things about your module too [13:19] how are the ubuntu kernel_image packages from the repository built? Using make-kpkg on the source package or using make deb-pkg on a kernel tree? [13:24] dpkg-buildpackage -B [16:20] Steven_, yeah alll builds in the archive are essentially schroot builds using dpkg-buildpackage -B or -b deepending on arch === chiluk` is now known as chiluk [19:45] ogasawara: is there a timeline for when we are likely to get 4.2 in wily? [19:46] cyphermox: I want to say sometime next week, we're sorting our fixes for DKMS packages at the moment, but hope to have that resolved early next week [19:56] ogasawara: alright, thanks [20:12] apw: I see, so neither make-kpkg nor make deb-pkg is used? does anyone ever test sourcepackages for the kernel? [20:30] Steven_, dpkg-buiildpackage only builds srcpkgs, as doesnthe archive [20:31] what we upload is a srcpkg, and is in there too [20:55] apw: so who builds the kernels themselves? [20:55] I only ask because I tried building one of these sourcepackages, and I got compile errors [20:55] so I wonder if they were tested at some point [21:00] which package -source? [21:00] linux-image-3.19.0-generic I believe [21:00] I filed a bugreport [21:00] that is an internal thing not the source fpor building [21:00] I tried with 3.16.0, works fine there [21:06] Steven_, whats the bug number [21:08] 1481723 [21:12] they all must build in the appropriate chroots as that is how the binaries get made, no excdeptions [21:14] the package source need to be cleaned after unpack because symlinks cannot be represented [21:14] the build process uses fakeroot debian/rules clean to do this [21:15] but the symlinks are all in one rebuild script [21:18] Steven_, ^^ [21:19] hmm [21:19] I always assumed that kernel image source packages could be built with make-kpkg [21:19] is that not the case then? [21:19] where are these extra steps documented? [21:22] the documented way to buiild a debian source package is dpkg-buildpackage -S and the steps are all in rules [21:23] hmm ok [21:23] this is the third documented way of building kernels I've found [21:25] that is how tjhe archive does it, so it is the most reliabkle [21:25] ok nice, I should try it [21:25] thx === shirgall is now known as Guest40361 === BenC- is now known as BenC