| === gerald is now known as Guest31900 | ||
| === gerald is now known as Guest85601 | ||
| === gerald is now known as Guest59084 | ||
| === gerald is now known as Guest19541 | ||
| austin | hi all | 11:45 |
|---|---|---|
| austin | 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:45 |
| apw | austin, you really have /etc/modules, an init job which modprobes it, or a udev rule pointing to an alais on it | 11:49 |
| austin | ok makes sense apw | 11:50 |
| austin | if my module doesn't have dependencies, do i need to run it? | 12:22 |
| austin | do i need to run depmod i mean | 12:22 |
| apw | austin, depmod tells module init tools things about your module too | 12:28 |
| Steven_ | 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:19 |
| rtg | dpkg-buildpackage -B | 13:24 |
| apw | Steven_, yeah alll builds in the archive are essentially schroot builds using dpkg-buildpackage -B or -b deepending on arch | 16:20 |
| === chiluk` is now known as chiluk | ||
| cyphermox | ogasawara: is there a timeline for when we are likely to get 4.2 in wily? | 19:45 |
| ogasawara | 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:46 |
| cyphermox | ogasawara: alright, thanks | 19:56 |
| Steven_ | apw: I see, so neither make-kpkg nor make deb-pkg is used? does anyone ever test sourcepackages for the kernel? | 20:12 |
| apw | Steven_, dpkg-buiildpackage only builds srcpkgs, as doesnthe archive | 20:30 |
| apw | what we upload is a srcpkg, and is in there too | 20:31 |
| Steven_ | apw: so who builds the kernels themselves? | 20:55 |
| Steven_ | I only ask because I tried building one of these sourcepackages, and I got compile errors | 20:55 |
| Steven_ | so I wonder if they were tested at some point | 20:55 |
| apw | which package -source? | 21:00 |
| Steven_ | linux-image-3.19.0-generic I believe | 21:00 |
| Steven_ | I filed a bugreport | 21:00 |
| apw | that is an internal thing not the source fpor building | 21:00 |
| Steven_ | I tried with 3.16.0, works fine there | 21:00 |
| apw | Steven_, whats the bug number | 21:06 |
| Steven_ | 1481723 | 21:08 |
| apw | they all must build in the appropriate chroots as that is how the binaries get made, no excdeptions | 21:12 |
| apw | the package source need to be cleaned after unpack because symlinks cannot be represented | 21:14 |
| apw | the build process uses fakeroot debian/rules clean to do this | 21:14 |
| apw | but the symlinks are all in one rebuild script | 21:15 |
| apw | Steven_, ^^ | 21:18 |
| Steven_ | hmm | 21:19 |
| Steven_ | I always assumed that kernel image source packages could be built with make-kpkg | 21:19 |
| Steven_ | is that not the case then? | 21:19 |
| Steven_ | where are these extra steps documented? | 21:19 |
| apw | the documented way to buiild a debian source package is dpkg-buildpackage -S and the steps are all in rules | 21:22 |
| Steven_ | hmm ok | 21:23 |
| Steven_ | this is the third documented way of building kernels I've found | 21:23 |
| apw | that is how tjhe archive does it, so it is the most reliabkle | 21:25 |
| Steven_ | ok nice, I should try it | 21:25 |
| Steven_ | thx | 21:25 |
| === shirgall is now known as Guest40361 | ||
| === BenC- is now known as BenC | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!