=== JayFo is now known as JFo === lamont__ is now known as lamont [03:26] someone remind me how to tell what the actual path to /dev/sdc is..?? === jk-_ is now known as jk- [03:30] lamont: actual path? [03:33] lamont: but 'udevadm info --query=all --name=/dev/sdc' is probably what you're after [03:33] ah, yeah. thanks [03:33] I kinda randomized the drives and needed to figure out where /boot migrated to [03:37] hi [03:39] git clone git://kernel.ubuntu.com/ubuntu/ubuntu-karmic.git [03:40] will this give me the latest version of the ubuntu-kernel or the release-version? [03:41] the kernelGitGuide says I will get "the master tree", but i find it strange to have to give the name of the release to get the latest version === KB1JWQ_ is now known as KB1JWQ [03:54] PrototypeX29A: It will get you the the latest Ubuntu version + any changes that will presumably make it into the next Ubuntu version. [03:55] "latest ubuntu version" means "latest release version"? [03:55] If you clone ubuntu-karmic.git you'll get 2.6.32-9 + any changes since that release. [03:56] You _won't_ get Linus' linux-2.6 tree. [03:56] ok, that is what i intended [03:57] but i don't understand the principle [03:57] what would happen if i replace karmic with jaunty? [03:58] You'd get the kernel that's in Jaunty. If your question is "why isn't there a single git repository with branches for the various releases", then I don't know. [03:58] and how would i get the karmic without the changes? [04:00] It's tagged in the ubuntu-karmic.git repository. [04:01] ok, thanks [04:01] so my next question you have already answered :) [08:13] hi [08:13] i get the source of 9.10 kernel, and found that Ubuntu patches the vanilla kernel. where can i find the information on the patch? [08:13] i want to know which change Ubuntu made to the vanilla kernel [08:16] it seems Ubuntu uses Non-exec patch from OpenWall? [08:17] is it really the Exec-shield patch from Redhat?? [08:18] or if not, what is the difference between Non-exec patch and Exec-shield patch? [08:30] junjun: you can find the ubuntu git trees at https://wiki.ubuntu.com/KernelTeam/KernelGitGuide [08:30] from there you can find all the patches that have been applied [08:33] jjohansen: thanks [10:17] apw: according to marjo's test report, we're still seeing bug 494052 in cert testing [10:17] Malone bug 494052 in linux "bnx2 driver cannot find firmware" [Medium,Fix released] https://launchpad.net/bugs/494052 [10:18] mdz, thanks for the heads up [10:19] apw: I've emailed suggesting he take it up with the kernel team, but figured there was no need to wait for him to wake up to get the ball rolling [10:19] yep [10:51] mdz well the firmware was in the .udeb at least in -8 ... will talk to marjo and get a dmesg [10:56] apw: you folks really ought to have access to pull data like that directly out of the certification db rather than having to ask for it (IMO) [11:02] mdz yeah probabally true === Hellow_ is now known as Hellow [16:10] gah. wtf does it boot to a blinking cursor, instead of grub? [16:11] lamont, lucid? the grub prompt is quite brief [16:11] karmic [16:12] oh, hrmm. is this something that used to work? [16:12] workstation powersupply took out the MB, one drive of the raid array.. I can get to all of the array with karmic-live, but booting from the hard drives is not happening [16:12] of course, when I pulled out all the drives and put them back in as part of getting the MB out, they got a tad bit randomized [16:12] so /boot is RAID1 across /dev/sd{c,d,e}1 [16:13] but UUID should find the right one [16:13] and root is an LVM partition on a RAID6 array across sd{a,b,c,d,e}6 or so [16:14] kind of complex [16:14] and (go me) I had the wrong UUID in fstab, so the root=/dev/MIX/root in menu.lst was saving the day before [16:15] so I guess the real question is: given a running livecd, chrooted into the real root with all the other stuff mounted under that, htf do I get the MBR written on the drive of my choice? [16:15] because I'm thinking all 5 is a good answer.... :-) [16:15] lamont, a grub reconfigure or reinstall? might have to bug cjwatson on that one. [16:16] ok [16:28] looks like maybe grub-install /dev/sd$i [16:28] anyway, afk [20:30] hi, compiling kernel 2.6.33-rc1 with make-kpkg, i get this error http://pastebin.com/d66472fa7 after compiling ... any ideas, what i am doing wrong? [20:33] The UTS Release version in include/linux/version.h [20:33] means the file shows a wrong verioning [20:33] version [20:34] have you checked the file ? [20:34] ghostcube, yes, i can understand the error message, i already did a make mrproper in the source tree, though [20:34] have you looked into the file o.O [20:35] http://pastebin.com/d5c3f079c [20:35] kannst du deutsch [20:35] ja [20:35] gut [20:37] is das en ubuntu kernel source oder normaler kernel.org [20:38] gibt es einen ubuntu kernel v2.6.33-rc1? ist linus/master [20:39] http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33-rc1/ [20:39] warum nimmste nit den o.O [20:39] is weniger action [20:40] o.O? [20:41] hilft das ? [20:42] :) [20:42] oder musste selbst bauen [20:43] ja ... einfache debs nutzen mir nicht wirklich viel [20:43] hmm ok [20:43] bauste patches ein oder wie ? [20:44] weil bei dem kernelcode bug kann ich dir nicht wirklich helfen ich denke die zahl is falsh [20:44] oder du hast da ne alte version [20:44] irgednwo und der greift auf die zu [20:45] ich brauche ein paar dinge im kernel, die nicht unbedingt im ubuntu package aktiviert sind ... [20:45] ich hab das ./debian verzeichnis gelöscht, ein make mrproper gemacht, bzw das include/linux/version.h file gelöscht [20:46] aber der kernel selbst wurde schon gebaut, nur das debian package mag sich nicht erstellen [20:47] hm, ansonsten mach ich mich mal an ein git bisect zu v2.6.32 ... möglicherweise hat sich das format der header files etwas geändert ... [20:53] boah ich bau schon lange nich mehr selbst [20:53] ich bin da keine grosse hilfe [20:54] aber evtl hilfts wenn du wieder auf english wechselst [20:54] weil keiner hier peilt was wir schreiben [20:54] :D [20:55] hm ... i will drop by again tomorrow to have a closer look at this ... === maco_ is now known as maco2