=== evand_ [n=evand@acmns.pct.edu] has joined #ubuntu-installer === cr3 [n=marc@pdpc/supporter/bronze/cr3] has joined #ubuntu-installer === mpt [n=mpt@121-72-137-28.dsl.telstraclear.net] has joined #ubuntu-installer === evand_ [n=evand@acmns.pct.edu] has joined #ubuntu-installer === philwyett [n=philwyet@bb-87-81-146-45.ukonline.co.uk] has joined #ubuntu-installer === CIA-4 [i=cia@cia.navi.cx] has joined #ubuntu-installer [10:26] linux requiring restarts for a lot of partition changes sucks a lot for the installer eh [10:26] I am just installing ubuntu on a desktop machine, and the installer fails / hangs because of it [10:36] that should only happen if partitions on the relevant disk are mountted [10:36] mounted [10:37] if the partition table is unused then Linux doesn't need to be rebootted [10:37] argh, damn t key [10:57] ubiquity: cjwatson * r1898 ubiquity/ (d-i/manifest debian/changelog): (log message trimmed) [10:57] ubiquity: * Automatic update of included source packages: apt-setup 1:0.16ubuntu4, [10:57] ubiquity: base-installer 1.70ubuntu4, choose-mirror 2.10ubuntu2, clock-setup [10:57] ubiquity: 0.12ubuntu2, debian-installer-utils 1.42ubuntu2, migration-assistant [10:57] ubiquity: 0.4, partman-auto 62ubuntu5, partman-base 100ubuntu4, [10:57] ubiquity: partman-basicfilesystems 51ubuntu2, partman-basicmethods 33ubuntu2, [10:57] ubiquity: partman-efi 11ubuntu2, partman-ext3 45ubuntu2, partman-jfs 20ubuntu2, [11:21] ubiquity: cjwatson * r1899 ubiquity/debian/changelog: releasing version 1.3.22 === mpt [n=mpt@121-72-137-28.dsl.telstraclear.net] has joined #ubuntu-installer === cr3 [n=marc@pdpc/supporter/bronze/cr3] has joined #ubuntu-installer === chrisj [n=tortoise@dhcp-152-78-61-78.ecs.soton.ac.uk] has joined #ubuntu-installer === chrisj [n=tortoise@dhcp-152-78-61-78.ecs.soton.ac.uk] has joined #ubuntu-installer === secureboot [n=lstclair@coriakin.cse.psu.edu] has joined #ubuntu-installer [04:05] when I fakeroot make build_monolithic, the .iso I get has the 2.6.17-10-generic kernel on it, while the modules are for 2.6.17-10-386. [04:05] i have udebs for the 386 modules in localdebs [04:05] now, i can modify the kernel-version in the i386.cfg file to specify generic, and all works well [04:05] however, i'd like the 386 kernel - why might the generic kernel be the one being booted in the iso, instead of 386? [04:17] you'd need to change build/config/i386.cfg or wherever it is - somewhere under build/config anyway [04:17] there's a master kernel version encoded in there [04:19] one more question - with custom udebs - why don't all modules show up in the installer's /lib/modules? I"d like to include more modules than are there, and all the ones built into the kernel that the udebs came from aren't included - why is this, and how do i add them so that d-i knows about them? [04:20] because only Priority: standard and above ones are pulled in automatically [04:20] (above => important, required) [04:21] note that those that aren't in the initrd will not show up in /lib/modules until after the "Retrieving installer components from CD" or similar stage; the initrd is deliberately kept fairly small, only what's needed to boot and fetch more bits [04:21] we don't include everything in udebs because not everything's useful in the installer environment, and there are typically some space constraints [04:25] so more things will show up after a ceratin boot stage? [04:25] neat [04:26] how does one pull in other modules then? [04:26] like the aes module, for instance [04:29] Depends [04:30] if e.g. a partman module needs something, it can depend on it [04:30] alternatively, the anna-install program, if an installer component needs to make a dynamic decision on what to grab [04:36] are all the kernel modules in SOME udeb? For example, is the AES module guaranteed to be in some udeb, or could it just be nowhere? [04:38] assuming of course, i built correctly and AES is in the kernel [04:50] no, it could be nowhere [04:50] for example there's no need for squashfs in the (alternate) installer [04:50] or mouse drivers [04:51] or the bits of X support that are in the kernel (drm) === evand_ [n=evand@acmns.pct.edu] has joined #ubuntu-installer [04:52] cjwatson: so how does one add custom modules to the installer's kernel? [04:53] cjwatson: i haven't seen docs on that around [04:54] could you clarify? [04:55] say i want the installer kernel to have access to the AES module - how would I do such a thing? [04:55] if the AES module isn't in the udebs that are generated when I make a custom kernel, what's the best procedure? [04:55] i have a linux-image deb - should I get the installer to install that, and use its modules? is that the most appropriate approach? [04:56] wah, no [04:56] good - that's ugly [04:56] if you need it in the installer, add it to the appropriate files in debian/d-i/ or wherever it is - somewhere along those lines anyway [04:56] you'll need to add it to package-list and then create the right file to list what modules should be includued [04:56] included [04:57] if you look at the existing files there, it should be relatively straightforward to work out [04:57] the kernel-wedge program has online help (see kernel-wedge(1) for pointers) [04:58] are these files in the kernel source, or in d-i? [04:58] kernel source [04:58] okay - i'll look into it, thanks === cr3 [n=marc@pdpc/supporter/bronze/cr3] has joined #ubuntu-installer [07:43] is there a good way to run post-install scripts? [07:49] i've got like 5 i want to run [07:58] secureboot: /usr/lib/finish-install.d, I believe. [07:58] so /usr/lib/finish-install.d/99yourscript [07:58] would be the last thing to run [07:59] if I understand your question correctly [08:00] evand: sounds like you do [08:00] evand: thanks [08:00] no problem === evand_ [n=evand@acmns.pct.edu] has joined #ubuntu-installer