[07:21] What is the most direct way to obtain the source corresponding to the currently running Ubuntu generic kernel? [07:21] apt-get is pulling linux-meta and the results are a newerr version that doesn't support the same crypto [07:28] Hi [08:19] one (N,BFTL), the easiest is probabally to look at the tags in the git repositories at kernel.ubuntu.com/ubuntu/ubuntu-.git [09:18] Hi [09:19] WHat is the most direct way to obtain the kernel source? [09:20] For a spcific version. Matching what is currently run on the system used. [09:28] one, the easiest is probabally to look at the tags in the git repositories at kernel.ubuntu.com/ubuntu/ubuntu-.git [09:28] one, or pull-lp-source -d linux [09:34] apw: looking at the versions [09:34] what are 'tags' I do not want to do any more 'cooldude; lingo [09:35] The version closest to the kern I am looking for just contains a 'metasource' package in place of where the sourcecode is usually located [09:35] apw: Hola [09:36] apw: A friend of mine is complaining that the Ubuntu repos are pretty slow - are there alternatives? [09:37] lag: mirrors? [09:37] amitk: Looking here now: https://wiki.ubuntu.com/Mirrors [09:38] amitk: Now here: https://launchpad.net/ubuntu/+archivemirrors [09:40] Why is the sourcecode hidden? [09:40] lag: http://askubuntu.com/questions/39922/how-do-you-select-the-fastest-mirror-from-the-command-line [09:41] lag: though the installer should select the best mirror [09:42] amitk: "It's coming down faster now" :) [09:42] heh [09:43] Why is the sourcecode hidden? [09:45] one: https://wiki.ubuntu.com/Kernel/SourceCode [09:49] one the source code is not hidden, it is either in our git repo or in the source package for the linux-image-* package that contains your kernels [09:51] one, i assume you are looking at the meta-package package such as "linux-image-generic" which comes from a different source, and is part of the mechanism which lets you have a "current" and "previous" kernels [09:52] a very special feature of the kernel packages [09:54] as amitk says that wiki page has all the details on how to obtain it easily [09:56] apw no looking at the git repo [09:57] apw no, looking at the git repo and the source tree includes linux-meta that just has a few text files [09:57] apw: Where is the actual sourcecode? [09:57] in the right git repo [09:57] which release are you on [09:57] one: read the fine manual: https://wiki.ubuntu.com/Kernel/SourceCode [09:58] ie which kernel version range are you looking for, and i'll find you the right link [09:58] git clone git://kernel.ubuntu.com/ubuntu/ubuntu-.git [09:58] so that one yes? [09:58] which did you substitute in [09:58] quantal [09:58] http://kernel.ubuntu.com/git?p=apw/ubuntu-quantal-meta.git;a=summary [09:58] you [09:59] no that is substituting in quantal-meta, that is not substituting in quantal [09:59] and that is something from my directory not from the ubuntu one [09:59] git://kernel.ubuntu.com/ubuntu/ubuntu-quantal.git [10:00] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git;a=summary [10:00] that one is the gitweb you wanted [10:00] I do not want to install git [10:00] I just want the sourcecode [10:01] not download and install more trash [10:01] apt-get source linux-image-$(uname -r) [10:01] is how to get the source [10:01] if you arn't using git, as it says on that wiki [10:01] as it even said first on that wiki [10:02] the https connection doesnt establish [10:03] if the server was accepting http I could have looked [10:03] that i am unable to help you with [10:03] I do not want to install more trash nor do I want to be forced to use a bunch of tracking codes [10:03] apt-get source linux-image-$(uname -r) [10:04] will do what you want then, it will get you the raw source [10:04] which is how you get the source of all and any package in debian based systems [10:04] that looks to be downloading the full source previously I had run apt-get source linux-source or something without the uname [10:05] yep, that gets you the meta package which tracks our releases [10:05] the kernel is special in that regard, so you can have old kernels for emergencies [10:05] then I downloaded the package for the source from some link that was in the meta package [10:05] and it compiled into a version other than what it was labled as [10:07] which link was that [10:08] I do not recall at the moment it was a while back but the package is labled 3.5.0 and the result is 3.5.5 [10:09] that would depend how you build it, if you use the debian rules to build it it will likely come out as 3.5.0-NN style, if you use direct make it might well be 3.5.N [10:09] And it isnt compatible with the crypto running on the current 3.5.0 [10:10] How are the debian rules used to build it? [10:13] to build the full package you would use dpkg-buildpackage -b which will build it for the build machiens architecture [10:13] of course you need th [10:13] the appropriate build infratstructure installed, compilers, kernel-wedge etc etc [10:13] or one could build it in a PPA [10:31] this looks like some more source not sure if its different from what is in the linux-source-3.5.0 [10:31] they are both 3.5.0 [10:31] also theres a linux-meta-3.5.0 [10:32] this scheeming doesn't make sense [10:32] in that way it is hidden [10:32] without sense it becomes dice [10:32] just guess at a random naming schema [10:33] like cracking a bicycle lock just to figure out what it is possibly named [10:36] one, apt-get source gets that actual source package which was uploaded to make the binaries you have, so its not random source [10:37] apw are there any other advantages to using dpkg-b... to build other than detecting the architechure not even to the specifics of cpuinfo [10:37] one, you get a package that is built the same way the archive builds it, it all depends what you are building your kernel for to know whether it matters [10:38] apw: so does it force automation of everything or is there a way to modify the config? [10:38] the configs are builtin and can be modified [10:42] apw: is it also possible to build something for another machine using the dpkg-build... [10:44] apw: the kernel is being rebuilt to cut out the extras and then add some custom modules [10:45] I am planning on some modules which use interactive crypto [10:45] dpkg-buildpackage can build for the architectures the build machine supports only [10:45] unless you use cross-compilers [11:16] well that is where to start, kernel, and start cleaning up this junk [11:16] bunch of junk everywhere on the machine [11:17] any links to a linux compatible braille term [11:17] interactive crypto to check the eyes for trickery [11:18] clean machine [11:19] Iam going to clean up the machine and then use it. [11:19] Can't even be used the popular idea is that folks pay to have machines use them. [11:19] obsurd! [11:21] vanguard robots spying on me [11:21] they play game [11:21] communists [11:22] it seems somewhat surreal [11:22] Did you just open emacs? [11:23] Something just opened emacs [11:23] I know you want me to code. === barq_ is now known as kswit [23:05] you wanna talk about surreal [23:16] hallyn, is that the state after too many beers? [23:18] smb: haha, no, i just looking at the backscroll, with 'one' and 'apw' talking to each other [23:19] smb: all i've had is half of rharper's bottle. where are you? [23:19] i've turned qemu-nbd into an orphan and accidentally downloaded an armhf cloud image, i think i can call tonight a success [23:19] hallyn, In my room but ready to roll any time [23:20] zul hasn't yet shown up on irc [23:20] smb: lobby in 10 misn? [23:20] sounds like at least some err progress (nbd and arm) [23:20] hallyn, ack [23:25] smb: woohoo, container with qcow2 backing store working '\o/ [23:27] yay [23:55] here does dpkg place the kernel after using buildpackage? [23:55] Where does dpkg place the kernel after using buildpackage?