[04:23] <JanC> hm, I'm just reading http://blog.bofh.it/debian/id_267 and I'm wondering if something like the 'new_id' parameter works for other subsystem than USB too (e.g. PCI) ?
[04:34] <infinity> JanC: I do believe that it works for PCI too, yes.
[04:35] <JanC> that might be great to easily fix some "new hardware" problems
[04:36] <JanC> or at least try to
[04:39] <JanC> if I understand correctly, it might be possible to solve quite some hardware problems without needing a new kernel...
[04:40] <JanC> and thus it shouldn't be too difficult to provide support for new hardware after the release
[07:42] <schiggy> hi @all
[07:44] <schiggy> i hope you can help me. i search the file, which starts the first user process. i must work with the 2.6.21.1 kernel
[13:21] <jpoirier_> Hello
[13:21] <jpoirier_> I have a question about compiling Ubuntu Jaunty
[13:22] <jpoirier_> I am trying to build kernel version 2.6.28-12.43 but for some reason the version shows up as 2.6.28.9 when the build completes
[13:24] <jpoirier_> Where does the kernel version get set?
[13:46] <jpoirier_> Never mind, I see the version in the Makefile here.
[13:48] <jpoirier_> Which I can change to match 2.6.28-12 of course, but really I think that given that I did checkout of a specific tag "Ubuntu-2.6.28-12.43", the Makefile should already have been updated to match the tag.
[13:48] <jpoirier_> I think what I am building is the correct source for 2.6.28-12, given that git log shows the latest commit.
[13:49] <jpoirier_> Thank you..
[14:51] <echooo6> can someone point me to a howto for including a new kernel recompile + cd remaster?
[14:52] <echooo6> I think I'm missing aufs, which refuses to build 
=== mcasadevall is now known as NCommander
=== pace_t_zulu is now known as pace_t_zulu|nash
=== pace_t_zulu|nash is now known as pace_t_zulu
[22:40] <franczena_> Hello