[03:03] <persia> cjwatson: Thanks for the adjustment.  I'll poke when I hear about lpia ABI bumps.
[04:39] <TheMuso> kirkland: Did you get a sponsor for your initramfs-tools fix?
[04:42] <TheMuso> kirkland: Never mind, seems you did.
[08:14] <NCommande> Can anyone answer a few questions on how to run Ubiquity, if possible, as a normal application. I ran ./configure && make, but it only generated site libraries, and didn't spit out anything that was directly executable AFAIK
[08:21] <xivulon> cjwatson in 268123 as mentioned yesterday mount -t ntfs does not work yet (no such device), mount.ntfs is ok
[08:22] <xivulon> I was expecting mount -t ntfs  to call mount.ntfs but it does not seem to be the case
[08:22] <persia> NCommande: Have you looked in ./bin/
[08:23] <evand> NCommande: run debuild in the top directory, then install the deb.  However, note that ubiquity is intended to run on the desktop CD and will break horribly without the presence of /rofs.
[08:24] <xivulon> me goes out
[08:24] <persia> evand: Is it a bug that it fails to complete the install with an empty blacklist set?
[08:25] <persia> I can't imagine a use case for an empty blacklist, but thought the error was odd.
[08:26] <evand> ugh, yeah, if it crashes in the blacklist code then it's my fault and should be filed as such ;)
[08:26] <persia> evand: OK.  I'll pinpoint it and open a bug.  I worked around it by creating the correct manifests, but I'll try to link a branch with a naive fix to the bug.
[08:28] <evand> thanks, much appreciated
[08:38] <NCommande> evand: /rofs?
[08:40] <persia> NCommande: It's one of the mount points on a live image.
[08:40] <persia> Specifically the one of the pristine squashfs, without overlay, etc.
[08:43] <NCommande> Oh I see
[08:43]  * NCommande rights now just wants to make sure the GUI code he wrote works correctly, and then worry about doing a real install
[08:44] <persia> The only way to test it is from the live environment.  I personally test under KVM, as I find that easiest.
[08:44] <persia> Are you building a Xubuntu-specific UI?
[08:44] <NCommande> No, Kubuntu
[08:44] <NCommande> Qt -> KDE4
[08:45] <NCommande> For some reason, I said I'd look into it when I was made a Kubuntu member >.>;
[08:50] <persia> So, test proceudre:
[08:50] <persia> first, boot the latest livecd
[08:50] <persia> next download (from somewhere: maybe ssh to your workstation) the updated ubiquity.
[08:50] <persia> Install the updated version.
[08:51] <persia> run ubiquity (I use ubiquity -d so I can see the logs)
[08:51] <NCommande> Sounds like fun
[08:51] <NCommande> :-P
[08:51]  * NCommande is going to be abusing his PPA it seems
[08:51] <persia> WIth practice, you can get a cycle down to 5-10 minutes.
[08:52] <NCommande> sounds painful :-P
[08:52] <NCommande> Maybe I can setup build-tools and friends on the liveCD
[08:52] <persia> Well, it just adds incentive to get the changes right the first time.
[08:53] <persia> I've not had much success with running ubiquity twice in the same session.  Seems that when ubiquity crashes, you need to manually remove hal locks, etc.  Easier to just reboot.
[08:53] <NCommande> and it just gets better and better
[08:53] <NCommande> oh well
[08:53] <NCommande> It shall be a learning experiment none the less
[08:54] <evand> I often hack on ubiquity from the live cd
[08:54] <NCommande> I figuring that might be possible
[08:54] <persia> evand: You don't encounter issues with HAL?
[08:54] <evand> What issues?
[08:54] <persia> Might just be my images (which are full of other sorts of problems)
[08:55] <persia> Well, if, for example, I do something that causes ubiquity to crash, running it again it complains about lockfiles.
[08:55] <evand> hrm
[08:55] <persia> I can probably reproduce it if you need: I figured it fell well into the "don't do that then" category.
[08:55] <evand> you may have to kill stray processes
[08:56] <persia> That might be it.
[08:56] <persia> For me, rebooting was the fast way to do that :)
[08:56] <evand> ps aux | grep part -- see if partman is still spinning in the background
[08:56] <evand> heh
[08:57]  * NCommande just sets up his Bazaar branch with his source
[08:57] <NCommande> Any reason why the Bazaar repo uses such an old Knit frmat?
[08:57] <NCommande> *format
[08:57] <persia> evand: Do you prefer conditional tests before execution, or exception processing when errors are encountered?
[08:57] <evand> it's an old repo and no one has bothered to update it
[08:58] <evand> persia: I'm not picky.  Whatever best suits the situation.
[08:58] <NCommande> so development isn't done there?
[08:58] <persia> If it is updated, it probably oughtn't be updated to be newer than that supported by bzr 1.3.1
[08:58] <persia> NCommande: Development is rarely done in a public repo: it's a means to share the code.
[08:59] <evand> NCommande: sorry, bad explanation.  ~ubuntu-installer/ubiquity/trunk is in fact where the development is done, it's just been around for a long time.
[08:59] <evand> persia: any idea how I go about doing that?
[08:59] <evand> bzr upgrade <remote source> ?
[09:00] <NCommande> persia: I figured as much, just wondering
[09:00] <NCommande> any special rules I need to know like about copyright assignment or such on hacking on ubuquity
[09:00] <persia> evand: I think you need to use scp, but I've never done it.  The guys in #launchpad have the answer.
[09:00] <NCommande> persia: no, it should work remotely
[09:00] <evand> http://wiki.ubuntu.com/InstallerDevelopment - I don't think there's any copyright assignment policy in place, but best to check with cjwatson on that.
[09:01] <NCommande> arg
[09:01] <NCommande> virtualbox doesn't work on current intrepid
[09:01] <evand> kvm is pretty awesome, I'd suggest giving it a go if your processor supports it
[09:02] <NCommande> I have the hack installed for my computers BIOS to enable VTx
[09:02] <NCommande> But I haven't got a clue on how to get started with kvm
[09:03] <evand> `kvm -hda somefile.img -m 768 -no-quit -k en-us` or some variation of is what I generally use
[09:03] <evand> where somefile.img is generated by qemu-img create
[09:03] <NCommande> I'll give it a spin
[09:03] <NCommande> I just need to install kvm, right?
[09:04] <evand> https://wiki.ubuntu.com/kvm
[09:04] <evand> should be a good starting point
[09:04] <evand> ah, I stand corrected: https://help.ubuntu.com/community/KVM
[09:15] <TheMuso> Unless I need to test sound in a VM, I use libvirt.
[09:15] <TheMuso> Very useful to manage multiple vms.
[09:16] <evand> cjwatson: any objection to upgrading the repository format for ~ubuntu-installer/ubiquity/trunk?
[09:26] <cjwatson> evand: none, I just haven't done it because bzr upgrade sftp:// takes bloody forever
[09:26] <evand> cjwatson: also, can you add usb-creator commits to the #ubuntu-installer CIA bot?  I've added the project to cia.vc.
[09:26] <evand> hahaha, ok
[09:26] <cjwatson> I would expect it to take hours, for the duration of which you don't get to commit to the branch
[09:27] <evand> hm
[09:28] <evand> I'll plan to do it this evening (EST), and if anyone feels that I should hold off so they can commit, please let me know beforehand.
[09:29] <persia> This evening being real soon now, or in 18-20 hours?
[09:29] <evand> 18-20 hours
[09:30] <evand> well, 16
[09:30] <persia> heh.  It's kinda late there :)
[09:30] <evand> Just out of curiosity, is it not possible to upgrade via bzr+ssh?
[09:31] <evand> early, really :)
[09:31] <cjwatson> not yet
[09:31] <evand> ok, noted
[09:31] <cjwatson> or at least it doesn't seem to work all that well
[09:31] <cjwatson> I believe that bzr 1.7 will add that
[09:31] <evand> cool
[09:32] <cjwatson> but at the moment, what bzr ends up doing is transferring every single file under .bzr back and forward several times, producing backup copies as well as for the actual upgrade
[09:32] <cjwatson> which is why it's so incredibly slow
[09:32] <cjwatson> each of those has to wait for round-trip times as well I think, it doesn't seem pipelinable as it stands
[09:32] <persia> Is it faster if run from somewhere network-near?
[09:32] <cjwatson> somewhat
[09:32] <cjwatson> I think "faster" is the wrong word. "Less painfully slow".
[09:32] <evand> lol
[09:33] <persia> OK.  Just wondering if it's worth asking for a run from either a machine in the DC or Ubuntuwire, rather than on an overseas link.
[09:33] <cjwatson> so I've upgraded a few installer repositories as they annoy me, but preferentially the smaller ones
[09:33] <cjwatson> you could ask #launchpad to upgrade it locally
[09:34] <evand> mm, I think I'll try for that, assuming they can accomodate the time or stick it in cron.
[09:34] <evand> I swear, cia.vc is run off a toaster oven.
[09:34] <cjwatson> locally, it should be fast enough that we don't have to worry about timing
[09:35] <cjwatson> I'd expect a minute or so at most
[09:35] <evand> ah, good point
[09:35] <cjwatson> cia.vc> annoying isn't it?
[09:35] <cjwatson> I'm *trying* to save the bot change ...
[09:35] <evand> hahaha, yeah it took me a good 10 minutes to just create the project
[09:35] <cjwatson> TheMuso: I'd use libvirt except that virt-manager's UI annoys me so much
[09:36] <TheMuso> cjwatson: Ah, I use cli to start it. :)
[09:36] <TheMuso> ubiquity doesn't have any ghost revisions by any chance? :)
[09:36] <cjwatson> no :)
[09:36] <cjwatson> grumble, lpia d-i failed to build
[09:37] <persia> I know why it failed on lpia, and it's being sorted.
[09:37] <TheMuso> Oh, and I've pushed some changes to casper trunk on launchpad, but launchpad is not reflecting them in the UI.
[09:37] <persia> Haven't looked at ia64
[09:37] <cjwatson> TheMuso: yeah, it won't
[09:37] <cjwatson> persia: sorted how?
[09:37] <evand> Is casper's bzr fixed?
[09:37] <TheMuso> cjwatson: Fair enough.
[09:37] <TheMuso> evand: No.
[09:37] <cjwatson> you've always been able to push to it, somewhat
[09:37] <evand> fun
[09:38] <cjwatson> I've fixed xivulon's mount -t ntfs thing, I think
[09:38] <persia> cjwatson: Actually shipping the additional d-i modules.  The problem was http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid-lpia.git;a=commitdiff;h=5041792ac41d6c5425598a4995b20370e7a79bb1
[09:38] <cjwatson> (enabled mount helpers in busybox)
[09:38] <evand> ah, thanks for taking care of that
[09:38] <cjwatson> persia: oh dear goodness. When will the kernel team learn that they need to tell us about this shit?
[09:38] <cjwatson> persia: is the fix to revert that commit?
[09:38] <persia> It's being reverted.
[09:39] <cjwatson> excellent
[09:39] <cjwatson> feel free to whack the rebuild button on d-i when it is
[09:39] <persia> I can't, but I'll deputise someone.
[09:39] <cjwatson> persia: ia64 is because linux-ports fails to build on ia64, and has done for months
[09:39] <persia> OK.  That needs someone who cares about the ia64 kernel then.
[09:41] <persia> Also, while reverting the commit, the lpia kernel will probably have an ABI bump.  I've been promised this process will include an email to the installer team, as I suspect it will require a change to build/config/lpia.cfg.  Will it save any time to prepare that branch, or is it just as easy to process from the mail?
[09:50] <cjwatson> it won't save any time to prepare the branch in advance
[09:50] <cjwatson> it's a sed
[09:55] <xivulon> cjwatson any hint on previous posts?
[09:55] <cjwatson> 09:38 <cjwatson> I've fixed xivulon's mount -t ntfs thing, I think
[09:55] <cjwatson> 09:38 <cjwatson> (enabled mount helpers in busybox)
[09:57] <xivulon> ah great, thanks a bunch, will resume tests tonight and let you know (davmor2 if you are around give it a go once the new busybox is up)
[10:05] <TheMuso> Unless anybody has some pressing casper changes they need to get in, I'd like to do an upload of casper to unbreak some accessibility profiles.
[10:05] <cjwatson> nothing from me
[10:14] <xivulon> TheMuso, on a different subject, how are things with panic messages?
[10:18] <TheMuso> xivulon: Should be fixed for intrepid, but I have been so busy the past months with intrepid work, that I haven't yet done an SRU for hardy.
[11:18] <NCommander> evand: which process did I have to kill to get ubiquity to work twice in the install?
[11:19] <persia> NCommander: start by looking for partman.
[11:20] <NCommander> I just had to kill hal-lock and it started
[11:20] <persia> After that, start looking for anything with a higher process number than used by ubiquity.
[11:20] <persia> Are you sure rebooting isn't easier?
[11:21] <cjwatson> as evand said, running ubiquity twice in one session should not normally be a problem
[11:22] <cjwatson> I've never heard of hal-lock sticking around before
[11:22] <cjwatson> sometimes parted_server sticks around, but that's all
[11:22] <cjwatson> I often run it successively - saves a lot of time when editing stuff on the fly
[11:25] <persia> Maybe this is a new issue?  I always saw hal-lock sticking around.
[11:25] <persia> (well, since my images stopped being so broken that ubiquity couldn't run)
[11:40] <foka> Happy Mid-Autumn Festival, everyone!  中秋节快乐！ :-)
[13:30] <kirkland> TheMuso: kees did :-)  thanks!!!
[14:27] <kirkland> cjwatson: hi there, do you have a couple of minutes?  I'm trying to implement your suggestions for https://bugs.launchpad.net/ubuntu/+source/partman-target/+bug/268580
[14:27] <kirkland> cjwatson: i want to knock this out ASAP because of UI freeze :-/
[14:28] <cjwatson> kirkland: yes
[14:28] <kirkland> cjwatson: sweet ... okay, the templates file....
[14:29] <kirkland> cjwatson: should i create an mdadm-udeb.templates with just the boot_degraded question?
[14:29] <kirkland> cjwatson: ie, is that the proper method for getting the question into the udeb?
[14:29] <cjwatson> you already need an mdadm.templates, right? don't duplicate it
[14:29] <kirkland> cjwatson: right, the question is already in there
[14:29] <kirkland> cjwatson: it's used for dpkg-reconfigure mdadm in a running system
[14:30] <kirkland> cjwatson: works there now...  just want to add the question into the installer
[14:30] <cjwatson> kirkland: is there anything else in mdadm.templates that would need to be filtered out of the udeb?
[14:30] <kirkland> cjwatson: autocheck, mail_to, start_daemon
[14:31] <kirkland> cjwatson: i suppose those might be nice to actually ask, if someone is installing raid
[14:31] <cjwatson> then I'd recommend putting the boot_degraded question in a separate templates file; it doesn't matter what it's called
[14:31] <cjwatson> like debian/mdadm-boot-degraded.templates or something
[14:31] <kirkland> cjwatson: but raid installs then become somewhat significantly more conversational
[14:31] <cjwatson> don't make them more conversational :)
[14:31] <kirkland> cjwatson: agreed
[14:31] <kirkland> cjwatson: okay, done.
[14:32] <cjwatson> then add that new .templates file to debian/po/POTFILES.in
[14:32] <cjwatson> then after dh_installdebconf in debian/rules, add this:
[14:32] <cjwatson>         echo >> debian/mdadm/DEBIAN/templates
[14:32] <cjwatson>         po2debconf debian/mdadm-boot-degraded.templates >> debian/mdadm/DEBIAN/templates
[14:33] <cjwatson>         po2debconf debian/mdadm-boot-degraded.templates > debian/mdadm-udeb/DEBIAN/templates
[14:33] <cjwatson> something like that anyway
[14:33] <cjwatson> as you can see you can just build up the templates file in the package's control area dynamically
[14:33] <kirkland> cjwatson: sounds good
[14:33] <kirkland> cjwatson: okay, so do i add the check.d directory to the debian/ dir, or the top level?
[14:33] <cjwatson> an alternative approach would be to put that question only in mdadm-udeb.templates, and append that to debian/mdadm/DEBIAN/templates in much the same way
[14:34] <cjwatson> I think the above might be clearer in this case though
[14:34] <cjwatson> it doesn't matter. convention is the top level but it isn't mandatory
[14:34] <cjwatson> if you put it at the top level, then you can use the install-rc script from other partman-* packages to install it
[14:34] <kirkland> cjwatson: that does sound better to me, the mdadm-udeb.templates
[14:34] <cjwatson> (without modifying it)
[14:35] <cjwatson> kirkland: ok, then you can just echo >> debian/mdadm/DEBIAN/templates; po2debconf debian/mdadm-udeb.templates >> debian/mdadm/DEBIAN/templates
[14:35] <cjwatson> to make sure it appears in both without having to duplicate it in the source
[14:36] <cjwatson> just keep debian/po/POTFILES.in up to date, and remember to run debconf-updatepo after changing the .templates
[14:36] <kirkland> cjwatson: its in the clean block
[14:36] <cjwatson> was it there already from the current package?
[14:36] <kirkland> cjwatson: yup
[14:36] <kirkland> cjwatson: last step of "clean" in the rules
[14:37] <cjwatson> I generally prefer not to have it in clean myself, and to have the maintainer do it; saves on spurious timestamp diffs
[14:37] <cjwatson> but if it's there already, leave it
[14:37] <kirkland> cjwatson: k
[14:37] <kirkland> cjwatson: okay, so i put a check.d in the top level of mdadm source
[14:37] <kirkland> cjwatson: there's a _numbers file
[14:38] <kirkland> cjwatson: suggested value for, "05 root_on_raid" ...  ?
[14:38] <kirkland> cjwatson: this is an ordering, right?  i'm the only one
[14:38] <kirkland> cjwatson: so just leave some room for before and after?
[14:39] <cjwatson> kirkland: hmm, I don't think there's any particular sequencing in check.d. I'd put it with crypto if I were you, which would make it 07
[14:40] <kirkland> cjwatson: 07 root_on_raid, okay
[14:40] <cjwatson> it's not a big deal though, just controls which check will blow up first if multiple things are wrong *shrug*
[14:40] <kirkland> cjwatson: i called the script, root_on_raid
[14:40] <cjwatson> sure, that's fine
[14:40] <kirkland> cjwatson: seemed to read sort of like "proper_mountpoints", etc.
[14:41] <kirkland> cjwatson: in that script, i borrowed some code from proper_mountpoints
[14:41] <kirkland> cjwatson: basically looking if / or /boot is on a device named /dev/md*
[14:41] <kirkland> cjwatson: i had:                                 db_input critical mdadm/boot_degraded || true
[14:41] <kirkland> cjwatson: i think you suggested:
[14:42] <kirkland>                                 db_get mdadm/boot_degraded
[14:42] <kirkland>                                 echo mdadm mdadm/boot_degraded boolean "$RET" | debconf-set-selections
[14:42] <cjwatson> right, that's to go after the db_go
[14:42] <cjwatson> just transfers the setting into /target
[14:42] <kirkland>                         if [ "$mp" = "/" ] || [ "$mp" = "/boot" ]; then
[14:42] <kirkland>                                 db_input critical mdadm/boot_degraded || true
[14:42] <kirkland>                                 db_go || true
[14:42] <kirkland>                                 db_get mdadm/boot_degraded
[14:42] <kirkland>                                 echo mdadm mdadm/boot_degraded boolean "$RET" | debconf-set-selections
[14:42] <kirkland>                                 break
[14:42] <kirkland>                         fi
[14:42] <cjwatson> or, more strictly, queues it up to be transferred into /target once /target exists
[14:43] <cjwatson> yep
[14:43] <cjwatson> remind me how you're checking that the mountpoint in question is on RAID?
[14:43] <kirkland> cjwatson: okay, now what do I need to do to hook check.d/* to run?
[14:44] <cjwatson> 'debian/install-rc check.d' in the install target in debian/rules; see any partman-* package
[14:44] <kirkland> cjwatson: http://pastebin.ubuntu.com/46227/
[14:44] <kirkland> cjwatson: ^^^ untested
[14:44] <kirkland> cjwatson: okay, i'll grab it from partman-target, where I got most of this
[14:44] <cjwatson> looks plausible
[14:44] <cjwatson> oh, hmm
[14:45] <kirkland> cjwatson: k
[14:45] <cjwatson> I think you might have to consume the rest of the output from the fstab.d scripts otherwise stuff will go wrong
[14:46] <cjwatson> so found=0 up top, found=1 instead of break, and if [ "$found" = 1 ]; then continue; fi at the top of the while loop
[14:46] <kirkland> cjwatson: good suggestion, i'll do that
[14:46] <cjwatson> just to avoid stuff getting SIGPIPE. I can't remember whether that matters in this case but it certainly can do in other contexts
[14:46] <kirkland> cjwatson: that'll be more clear
[14:46] <cjwatson> specifically when you're reading from parted_server, things go badly wrong if you don't consume all the output
[14:47] <kirkland> cjwatson: okay, i'll need to install the check script into partman from mdadm
[14:47] <cjwatson> mdadm-udeb, rather
[14:48] <kirkland> cjwatson: gotcha
[14:49] <kirkland> cjwatson: so should the install-rc bit be in a udeb-specific section of the rules?
[14:49] <cjwatson> oh, maybe PACKAGE=mdadm-udeb debian/install-rc check.d
[14:49] <cjwatson> that'll force it to be copied into the right package
[14:50]  * kirkland puts that neat trick in his back pocket
[14:51] <kirkland> cjwatson: okay, let me get a debdiff for spot-inspection
[14:51] <kirkland> cjwatson: to test this, I'll build the udeb, and scp it over to a running installation kvm, udpkg -i the udeb, and restart the partitioning?
[14:52] <cjwatson> right, or even just udpkg -i before partitioning starts
[14:52] <cjwatson> mdadm-udeb doesn't have a postinst, right?
[14:54] <kirkland> cjwatson: it does not
[14:56] <cjwatson> ok, that's good. If it did, you'd have to use udpkg --unpack as -i would run the postinst immediately.
[14:57] <kirkland> cjwatson: untested debdiff looks like: http://pastebin.ubuntu.com/46231/
[14:58] <kirkland> cjwatson: more changelogging to come
[14:59] <cjwatson> kirkland: looks plausible. remember debian/po/POTFILES.in though
[15:00] <kirkland> cjwatson: right, okay, i manually pruned the generated .po changes
[15:01] <kirkland> cjwatson: and must have accidentally pruned that too
[15:01] <cjwatson> ok
[15:01] <kirkland> cjwatson: okay, i'll go test this
[15:01] <kirkland> cjwatson: thanks for your help
[15:09] <kirkland> cjwatson: okay, i that db_input action did not fire...  at what point in the partitioning would you have expected it?
[15:09] <cjwatson> after selecting finish
[15:10] <cjwatson> you can debug it by sticking set -x at the top
[15:10] <cjwatson> oh, make sure it's executable too!
[15:10] <cjwatson> you might need to put chmod +x in debian/rules
[15:10] <cjwatson> partman-* packages don't need that because they're all native, but the executable bit isn't preserved on files added in the Debian diff
[15:11] <cjwatson> (this is perhaps not obvious)
[15:11] <kirkland> cjwatson: i bet that's it
[15:11] <kirkland> cjwatson: i should have remembered that
[15:55] <kirkland> cjwatson: i know your attention is elsewhere now, so just answer this question in time...  I am certain that the code path containing "db_input critical mdadm/boot_degraded" is getting executed...  but the question is not making it to the installer screen...  ideas?
[15:56] <kirkland> cjwatson: perhaps the question didn't make it into the debconf db?  how can I check that?
[15:57] <cjwatson> oh
[15:57] <cjwatson> of course, you're running it in a while loop with stdin coming from a pipe
[15:57] <cjwatson> debconf uses stdio ..
[15:58] <cjwatson> have a look at the must_be_on_root function in partman-target's proper_mountpoints - you need to follow that model
[15:58] <cjwatson> i.e. have the while loop output a list of things to act on (or nothing), and then iterate over that in a for loop that *doesn't* have piped stdin
[15:58] <cjwatson> this is considered a wart in debconf
[16:00] <kirkland> cjwatson: fooey :-)  okay.
[16:01] <cjwatson> archive-copier used to have a supremely ugly solution to this involving redirecting to fd 9
[16:01] <cjwatson> fortunately that abomination is long since dead
[16:01] <kirkland> that's obfuscation ;-)
[16:04] <cjwatson> http://bazaar.launchpad.net/~kamion/archive-copier/mainline/annotate/170?file_id=x_Colin_Watson_<colin.watson%40canonical.com>_Tue_Aug_10_16%3A59%3A47_2004_7462.3 lines 187-194 if you care
[16:04] <superm1> evand, how scriptable is this live usb creator going to be?  Will it be possible to call it outside the live environment?  Eg on normal ubuntu system w/ the cdimage as an argument?
[16:07] <evand> superm1: I eventually intend to write a console frontend, though I can probably get away with accepting arguments for the source, target, and persistence size now with the GTK UI
[16:07] <evand> however it does not download ISO files at the moment, and that's quite a large feature to add past FF.
[16:08] <evand> oh
[16:08] <evand> sorry, I misread
[16:08] <evand> I thought you were suggesting that cdimage.ubuntu.com was the argument.
[16:08] <superm1> evand, nah, well I ask because one of the things I'm going to be throwing together this month is something that will convert the recovery media ISO that we generate from  factory over to a USB image.  I started to put it together and came across the existence of this project that you are were trying to get ready for main
[16:09] <evand> superm1: it's in bzr if you'd like to have a look at the code to see if it's applicable to your project.
[16:09] <evand> lp:~ubuntu-installer/usb-creator/trunk
[16:10] <superm1> evand, okay thanks, i'll see.
[16:10] <evand> Anytime
[16:10] <superm1> evand, as it stands from my briefly reading, it looked like it had to be called while booted into the live cd.  is that the case?
[16:11] <evand> Not at all.  It only requires a CD or ISO to use.
[16:11] <evand> Nothing extra aside from the obvious (HAL, D-BUS, GTK)
[16:11] <superm1> okay then this may be a lot more feasible.  I'll take a look.
[16:12] <superm1> given that you already mentioned HAL, probably a lot more intelligent than what I was starting to do w/ parsing /sys/block for devices and requiring the user to refresh
[16:25] <evand> heh, yikes
[16:26] <evand> yeah, this will automatically update the UI and its options based on the state of the drives, as well as automatically add new CDs and USB disks.
[16:34] <CIA-50> debian-installer: cjwatson * r962 ubuntu/ (build/config/lpia.cfg debian/changelog): Move lpia to 2.6.27-3 kernels.
[16:39] <persia> cjwatson: Please don't upload that yet: the binaries haven't published, so it will FTBFS (or I suppose we can press the button later)
[16:39] <cjwatson> yep, I checked
[16:39] <cjwatson> just getting it into bzr for the meantime
[16:40] <persia> OK.  I'm watching the build, and will let you know when it's published.
[16:42] <kirkland> cjwatson: dude, i'm definitely outside of the stdio pipe, mirrored must_be_on_root operation, definitely hitting the db_input critical call, but still not seeing the prompt
[16:42] <cjwatson> kirkland: DEBCONF_DEBUG=developer may help you
[16:42] <cjwatson> persia: tell me when it hits NEW and I'll shove it through
[16:43] <persia> cjwatson: That's even better, as our archive-admin went to bed :)
[16:43] <kirkland> cjwatson: http://pastebin.ubuntu.com/46280/ fyi
[16:50] <cr3> is there any ssl support in the busybox environment? libssl, stunnel, etc.?
[16:52] <cjwatson> doubt it
[16:52] <cjwatson> oh, actually we must ship a libssl udeb
[16:52] <cjwatson> libcrypto0.9.8-udeb IIRC, basically just for use by openssh-*-udeb
[16:54] <cr3> cjwatson: hm, not quite libssl, so I probably won't be able to perform https connections
[16:54] <cjwatson> no - why do you need that?
[16:55] <cjwatson> (busybox wget doesn't have https support anyway)
[16:55] <cr3> cjwatson: I wanted to submit test results during the installation process, but I guess I could support both secured and unsecured connections
[16:56] <cr3> if I wanted to submit to Launchpad, I wonder if that would be a feasible request
[16:57] <kirkland> cjwatson: interesting, when i run ./07root_on_raid manually, it does-the-right-thing, but not when it's called from partman
[17:04] <kirkland> cjwatson: how would I verify that the mdadm/boot_degraded question actually made it into the debconf database?
[17:04] <kirkland> cjwatson: actually, scratch that...  it's there when I run it by hand
[17:05] <cjwatson> let me get back to you after this meeting
[17:05] <kirkland> cjwatson: no prob
[17:05] <kirkland> cjwatson: fwiw, i have 2.5 hours, then I leave the office to catch a flight
[17:54] <superm1> evand, you i'm not sure if it was intended just because of your development process, but you have the glade file referenced directly within the tree, so when a deb get's built it's not usable
[17:56] <evand> argh
[17:56] <evand> I keep doing that by accident
[17:57] <superm1> might be best to set up a variable at the top perhaps
[17:58] <superm1> so glancing through, the app has the expectation that the drive you are going to use is already formated, so i take it you've decided that is a fair assumption?
[17:59] <cjwatson> ... and mounted (I filed a bug about that)
[18:00] <evand> it's not a fair assumption, it just doesn't handle that case yet.
[18:00] <superm1> ah okay
[18:02] <CIA-50> usb-creator: evand * r10 usb-creator/usbcreator/ (backend.py gtk_frontend.py): Fixed paths.
[18:02]  * evand pets CIA-50 
[18:02] <superm1> something else that you might want to consider doing, when you copy over the contents of the ISO to the flash drive, you might want to regenerate the UUID in .disk and the initramfs. so as to prevent confusion/slowness if someone happens to have a cd in the drive with the same .disk etc
[18:02] <cjwatson> oh good, it worked
[18:03] <evand> superm1: ah, good call.  Noted
[18:03] <superm1> evand, in casper there's a script that I submitted sometime during hardy, a variant of it is what we've been using when making recovery media
[18:04] <evand> ok
[18:04] <superm1> (for the exact same type of issue, where the recovery partition is always present when you put in the CD)
[18:07] <cjwatson> kirkland: did you try DEBCONF_DEBUG=developer? can I see the output from it?
[18:07] <cjwatson> (boot with that on the kernel command line)
[18:08] <cjwatson> kirkland: oh and FWIW you don't need the for loop, just do case $prompt in ... esac
[18:08] <cjwatson> (case's variable expansion semantics DTRT there)
[18:12] <kirkland> cjwatson: i tried the DEBUG thing, where does the output land?
[18:12] <cjwatson> /var/log/syslog
[18:12] <cjwatson> you'll get a BIG trace
[18:12] <cjwatson> it's a hammer, but an exceedingly useful one
[18:13] <kirkland> cjwatson: one sec, i'll grab it
[18:14] <persia> cjwatson: linux-lpia hit new.  Please forgive the missing Architecture:all packages - it's a known build issue, but the fix isn't critical for either the alternate CD or the live image (I think).
[18:15] <kirkland> cjwatson: okay, db_input not found ...  do I suppose I need to source something to get the debconf functions?
[18:16] <kirkland> cjwatson: none of the other scripts in there have anything exotic sourced, just the /lib/partman/lib/base.sh
[18:21] <kirkland> cjwatson: http://pastebin.ubuntu.com/46313/
[18:24] <cjwatson> kirkland: /lib/partman/lib/base.sh sources the debconf confmodule as the first thing it does
[18:24] <kirkland> cjwatson: good
[18:24] <cjwatson> kirkland: can I see the *exact* script you're currently using?
[18:24] <kirkland> cjwatson: when I sh -x the script
[18:25] <cjwatson> I have http://pastebin.ubuntu.com/46280/ but it's not that
[18:25] <kirkland> cjwatson: I get: RET=10 "mdadm/boot_degraded" doesn't exist
[18:25] <kirkland> cjwatson: sure
[18:25] <cjwatson> don't run any of these scripts from the shell prompt
[18:25] <cjwatson> it will not work properly and it will confuse you
[18:25] <cjwatson> you need to edit set -x into them and have partman run them
[18:26] <kirkland> cjwatson: http://pastebin.ubuntu.com/46319/
[18:26] <cjwatson> DEBCONF_DEBUG=developer will not work in the script; you need to boot with it on the kernel command line
[18:26] <cjwatson> it's checked by the frontend, not the confmodule
[18:27] <kirkland> cjwatson: didn't grok that, sorry
[18:28] <cjwatson> this is really weird, I can't figure it out
[18:28] <kirkland> cjwatson: let me post the full debdiff, just in case
[18:29] <cjwatson> could you explain to me exactly what you did? did you scp the udeb into the installer?
[18:29] <kirkland> cjwatson: yes
[18:29] <kirkland> cjwatson: udpkg -i *udeb
[18:29] <cjwatson> ok, I'd like the debdiff, sure
[18:29] <kirkland> cjwatson: then ran the partitioning
[18:30] <cjwatson> if possible on non-pastebin so I can check for funny characters
[18:30] <kirkland> cjwatson: this one has the po poo : http://pastebin.ubuntu.com/46321/
[18:31] <cjwatson> where is "date" coming from? it's not in your debdiff
[18:32] <kirkland> cjwatson: after i install my debdiff, then i have been doing "active development" in the install filesystem
[18:32] <kirkland> cjwatson: by manually editing 07raid_on_root
[18:32] <kirkland> cjwatson: backing out to the partman screen that has "Finish" on it
[18:32] <kirkland> cjwatson: and then I rerun finish
[18:33] <cjwatson> did you change anything else? :)
[18:33] <kirkland> cjwatson: my script runs between clicking "Finish" and the warning that I have no swap space
[18:33] <kirkland> cjwatson: :-)  no  just 07raid_on_root
[18:34] <kirkland> cjwatson: i just kicked off a fresh install with DEBCONF_DEBUG=developer
[18:34] <kirkland> cjwatson: perhaps i polluted something else along the way....
[18:35] <kirkland> cjwatson: i'm going to go through the networking setup
[18:35] <cjwatson> I just can't see how this could happen with that script
[18:35] <kirkland> cjwatson: and anna-install openssh-client-udeb
[18:35] <cjwatson> you need to chmod +x debian/install-rc in debian/rules FYI
[18:35] <cjwatson> PACKAGE=mdadm-udeb debian/install-rc check.d
[18:35] <cjwatson> /bin/sh: debian/install-rc: Permission denied
[18:35] <cjwatson> do it just before calling it
[18:39] <kirkland> cjwatson: see line 799 of http://pastebin.ubuntu.com/46321/
[18:39] <kirkland> cjwatson: (and I notice my whitespace is off)
[18:39] <cjwatson> kirkland: you need to chmod +x debian/install-rc too, not just the check.d script
[18:40] <kirkland> cjwatson: oh
[18:42] <kirkland> cjwatson: okay, i've installed my updated udeb
[18:42] <kirkland> cjwatson: i'm going through the raid partitioning
[18:42] <cjwatson> persia: processing now, thanks
[18:43] <persia> cjwatson: Thank you.  Do you expect to need anything else from us to get d-i built for lpia for 2:02 BST?
[18:43] <cjwatson> persia: nope
[18:44] <persia> Great.  Thanks again.
[18:45] <cjwatson> (you going to be working on it over the weekend or something?)
[18:45] <cjwatson> err, and speaking of, isn't it 0dark:00 in .jp?
[18:45] <kirkland> cjwatson: fresh syslog http://pastebin.ubuntu.com/46329/
[18:45] <kirkland> cjwatson: syslog from a fresh install
[18:46] <cjwatson> ok, so at least it's stopped spewing shell syntax errors
[18:46] <kirkland> cjwatson: it's like the mdadm/boot_degraded isn't making it into the debconf db
[18:46] <cjwatson> oh! duh
[18:46] <kirkland> cjwatson: :-)  yeah, that was probably from one of many, many dev runs on that system
[18:46] <cjwatson> sorry, I forgot, you can't install udebs that contain templates from tty2
[18:46] <kirkland> cjwatson: wtf?  :-)
[18:46] <persia> cjwatson: I'm not very good with tracking solar cycles :)
[18:47] <cjwatson> kirkland: complicated reasons due to how debconf is plumbed into the installer; basically, it updates the database, but that doesn't help the running debconf instance on tty1 notice it
[18:47] <kirkland> cjwatson: so is tty3 magically blessed?
[18:47] <cjwatson> kirkland: no, it is possible but you need to do something more evil
[18:47] <cjwatson> if I could bless tty3 I'd bless tty2 too :-)
[18:47] <kirkland> cjwatson: yeah, that was a joke ;-)
[18:48] <kirkland> cjwatson: okay, so is there some way to "refresh" the debconf instance on tty1?
[18:48] <cjwatson> kirkland: wait :)
[18:48] <kirkland> cjwatson: or install the udeb from tty1?
[18:48] <cjwatson> kirkland: so, when you get to that netcfg prompt, stop
[18:49] <cjwatson> kirkland: edit /var/lib/dpkg/info/clock-setup.postinst (this is just a handy victim because it comes after netcfg and before partitioning)
[18:49] <kirkland> cjwatson: do i need to restart my current install, or can i back it out far enough?
[18:49] <cjwatson> kirkland: below . /usr/share/debconf/confmodule, put 'wget http://url/of/your/udeb; udpkg -i your.udeb'
[18:49] <cjwatson> kirkland: you need to restart
[18:50] <kirkland> cjwatson: okay, lemme try that
[18:50] <cjwatson> yes, this is a mess
[18:50] <kirkland> cjwatson: well, black magic at the very least
[18:50] <cjwatson> it's a mess, and it's related to debconf using stdio so there's no way to get at it from another process to send it commands
[18:50] <cjwatson> such as X_LOADTEMPLATEFILE
[18:51] <cjwatson> debconf needs to be properly client/server in order to fix this, but that requires an internal select loop and all kinds of gubbins ... not easy
[18:51] <cjwatson> Tollef had a go at it a while back
[18:52] <cjwatson> ~    
[18:52] <cjwatson> (sorry, network-manager randomly decided to break my network)
[18:53] <kirkland> cjwatson: what about a hook that, on every screen refresh in debconf, sources a file in some magic location if it exists, to read a template
[18:53] <cjwatson> then you have to decide what happens when they're changed in both locations
[18:54] <cjwatson> it needs to be a lot more structured than that
[18:54] <kirkland> cjwatson: okay, not my current problem ;-)
[18:54] <cjwatson> you get used to the workaround, really :)
[18:54] <cjwatson> and it doesn't affect end users, so low priority
[18:57] <kirkland> cjwatson: what can i use in place of dpkg -l ?
[18:57] <kirkland> cjwatson: to check that it was installed?
[18:58] <kirkland> cjwatson: i see it in / so it was at least wgot
[19:00] <kirkland> cjwatson: \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/ \o/  \o/  \o/  \o/
[19:01] <evand> hahaha, that's quite a bit of excitement
[19:01] <kirkland> evand: this has been many hours invested, with relatively little show of progress
[19:02] <kirkland> evand: until now :-)
[19:04] <cjwatson> kirkland: nano -v /var/lib/dpkg/status
[19:05] <kirkland> cjwatson: debconf question successfully posed
[19:06] <kirkland> cjwatson: i'm testing the rest of the install now, to ensure that the answer to that question is in fact applied and effective ;-)
[19:06] <cjwatson> cool. check that it landed in /var/lib/preseed/log
[19:06] <kirkland> cjwatson: while it's installing, would you clarify one thing.....
[19:06] <kirkland> cjwatson: k
[19:07] <kirkland> cjwatson: when I post the final debdiff, I should have the one change to the POTFILES.in, but not the 50+ changes to all the .po's....  is that correct?
[19:07] <cjwatson> right, if you accompany it with an instruction to run debconf-updatepo after application
[19:07] <cjwatson> that's certainly what I'd prefer
[19:07] <kirkland> cjwatson: okay, i'll prep that
[19:08] <kirkland> cjwatson: i have to leave for the airport in 23 mins, i'll drop it before then
[19:14] <Goosemoose> I keep getting a 'failed with exit code 127' for this presed command: d-i preseed/late_command string wget http://10.0.2.131/post_install_tasks && chmod +x ./post_install_tasks && ./post_install_tasks returns > /dev/null 2>&1
[19:14] <Goosemoose> anyone have any ideas? with the wget statement alone it works fine
[19:15] <Goosemoose> i just added the /dev/null part on the last run to test it
[19:20] <cjwatson> is there anything in syslog?
[19:21] <cjwatson> (please don't send me private /msgs duplicating stuff in this channel; I pay attention to this channel when I'm around and it won't make me see things any faster)
[19:22] <kirkland> cjwatson: doesn't look like the value of that debconf made into the /target
[19:22] <cjwatson> kirkland: was it in /var/lib/preseed/log?
[19:24] <kirkland> cjwatson: i'm going to pick this back up at the airport once I get on wireless
[19:25] <kirkland> cjwatson: my concern was this making it in before ui freeze
[19:25] <cjwatson> kirkland: your problem is that you're setting BOOT_DEGRADED in mdadm.config
[19:25] <cjwatson> (debian/mdadm.config)
[19:25] <cjwatson> -BOOT_DEGRADED="false"
[19:25] <kirkland> cjwatson: ah, yeah, that's deprecatednow
[19:25] <cjwatson> +BOOT_DEGRADED=""
[19:25] <cjwatson> that should fix it
[19:25] <kirkland> cjwatson: good catch
[19:25] <kirkland> cjwatson: okay...  so i've been slammed with landscape stuff all week, my apologies for this being late
[19:25] <kirkland> i'm desperately trying to get you this today
[19:25] <cjwatson> no worries
[19:26] <cjwatson> I'm fairly relaxed about UI freeze for server
[19:26] <kirkland> cjwatson: thank you
[19:26] <cjwatson> the people who really care are people taking screenshots, and this is an edge case for them
[19:37] <cjwatson> persia: the d-i I'm about to upload might fail on lpia, but ignore it, I can retry later if it does
[19:37] <cjwatson> just want to get it off my disk
[19:39] <CIA-50> debian-installer: cjwatson * r963 ubuntu/debian/changelog: releasing version 20080522ubuntu14
[19:52] <Goosemoose> hey cjwatson, sorry about the priv msg
[19:52] <Goosemoose> cjwatson, which file should i be looking in for the error?
[19:53] <Goosemoose> the /var/lib/preseed/log?
[20:07] <Goosemoose> cjwatson?
[20:08] <Goosemoose> oh, my other issue is that: d-i partman-lvm/confirm boolean true , is not preventing the error about an existing volume being present which is stopping the preseed as well
[20:53] <Goosemoose> this is nuts, there's gotta be some better examples for preseed files
[20:58] <cjwatson> Goosemoose: when I said /var/lib/preseed/log, I was talking to kirkland about something completely different.
[20:58] <Goosemoose> ok
[20:58] <cjwatson> Goosemoose: /var/log/syslog
[20:58] <Goosemoose> ok, let me look
[20:58] <cjwatson> Goosemoose: from the installation guide:
[20:58] <cjwatson> # If one of the disks that are going to be automatically partitioned
[20:58] <cjwatson> # contains an old LVM configuration, the user will normally receive a
[20:58] <cjwatson> # warning. This can be preseeded away...
[20:58] <cjwatson> d-i partman-lvm/device_remove_lvm boolean true
[20:58] <Goosemoose> yes exactly, i have that line just like that
[20:58] <Goosemoose> but the command still gets asked
[20:59] <Goosemoose> or question asked
[20:59] <cjwatson> you said partman-lvm/confirm earlier
[20:59] <Goosemoose> oh i have both
[20:59] <cjwatson> what release of Ubuntu are you trying to install?
[20:59] <Goosemoose> hardy
[20:59] <Goosemoose> actually, hmm
[20:59] <Goosemoose> i have: d-i partman-auto/purge_lvm_from_device boolean true
[21:00] <cjwatson> Goosemoose: what is the exact text of the question you see/
[21:00] <cjwatson> ?
[21:01] <Goosemoose> its no on the screen right now but im sure your statement will take care of it. let me look at the syslog regarding that late_command error
[21:01] <Goosemoose> funny, i d/l this preseed.cfg from the ubuntu website
[21:01] <cjwatson> OK, this was a bug in the hardy installation-guide unfortunately
[21:01] <Goosemoose> got it
[21:01] <cjwatson> it was changed in Debian, but I didn't notice the change so we didn't pick it up; my fault
[21:01] <Goosemoose> its ok
[21:02] <Goosemoose> if i can figure out these last two
[21:02] <Goosemoose> checking the syslog ,just a sec
[21:03] <cjwatson> http://bazaar.launchpad.net/~vcs-imports/installation-guide/trunk/revision/3099 was the installation-guide change in question
[21:04] <Goosemoose> there's nothing in the syslog regarding the late_command error
[21:04] <Goosemoose> d-i preseed/late_command string wget http://10.0.2.131/post_install_tasks && chmod +x ./post_install_tasks && ./post_install_tasks returns > /dev/null 2>&1
[21:04] <Goosemoose> if i just do the wget part it works fine
[21:04] <Goosemoose> if i run it from a command line it works fine
[21:04] <Goosemoose> as a preseed i get exit code 127
[21:04] <cjwatson> there should be *some* output at least; could you put the full syslog somewhere for me and I'll take a look?
[21:05] <Goosemoose> i think the machine has been rebooted which is why
[21:05] <Goosemoose> it just has a complaint about me trying to log in as root
[21:05] <Goosemoose> i can post it, just a sec
[21:05] <cjwatson> err, is this post-install? you need /var/log/installer/syslog then
[21:05] <Goosemoose> ahh ok
[21:07] <Goosemoose> hmm
[21:07] <Goosemoose> http://pastebin.com/d4cfe1c27
[21:08] <Goosemoose> looks like a few errors
[21:08] <Goosemoose> i do install likewise and i know it starts when the machine restarts
[21:08] <Goosemoose> looks like the domainjoin-cli command isn't valid there
[21:08] <cjwatson> pushd and popd are bashisms; you can't use them in d-i's shell
[21:09] <cjwatson> are you intending for this command to be run in the target system?
[21:09] <Goosemoose> ok. i had just tried that after reading a website where the guy specifically wrote out to use that
[21:09] <Goosemoose> yes
[21:09] <Goosemoose> i want the system to join the domain
[21:09] <cjwatson> you see, your late_command runs the command in the installer environment
[21:09] <Goosemoose> i also copy the nsswitch.conf to fix the but with .local domains
[21:09] <cjwatson> you need this instead:
[21:10] <cjwatson> d-i preseed/late_command string wget -O /target/post_install_tasks http://10.0.2.131/post_install_tasks && chmod +x /target/post_install_tasks && chroot /target /post_install_tasks returns >/dev/null 2>&1 && rm -f /target/post_install_tasks
[21:10] <cjwatson> (what's the "returns" for?)
[21:11] <Goosemoose> just something i was reading
[21:11] <Goosemoose> i added it later
[21:11] <Goosemoose> to test if it helped
[21:12] <Goosemoose> ok so the only difference is to chroot /target
[21:12] <Goosemoose> ok im referring directly to the file in /target too
[21:13] <Goosemoose> so in my script, can i rm /etc/nsswitch.conf if im just in the installer environment? i can i access outside the target folder?
[21:14] <cjwatson> 'chroot /target foo' means you're no longer in the installer environment (effectively)
[21:14] <cjwatson> no, you can't break out of /target within that, but from your description you don't need to
[21:14] <cjwatson> the stuff in /target is what the real system will be after you reboot
[21:15] <Goosemoose> well the other thing i do is to download a new nsswitch.conf file
[21:15] <cjwatson> so you only need to remove /etc/nsswitch.conf in /target, not in the installer environment
[21:15] <Goosemoose> its in the post_insatll_tasks
[21:15] <cjwatson> that should work fine, chrooting doesn't particularly affect networking
[21:16] <Goosemoose> oh so im doing rm -f /target/etc/nsswitch.confg?
[21:16] <cjwatson> you do not need to change your script
[21:16] <cjwatson> I mean, yes, you are effectively, but you shouldn't write that in your script if you have chroot /target in front of the call to it
[21:16] <Goosemoose> well im removing the pushd, pop since that doesnt work
[21:16] <cjwatson> ARGH
[21:16] <cjwatson> no stop messing about
[21:17] <cjwatson> they will work if you do the late_command change (well, you also have to make sure the script starts with #! /bin/bash rather than #! /bin/sh)
[21:17] <Goosemoose> ok
[21:17] <Goosemoose> sorry, new to this preseed.cfg, worked on it once a year ago
[21:17] <cjwatson> change one thing at a time; standard troubleshooting practice
[21:17] <Goosemoose> ok
[21:18] <cjwatson> when I advise you to try something, try that first *on its own* before making further changes
[21:18] <Goosemoose> just have to wait 30 min inbetween installs so trying to knock out a few issues
[21:18] <Goosemoose> ok, will do
[21:18] <cjwatson> (or when another developer advises you)
[21:18] <cjwatson> do check the #! line at the start of your script, though
[21:18] <Goosemoose> yup, just did, thanks
[21:18] <cjwatson> right, the problem is that if you change lots of stuff at once then you might actually make it worse
[21:18] <Goosemoose> yeah i understand
[21:20] <Goosemoose> one other quick question. to get edubuntu desktop to load
[21:20] <Goosemoose> i've tried: tasksel tasksel/first multiselect standard, edubuntu-desktop
[21:20] <Goosemoose> but i just boot to terminal
[21:21] <Goosemoose> if i add ubuntu-desktop then it boots to ubuntu desktop
[21:22] <Goosemoose> nvm, ill try and at least get the other stuff working first, brb
[21:24] <cjwatson> that should be the right syntax
[21:24] <cjwatson> although of course won't work if you're installing from an Ubuntu CD
[21:25] <Goosemoose> edubuntu split on to two cd's now
[21:25] <Goosemoose> the first cd is ubuntu only
[21:25] <cjwatson> you can omit "standard, ", actually - that's installed automatically
[21:25] <Goosemoose> im installing from the network
[21:25] <cjwatson> yes, I know, I did most of the work for that
[21:25] <Goosemoose> ahh cool
[21:26] <cjwatson> again, /var/log/installer/syslog should let me see why edubuntu-desktop isn't getting installed
[21:26] <Goosemoose> ok
[21:26] <Goosemoose> i downloaded the netboot.tar.gz off ubuntu.com
[21:26] <Goosemoose> i restarted the install, so i'll have to wait until it's done
[21:35] <Goosemoose> cjwatson, a long time ago I had asked you how to get the installer to ask me the computer name and you had me unpack and make a change to initrd. that worked in fiesty but not in hardy. i read on a site online that i could change the default install line to include: netcfg/get_hostname=hostname and then pass the computer name in via the installer line. but that didn't work. was the site wrong? (install is still running btw
[21:37] <cjwatson> that's a long-standing bug; you have to work around it by fixing up the files in late_command
[21:37] <cjwatson> https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/218965
[21:37] <cjwatson> the site was right as to intent but wrong in that AFAIK it's never actually worked
[21:38] <Goosemoose> figures, lol
[21:39] <Goosemoose> several of these things have been driving me nuts for days, i forgot all about the ubuntu-installer room and the server room didn't have answers
[21:39] <Goosemoose> i just needed to find you!
[21:40] <Goosemoose> ok so the change you had me made previous was to comment out the set_network call in the dhclient-script file
[21:40] <Goosemoose> that was a year ago with feisty, but that function doesn't exist
[21:40] <Goosemoose> there's a set_hostname
[21:41] <Goosemoose> i tried commenting that out and rebuilding but it didn't make the prompt appear
[21:41] <Goosemoose> (doesn't exist now in hardy i mean)
[21:51] <Goosemoose> cjwatson, ok the late_command exited with an error code 1
[21:51] <Goosemoose> im pasting it into pastebin
[21:52] <Goosemoose> http://pastebin.com/d3cdfdd76
[21:55] <Goosemoose> cjwatson, let me know when you're back around please
[22:31] <xivulon> cjwatson 268123 is fixed now, thanks a bunch, looking forward to see the new busybox in the iso
[22:58] <cjwatson> Goosemoose: there's no sign of a failure there; please remove the 2>&1 so that errors are visible
[22:58] <cjwatson> >/dev/null 2>&1 throws away both output and errors, >/dev/null just throws away output
[22:59] <cjwatson> Goosemoose: what I advised somebody to do recently wasn't anything in dhclient-script, but was just to adjust /etc/hostname, /etc/hosts, and /etc/resolv.conf in their late_command script; I suggest you do that
[22:59] <cjwatson> xivulon: good stuff
[23:02] <Goosemoose> ok
[23:03] <Goosemoose> cjwatson, the problem with that is that im doing this to 250 machines, so i can't hard code anything
[23:03] <Goosemoose> in to the hosts files
[23:04] <Goosemoose> editing the preseed.cfg and reinstalling now
[23:09] <cjwatson> Goosemoose: in that case I would recommend that you configure your DHCP server such that the installer's automatic guesswork gets it right
[23:09] <cjwatson> that's by far the easiest method long-term
[23:10] <Goosemoose> ok, guess i'll have to do that then
[23:10] <Goosemoose> im reinstalling right now withou the null statement
[23:10] <Goosemoose> i couldnt find anything about the edubuntu-desktop in the syslog but it's long, i could have missed it
[23:11] <cjwatson> if you post the whole thing, I have lots of practice at looking
[23:11] <cjwatson> I'm going to bed soon though
[23:12] <Goosemoose> ok, i might have to hit you up tomorrow, i'll be another 20 min before the current install finishes
[23:13] <Goosemoose> thank you for all your help
[23:13] <cjwatson> ok
[23:20] <Goosemoose> ok got to the error
[23:27] <Goosemoose> damn it failed on both commands
[23:28] <Goosemoose> cjwatson, if you're still around: http://pastebin.com/d32527b4c
[23:28] <Goosemoose> it looks like for joining the domain is says it was unable to start daemon
[23:29] <Goosemoose> so likewise-open hadn't started yet
[23:29] <Goosemoose> i guess i need to force it to start in the script first
[23:29] <Goosemoose> but would i do /etc/init.d/likewise-open start; or /target/etc/init.d/likewise-open start;