[01:11] <CIA-2> debian-installer: cjwatson * r948 ubuntu/ (4 files in 3 dirs): Move mainline architectures to 2.6.26-5 kernels.
[01:17] <CIA-2> debian-installer: cjwatson * r949 ubuntu/debian/changelog: releasing version 20080522ubuntu8
[01:22] <kirkland> What calls grub-install in the installer?
[01:22] <kirkland> my grep's are not turning up the culprit
[06:34] <persia> kirkland: I'm still very much just learning d-i, but I'd suspect bootloader.sh
[06:39] <kirkland> persia: interesting, okay i'll check it
[06:39] <kirkland> grub-installer looks like what i need
[06:39] <kirkland> i'm also wondering what generates devices.map
[06:39] <persia> Ah.  Sorry.  I misread your question entirely, and substituted "grub-install" with "grub-installer" internally :)
[06:40] <kirkland> ;-)  np
[06:40] <persia> I think devices.map would be generated by grub during the grub-install call.
[06:40] <persia> At least that's the way MIC does it (although MIC should very much *not* be used as an example of how to write an installer)
=== superm1|away is now known as superm1
=== superm1 is now known as superm1|away
=== superm1|away is now known as superm1
=== superm1 is now known as superm1|away