[18:01] <xivulon> evand ping
[18:24] <xivulon> cjwatson ping
[18:26] <evand> xivulon: pong
[18:29] <xivulon> hey evand couple of quick questions
[18:29] <xivulon> a few users reported errors with m-a and wubi
[18:30] <xivulon> Unable to open the registry file at '/mnt/migrationassistant/WINDOWS/system32/config/software'
[18:30] <xivulon> I think the path case is the issue
[18:30] <xivulon> but that make the installer stop
[18:31] <xivulon> how can I go around that for the time being? Do you know the relevant file on top of your head?
[18:31] <xivulon> Issue 2: I'd like to silence the dialog that complains about security.ubuntu.com being unreachable, can I preseed that?
[18:32] <cjwatson> apt-setup/security_host
[18:32] <xivulon> thanks chwatson
[18:32] <cjwatson> actually, no
[18:33] <cjwatson> apt-setup/service-failed
[18:33] <cjwatson> except that's in hardy :)
[18:33] <cjwatson> use apt-setup/security-updates-failed in gutsy
[18:33] <xivulon> what value do I preseed to make it skip?
[18:33] <evand> xivulon: that error alone will not make the installer stop.  I'd need to see the full logs.
[18:34] <cjwatson> anything, it just needs to be seen. the empty string would be traditional
[18:34] <cjwatson> d-i apt-setup/security-updates-failed note
[18:34] <xivulon> evand see http://ubuntuforums.org/showpost.php?p=3638010&postcount=101
[18:35] <xivulon> don't have the syslog but can ask the user that reported that
[18:35] <xivulon> m-a works well for me
[18:36] <xivulon> Issue 3 is that when ntfsresize fails, users are shown posix_filesystem_required
[18:37] <xivulon> that message is quite confusing, since what they should see is "Please run chkdsk /r from windows and reboot again into Ubuntu"
[18:37] <xivulon> ntfsresize --info
[18:39] <xivulon> Issue 4: not sure how to get right the grub-drive, the drive order of what is seen by grub4dos and what is seen from linux is not always the same
[18:39] <xivulon> that's it!!
[18:42] <xivulon> cjwatson, can I show a custom message in ubiquity from autopartition-loop and force ubiquity to quit?
[18:42] <xivulon> that is to go around #3
[18:44] <CompBrain> So, Two Questions: 1) is there a python parser or generator for preseed configuration files 2) Is there a python parser for template files, and whats the easiest way to amass a collection of them
[18:45] <evand> CompBrain: I am unaware of any tool to generate preseed files.  The closest thing is the kickstart GUI to generate kickstart files that the installer can handle.
[18:45] <CompBrain> Ok, I borrowed pseudo code from debconf-(get,set)-selections and build a module for that purpose
[18:47] <evand> please keep in mind that debconf doesn't have to be flat files forever, so it's best to interface directly with the existing tools so that you're well insulated from any changes to the underlying database format.
[18:47] <CompBrain> I'm mostly interested here in building a preseed configuration widget
[18:52] <xivulon> evand is the msg above enough for you?
[18:53] <evand> xivulon: what message?
[18:57] <xivulon> http://ubuntuforums.org/showpost.php?p=3638010&postcount=101
[18:58] <evand> xivulon: http://ubuntuforums.org/showpost.php?p=3655006&postcount=113
[18:59] <xivulon> good
[19:00] <xivulon> By the way more than a failure I guess the installer would just sit there when in automatic-mode
[19:01] <xivulon> If I wanted to display a message box in Ubiquity, from within autopartition-loop what would be a good route?
[19:01] <xivulon> db_input?
[19:02] <xivulon> And to make ubiquity exit?
[19:06] <cjwatson> CompBrain: you'd have to develop it
[19:06] <cjwatson> I doubt it would be in python; that's the implementation language of neither debconf nor cdebconf
[19:06] <cjwatson> you can use debconf-copydb to help
[19:30] <xivulon> cjwatson I notice that grub-installer uses an existing device.map, how is that generated?
[19:31] <cjwatson> xivulon: grub-install (from grub) generates it
[19:32] <xivulon> having a look
[19:36] <xivulon> hmm cannot find where that is actually generated
[19:36] <xivulon> I can see line 413: echo "(hd0) $bootremovable" > "$device_map"
[19:36] <xivulon> but that does not look like it...
[19:40] <cjwatson> in turn, it gets grub to do it
[19:40] <cjwatson>     $grub_shell --batch $no_floppy --device-map=$device_map <<EOF >$log_file
[19:40] <cjwatson> quit
[19:43] <xivulon> hmm that's similar to what I am using
[19:43] <xivulon> echo quit | grub --batch --device-map=/boot/grub/device.map
[19:43] <xivulon> but I end up with disks that do not match what is seen by grub4dos (at least accordingly to user reports)
[19:44] <xivulon> hd0 as seen by grub4dos becomes hd1 by the time I generate device.map
[19:45] <xivulon> nothing I can reproduce on my machines...
[19:46] <xivulon> am I missing anything?
[22:06] <foonux> Hello all.  I've got a quetion related to installing ubuntu(specifically the gutsy ubuntustudio.iso) From a usb-stick.  I've got syslinux working and I'm using the initrd and vmlinuz from hd-media however the iso scan is failing to load the iso file on the stick.  I set the ramdisk_size to 850MB in my syslinux.cfg,
[22:06] <foonux> Anyone had any issues getting this to work before?
[22:08] <foonux> I'm wondering if there the debian-installer doesn't recognize the non-standard ubuntu iso?  Or mayber the iso should be renamed in 8.3 (dos) format...
[22:08] <foonux> Yes, the file name does in .iso. :)
[22:18] <foonux> Hello?
[22:21] <xivulon> what iso are you using? is it the alternate one?
[22:22] <foonux> Yeah, the alternate dvd iso.
[22:22] <foonux> It seems to be the only one to download too...
[22:23] <foonux> Its the ubuntustudio-7.10-alternate-i386.iso
[22:24] <xivulon> don't remember on top of my head what checks are done, one sec
[22:24] <foonux> Cool, thanks!
[22:27] <xivulon> it checks for .disk/info (which should be there)
[22:28] <xivulon> and for the existence of /cdrom/dists/$distlink/Release
[22:28] <foonux> I can mount the .iso real quick and double check...just a sec
[22:29] <foonux> Release is there.
[22:29] <xivulon> allowed distros are determined by the line "for distlink in stable testing unstable ; do" in iso-scan.postinst
[22:29] <foonux> What did you mean by .disk/info though?
[22:30] <xivulon> it's a file that should be in the folder .disk within the cdrom
[22:31] <xivulon> but the reason might be a mismatch between the distlink in the initrd and the one in /cdrom/dists
[22:31] <foonux> Top-level of the iso contains the folders: dists, doc, install, isolinux, pics, pool, pressed and the files: cdromupgrade, md5sum.txt README.diskdefines
[22:32] <xivulon> ls -al
[22:32] <xivulon> cat .disk/info
[22:33] <foonux> Yeah, .disk is there. cat output: Ubuntu-Studio 7.10 "Gutsy Gibbon" - Release i386 (20071015)
[22:34] <xivulon> as mentioned, you have to check distlink in iso-scan.postinst vs folders in /cdrom/dists
[22:34] <foonux> Anyway I can make a modified initrd to match the distlink in the cdrom?  Or vice-versa?
[22:34] <foonux> Ah
[22:35] <xivulon> probably easier to do an initrd... certainly much faster
[22:36] <foonux> Ok.  How do I check the distlink in the initrd?
[22:36] <foonux> Find the source I'm guessing?
[22:38] <xivulon> or extract the initrd files
[22:40] <foonux> Is there a quick way to do that from the term?
[22:41] <foonux> Konqueror doesn't seem to want to do it.
[22:45] <xivulon> gunzip -c -9 $initrd | cpio -i -d -H newc --no-absolute-filenames
[22:47] <foonux> Ok, cpio gave me two Operation not permitted errors for dev/console and dev/null but that shouldn't matter.
[22:57] <foonux> I can't seem to find iso-scan.postinst
[23:01] <xivulon> If my memory serves me well should be in /var/cache/lib/apt/
[23:04] <foonux> Heh, /var/cache/anna contains nothing, but /var/lib/dpkg/info has it.
[23:04] <xivulon> yeah that's the one
[23:04] <foonux> I'm lessing it now.
[23:05] <foonux> under the register_cd() funtion I've found the following line:
[23:05] <foonux> for distlink in stable testing unstable ; do
[23:06] <foonux> relfile=/cdrom/dists/$distlink/Release
[23:06] <foonux> if [ --e $relfile ] &&
[23:07] <foonux> egrep -q 'Architectures:.* '$(udpkg --print-architecture)'( |$)' $relfile
[23:07] <foonux> then
[23:17] <foonux> Comment are as follows:
[23:17] <foonux>         # Make sure that the iso is usable for the architecture. If so,
[23:17] <foonux>         # set the suite and codename to the suite/codename that is on the CD.
[23:17] <foonux>         # This assumes that there will be no more than one distribution on
[23:17] <foonux>         # the CD, and that one of the testing, stable, or unstable links will
[23:17] <foonux>         # point to it. Since the CDs currently have many links, parse the
[23:17] <foonux>         # Release file to get the actual suite name to use.
[23:23] <foonux> Well from what I can tell they match.
[23:25] <foonux> It seems that it reads the Release file on the cdrom to see and then Checks to make sure the given iso file matches the Ubuntu release naming convention.
[23:26] <foonux> And the Release file reports it as simply a standard release of Ubuntu 7.10.
[23:26] <foonux> Since that's the case I'm going to shorten the name of the iso file on the usb-stick and see if that turns the trick.
[23:27] <foonux> Thanks for all the help!!