[02:38] <zul> heylo
[04:55] <makx> infinity: around?
[04:56] <infinity> makx: Not really.  It's 3am, and I was supposed to be in bed ages ago. :)
[04:56] <makx> ok, i'll send you mail.
[04:57] <makx> checking if ubuntu is also affected by heavily guess yes..
[05:00] <infinity> afftected by..?
[05:02] <infinity> makx: ?
[05:03] <makx> switched to boot
[05:05] <makx> sorry you are not in #ubuntu-boot
[05:05] <makx> 16:59 <makx> ok posting to the more relevant channel
[05:05] <makx> 17:01 <makx> initramfs-tools gets minor wrong if you boot with root=341
[05:05] <makx> 17:02 <makx> simple testcase on http://paste.debian.net/5276
[05:05] <makx> 17:02 <makx> minor is the actual code, minorreal is what should be done
[05:05] <makx> easy to fix just wanted to let you know.
[05:07] <infinity> Ahh, cool.  I'm going to be doing some bugfixing next week, so I'll get that in, do some merging of other fixes from Debian, and fix up a bunch of longstanding bugs we both have.
[05:08] <infinity> Should I add myself to Uploaders in the Debian package and just start uploading fixes there, or do you prefer to play release manager in Debian and have me push patches to you?
[05:08] <makx> add yourself to the uploaders is fine with me.
[05:09] <makx> i'll merge your stuff in my tree.
[05:09] <makx> i tried to split up the long modules line in seperate files
[05:09] <infinity> Kay.  Some of the fixes I need to do are pretty painful bugs, so I wanted to get them in both dists when I upload.
[05:10] <makx> but the downside was a real longer initramfs generation
[05:10] <infinity> Files with one module per line, filtered through "sort"?
[05:10] <infinity> I can fix that so it's just as fast.
[05:10] <makx> so i just aligned them to 80 chars inside hook-functions
[05:10] <infinity> I'll fix that in my next upload.
[05:12] <infinity> Yeah, that'll be a messy change, and one I may never do, just because it's messy.
[05:12] <makx> well we never released with in debian ;)
[05:12] <infinity> Besides, the binary /is/ mkinitramfs.  Who cares if it's not intuitively placed on the filesystem? :)
[05:12] <infinity> Yeah, maybe I'll move it in Debian, let the bugs shake out, then merge the move in dapper+1 when I think it's safe. :)
[05:12] <makx> no the binary is update-initramfs the ones othere should use
[05:13] <infinity> No way I'm moving the conf directory this late in the game for dapper.
[05:13] <makx> sure i waited for that :)
[05:13] <infinity> makx: Well, that's true now.  We used to use mkinitramfs raw. :)
[05:13] <infinity> We only started using update-initramfs in dapper.
[05:14] <makx> ok, we only started since not long too
[05:15] <makx> have a good sleep :)
[05:15] <infinity> Danke.
[05:15] <infinity> Later.
[05:22] <dilinger> aw
[05:24] <infinity> dilinger: Okay, okay.  I'll do it.
[07:39] <doko> BenC: any news about the default for not spinning down the hard disks? at least in the server kernel
[07:46] <BenC> doko: forgot about it
[07:46] <BenC> I'll look into it over the weekend
[07:49] <doko> thanks
[08:58] <h36sa> hey guys, I'm looking to distupgrade to dapper from breezy, but right now I am running a modified kernel (just downloaded the image from somewhere) to fix the p4-clockmod workaround in breezy (my cpu is misdetected and is limited to 2ghz+.. not the best for a laptop). I'm wondering if the dapper kernel has this fixed or not
[09:03] <overridden> helleuw
[09:05] <overridden> is this the channel to report that every kernel above 2.6.12 freezes a random minutes after boot ?
[09:11] <cjb> It might be, if one of the developers is around, but a full bug report would be even better.
[09:11] <cjb> (If you also run another OS, you should try that to check it isn't your hardware that's failing/overheating/something.)
[09:11] <overridden> Ok, but how do I get to some debug ingo ?
[09:12] <overridden> *info
[09:12] <overridden> because of the freeze, I dont get info
[09:12] <cjb> If you fill out the bug report, someone will tell you what they need.
[09:13] <overridden> ok