[03:25] at some point did things switch around so that ubiquity doesn't run the whole process as root? [03:26] yes [03:27] sorry, I should've told you that [03:27] whew that's not good, a lot of my scripts broke [03:27] my apologies [03:27] hopefully not a big deal.. [03:27] well going forward you can control what gets run as root and what doesn't [03:28] obviously some things need to run as root [03:28] were these very recent commits (i'll look over the history to see what you adjusted for items) [03:28] I'll get you the exact revno [03:29] bzr diff -r2464..2465 | vim - [03:29] should give you most of it [03:29] there was one or two changes after that [03:30] okay great thanks, i'll let you know if i have some difficulties switching things around [03:30] yeah, please do [03:30] best of luck [03:30] thx [04:02] ubiquity: superm1 * r2481 ubiquity/ (debian/changelog ubiquity/frontend/mythbuntu_ui.py): adjust permissions before/after launching external applications from ubiquity [04:03] luckily very easy fix :) [04:03] yay [05:50] cjwatson_: if you have a free moment today, can you take a look at the current state of ubiquity-dm? I'm not entirely confident in the approach and I'd like the reassurance of a trained eye. [05:50] and yay, CIA is down [05:50] * evand kicks CIA-44 [05:50] ow [06:02] evand, you weren't really consistent with spacing in ubiquity-dm changes. i'm making a few other changes to that file right now, i'll clean those up for you [06:04] oh? Thanks [06:11] ubiquity: superm1 * r2483 ubiquity/ (4 files in 2 dirs): add mythbuntu to list of possible frontends to look for upon ubiquity startup [06:11] ubiquity: superm1 * r2484 ubiquity/ (bin/ubiquity-wrapper debian/changelog): check for jockey-gtk instead of restricted-manager [10:39] If anyone would like to help review the english text in wubi/umenu please see the following 2 files: [10:39] http://bazaar.launchpad.net/~ubuntu-installer/wubi/hardy/annotate/agostino.russo%40gmail.com-20080225023058-shsf3oawibio0nxt?file_id=english.nsh-20070529205356-9mvslu0v3aodhtoy-1 [10:40] http://bazaar.launchpad.net/~ubuntu-installer/umenu/devel/annotate/evand%40ubuntu.com-20080220141346-5prmrb6va03jdtw1?file_id=english.nsh-20080212233008-kvy2sm0usmkk5nf3-18 [10:40] shouldn't take more than 5m [12:15] installation-guide: cjwatson * r409 ubuntu/ (656 files in 174 dirs): merge from Debian 20080211 [12:18] installation-guide: cjwatson * r410 ubuntu/en/appendix/chroot-install.xml: adjust chroot-install for Ubuntu sources.list [12:40] installation-guide: cjwatson * r411 ubuntu/ (10 files in 5 dirs): [12:40] installation-guide: * Bump kernelversion to 2.6.24. [12:40] installation-guide: * Bump GNOME version to 2.22. [12:40] installation-guide: * Bump release version and names for Hardy. [12:57] installation-guide: cjwatson * r412 ubuntu/debian/changelog: releasing version 20080211ubuntu1 [13:11] cjwatson, evand, is there any interest in having lupin-casper ported to the alternate ISO? [13:11] That would be mostly to support loopinstallations for distros that do not come with a live CD. [13:12] If that is something you would like to see, I'd be glad to work on an implementation. [13:32] xivulon: well, I did partman-auto-loop as a udeb for a reason; but there's no rush for hardy, I think there are probably more important things to work on for that [13:33] speaking of which [13:33] evand: I diagnosed bug 188492 - comment in the bug [13:33] Launchpad bug 188492 in ubiquity "console-setup/layoutcode settings are ignored" [Medium,Confirmed] https://launchpad.net/bugs/188492 [13:48] cjwatson, I was thinking of doing it using a udeb anyway, when you say that there is no rush for hardy, do you mean we should target hardy+1? [13:49] for me too is a low priority, I have a few crashes to debug first... [13:49] thanks for 188492 by the way [13:51] xivulon: that's what I meant, yes [13:52] I want the hardy installer to be really stable and don't want to rush many more features into it [13:52] np [13:59] ubiquity: jriddell * r2486 trunk/debian/changelog: set me in changelog [14:02] cjwatson: oh wow, whoops. Thanks for catching that. [14:03] cjwatson: did you happen to see my comments earlier in the day about ubiquity-dm? [14:04] evand: yeah, I wasn't sure exactly what was bothering you though? [14:05] running X as root still. I'm not sure if there are any side-effects of that. [14:05] you pretty much have to, surely [14:05] I think that's fine [14:05] oh? [14:05] ok, works for me [14:05] direct hardware access ... [14:06] the one thing that jumps out at me is chmodding the dm log file to 666 [14:06] what's with that? [14:06] ah, right [14:06] oh, and strictly we should fish HOME out of getpwnam too, although IIRC ubiquity has the same buglet in other places too [14:07] and chmodding 666 so that "ubuntu" can write to it. [14:07] as a style point I would prefer 'import pwd' and 'pwd.getpwnam' just to make it clear where that function is coming from [14:08] chmod> shouldn't be necessary if you pass the fd around; it opens it with elevated privileges, doesn't it? [14:08] you can be handed an fd by root that you wouldn't be able to create yourself [14:08] the file mode just governs new opens [14:08] I thought that was the case, but my testing seemed to prove otherwise [14:08] I'll take another look [14:09] something else going wrong then, I guess [14:09] not a big deal under the circumstances, just jumped out [14:11] evand re english^ [14:12] whoa, how did the code behind bug 194688 ever work? [14:12] Bug 194688 on http://launchpad.net/bugs/194688 is private [14:13] uhh odd. I know I've seen it work for me. [14:13] it's only the popup menu that's broken [14:13] it passes two extra user parameters that on_partition_list_edit_activate doesn't expect [14:13] ah [14:13] r2452 broke it [14:14] I think you forgot to update the popup menu code too? [14:15] hrmm [14:15] though he says later on in the report that he actually meant to report a different bug he also encountered [14:15] ah looks like it, but how on earth did I not run into that in UI testing. argh. [14:17] two different ways to do it ... [14:18] ah [14:18] yikes, so far not a great morning [14:20] plenty of time before the next alpha ;-) [14:21] heh, that's one way of looking at it [14:21] xivulon: can you elaborate? [14:21] oh nevermind [14:21] I mentioned the 2 english files that would need to be reviewed as we discussed earlier, no rush whatsoever [14:22] indeed, I didn't see that at first [14:26] I'll take a look after I fix the above mess. [14:29] evand: is bug 77966 handled by your fix for bug 48355? IIRC your solution was fairly general in the end and covered both [14:29] Launchpad bug 77966 in ubiquity "MASTER: Should warn about insufficient disk space (manual partitioning)" [Medium,Confirmed] https://launchpad.net/bugs/77966 [14:29] Launchpad bug 48355 in ubiquity "MASTER: partitioner should warn about too small disk while autopartitioning (some_device)" [Medium,Fix released] https://launchpad.net/bugs/48355 [14:30] that would cover resizing as well, right? [14:33] eventually, though the resize might well fail first [14:35] I figured, though never looked, that commit.d is run in all cases, but I'm pretty sure I fed partman a partition size that was too small using the resize widget and it let me go through. [14:38] it isn't run at resizing time; it would be run later when you actually try to finish off the partitioner [14:38] CIA is slow today [14:38] better than last night when it didn't work at all [14:38] right, but I'm saying I got all the way through to an ENOSPC on that one, I think. [14:39] I should probably test again to be sure. [15:13] ubiquity: evand * r2489 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py): [15:13] ubiquity: * Update partman_popup with respect to other recent changes (LP: [15:13] ubiquity: #194688). [15:14] welcome back, CIA-24 [15:16] ubiquity: evand * r2490 ubiquity/debian/changelog: Whoops, make sure launchpad-bugs-fixed picks up the previous revno. [15:27] ubiquity: evand * r2492 ubiquity/ (debian/changelog ubiquity/components/console_setup.py): [15:27] ubiquity: * Regain root when moving /etc/default/console-setup out of the way [15:27] ubiquity: (LP: #188492). [15:28] does CIA just not like me? [15:29] ah, it would help if I set cia-project [15:29] I was switching over to a bzr repository and it got lost along the way [15:29] :) [15:29] ubiquity: evand * r2493 ubiquity/debian/changelog: Credit where credit is due. [15:29] ubiquity: cjwatson * r2487 ubiquity/ (debian/changelog partman/check.d/03partition_too_small): [15:29] ubiquity: * Slight shell efficiency improvement in [15:29] ubiquity: partman/check.d/03partition_too_small. [15:29] ubiquity: cjwatson * r2488 ubiquity/ (configure configure.ac): bump to 1.7.12 [15:29] ubiquity: cjwatson * r2491 ubiquity/ (37 files in 10 dirs): [15:29] ubiquity: * Use 'autoreconf -fi' so that Autotools files reliably get upgraded. [15:29] ubiquity: * Upgrade to gettext 0.17. [15:29] there you go [15:30] thanks! [15:45] xivulon: "Reboot into a new world..." sounds too evangelistic. Perhaps somewhat replicate the text from the button, "Try or install Ubuntu"? [15:45] Of course that suffers from the same problem that a few of the other strings have, that is explicitly naming the distribution. [15:47] ahah loved that sentence [15:51] I can name the disto by the way using a variable, at that stage I'd know the distro name anyway [15:51] Doesn't that get you in trouble with translations? [15:51] "Reboot and try ?buntu..." [15:51] Should be ok [15:52] If you look into wubi english.nsh there are a few $xxx variables within translation strings [15:52] I will put a note not to translate $stuff [16:00] I'd also change "booter" to "boot helper" [16:01] evan pull both and feel free to change the text directly [16:01] Access doesn't seem right, but I face the same problem when you asked me that originally. I cannot think of a word for acessibility that fits in such a small space. How many characters is the maximum for a button again? [16:01] ok [16:03] I will see if I can make the button larger, not sure about that. [16:04] assistive would probably be better if you can fit it. Though I wont make the change until we have confirmation of that. [16:06] user32::SetWindowPos might do the trick === cjwatson_ is now known as cjwatson [17:04] ubiquity: evand * r2494 ubiquity/ (bin/ubiquity-dm debian/changelog): * Minor changes to ubiquity-dm from suggestions by Colin Watson. [17:40] evand got a log from the amd64 user [17:40] http://ubuntuforums.org/showpost.php?p=4402468&postcount=6 [17:41] does not look to me like it is the same issue (freeze around console-setup), but the error is strange: [17:42] 1) no swap (not sure why, does that cause a failure-command by the way?) [17:42] 2) I/O error, dev fd0 (not sure if that is very relevant) [17:46] 3) unsupported locale setting (LANG=en_US)? [17:47] * xivulon likes failure-commands [17:48] ...would be even better if we could split out non critical warnings though... [17:50] "interactive" warnings that is [17:50] ubiquity: evand * r2495 ubiquity/ (debian/changelog desktop/ubiquity-gtkui.desktop.in): * Remove suffix from icon path in .desktop file (LP: #188221). [17:50] hooray for omni-completion. Thanks for hacking that up, cjwatson. [17:52] evand I was thinking that ubiquity should have 3 modes: interactive, automatic, semi-automatic. [17:53] the last if for wubi type installation where the user is not supposed to answer any question, but he might be shown a failure message. [17:53] after the failure message we can still trigger a failure-command [17:58] 1) because it's asking a question. As I explained in a post on ubuntuforums, we had intended to split failure_command into a complete failure and an "automation failure" (when ubiquity requires human interaction for something) [17:58] You can avoid this question by preseeding it away. [17:59] we had intended> I had intended to do it at the start of the Hardy cycle, but I completely forgot. It's fairly straightforward and I've added it to my todo list. [18:00] 2) No, don't worry about that. [18:00] oh, I missed that comma. [18:00] So yes, it does cause a failure_command. [18:02] back to 1) now that I've reread it [18:02] debconf (developer): <-- GET partman-auto-loop/recipe [18:02] debconf (developer): --> 0 /ubuntu/disks/root.disk 3000 30001 30001 ext3 method{ format } format{ } use_filesystem{ } filesystem{ ext3 } mountpoint{ / } . [18:02] so it looks like you're not preseeding swap creation in that case. [18:03] really not sure why, as I imagine that's always done in your code, not just sometimes. [18:05] 3) that should be en_US.UTF-8 [18:05] oh hrm [18:05] you do set it as that [18:08] hmm really strange, that should be in the preseed file [18:08] Maybe it would help to copy preseed.cfg config.dat (other?) in the failure-command zip file. [18:08] I mean swap recipe [18:09] preseed.cfg> That would end up pulling in their password. [18:09] 3) Isn't the preseeding supposeed to be "locale en_US"? [18:09] might sed the password out [18:10] would that be in config.dat too? [18:10] no, it wouldn't [18:10] but I don't really see the need [18:10] of config.dat? [18:10] indeed [18:10] I'll add a sedded preseed then [18:11] well, I don't see the need of either of them [18:11] you already have debug enabled [18:11] yes [18:11] but in the case above how would I know the exact recipe string? [18:12] evand: you're welcome [18:12] You'd look in debug, just as I did [18:12] preseeding should be en_US.UTF-8 not en_US [18:13] evand does that contain the original "raw" string? [18:13] Did we stop writing passwords to the debug output at some point? [18:13] no [18:14] cjwatson is the locale going to be *.UTF-8 for all languages? [18:14] xivulon: unfortunately not quite. You need to know the actual locale from /usr/share/i18n/SUPPORTED not just make it up [18:14] curious, I don't see the user's password in this debug log, and I doubt he stripped it out [18:14] I'd suggest incorporating that file in your build process somehow [18:15] will do [18:15] and xivulon doesn't appear to be sed'ing the passwords out of the debug log before zipping, as far as I can tell [18:15] ah duh [18:15] because it didn't get that far [18:15] ok yikes, so using debug is probably a bad idea [18:16] we've talked about enabling this by default before [18:16] evand I don't sed anything at the moment, just zip the whole /var/log [18:16] but the situation is even worse for wubi [18:16] because there's no bold text warning them that their password will be in the logs [18:16] right, debug mode definitely isn't appropriate for any kind of default [18:17] let me know if I need to exclude / sed any file in failure-command [18:18] I think you should not use debug mode by default and add a command line option to wubi that enables it. [18:18] that still doesn't address the lack of a warning in the UI that their password is going to be in the logs [18:20] cjwatson I am looking at SUPPORTED, for US I have en_US.UTF-8, en_US, and en_US.ISO-8859-15 [18:20] use the one with 'UTF-8' in the second column [18:20] evand you mean for failure-command? [18:21] or in general [18:21] re pwd in the logs, isn't it possible to simply sed it out? [18:22] you could if you're careful. I did ask about including a patch to debconf that makes it never be included, but Joey noted (rightly) that it was fundamentally utterly awful [18:22] I don't think so. The text could change and you'd end up missing the password. [18:23] we have had very high-profile installer vulnerabilities before regarding leaked passwords, and it deserves the highest possible level of care [18:23] you don't get away with this sort of thing a second time [18:24] I remember that news [18:26] do all language have a second column with UTF-8? I also noticed that some lanugages have multiple @ variants all with UTF-8 [18:27] what shall I do with the log? is an (english) warning sufficient? [18:28] I will copy the log only if the user selects debug mode at boot [18:34] re (ubiquity) debug, that is not really enabled by default [18:34] the user has to hit esc and select verbose mode [18:34] oh? [18:34] ah, I had no idea [18:34] is that good enough (+pwd warning)? [18:35] yeah, I think if you can fit it, a password warning would be great [18:35] "(password included in logs)" perhaps [18:35] hmm that should be localized too... bugger [18:36] the password is only in /var/log/installer/debug, correct? [18:36] all languages should have a UTF-8-encoded locale; if they don't you can safely ignore them [18:36] for ones with multiple variants containing @ or . there should be one without those modifiers and you should use that [18:36] ca_ES.UTF-8@valencia is the only one I can think of offhand [18:36] cjwatson thanks, will do that [18:36] oh, I see there are a few others [18:37] yes [18:37] but yeah, looking through them, it's fine to just use the unmodified version; I suspect Windows does not have much in the way of Valencian support anyway and I don't think d-i does either [18:38] by the way I'd need a mapping of windows registry keys to keyboard variants [18:38] I have the code to use that info, and dvorak in as an example [18:38] but not sure where to grab such mappings [18:38] I think somebody might have to invent them [18:40] There is an hkl value in the registry, for instance 0x00010409=dvorak [18:40] but do not know how to get the others [18:43] ah http://softserv.murdoch.edu.au/pub/mswin/Citrix/Citrix4.21.779/MODULE.SRC [18:58] there is also the issue of preseed.cfg [18:58] that countains the pwd [18:59] now it gets deleted upon successful installation [18:59] but not upon unsuccessful installation [18:59] should probably comment that in failure command too? [19:02] ubiquity: jriddell * r2496 trunk/ (debian/changelog ubiquity/frontend/kde_ui.py): Fix QApplication args in ubiquity/frontend/kde_ui.py === andrea-bs is now known as andrea-bs_ === andrea-bs_ is now known as andrea-bs [19:30] evand: I'm planning on adding some bugs to the DebuggingUbiquity Known issues section and possibly try to make the page look more like the DebuggingTemplate page. Does that sound alright to you? [19:32] bdmurray: works for me, thanks for doing it [19:32] evand what's your take on preseed.cfg password? ^ [19:36] hrm, yeah, I'd do what you can to strip it out in that event [19:39] hmm the issue is that in many case the user will try to reboot and select "Ubuntu" to redo the installation if something goes wrong [19:39] if I strip out stuff from preseed.cfg, then the user will need to start windows and reinstall again to regenerate a new preseed.cfg [19:39] hrmm, indeed. [19:40] preseed.cfg will be deleted on successfull wubi installation and of curse whenever wubi is uninstalled [19:40] the problem are is if wubi installation fails and the user just keeps it around [19:40] I guess we don't have any other option but to leave it in on a failed install then. [19:41] I could add a note in failure-command, but if the error happens before (grub4dos / initrd) the user will not see that [19:42] unless I split failure_command into failure_command and automation_failure_command. Then stripping the password out and showing the user-setup page wouldn't be an issue. [19:42] It'd be ugly though, as they wouldn't be expecting that. [19:43] you mean asking for username/password in ubiquity as opposed in wubi? [19:43] right [19:43] I'm not too keen on the idea though [19:43] don't get me wrong, I'd like to split failure_command [19:43] pros and cons, might be a bit late for that though [19:44] all it would take would be splitting failure_command. ubiquity already handles showing a page when you haven't adequately answered all of the questions. [19:45] I think we're fine with our current approach though, at least for the time being. [19:45] I asked cjwatson whether we should ask for username/pwd in ubiquity and he rejected the idea. [19:45] I guess also because it would look akward to have to go through 2 installer interfaces [19:46] But on the other side, that would make wubi a true 1 click installer, and I like that! [19:46] indeed, mind you only in the case where the install failed once, but still like I said, I'm not keen on the idea. [19:46] ah I see [19:46] Hmm I'd say either we do it always or never [19:47] I vote for never [19:48] wait a minute [19:48] don't you use MD5 hashes anyway? [19:48] yes [19:49] so then I'm confused [19:49] by what? [19:49] how is the password exposed in preseed.cfg? [19:49] in hashed form [19:50] so the fact that preseed stays around on failure is half damage [19:51] half damage? [19:51] I don't think there's anything to worry about if you're using user-password-crypted. [20:01] what are the permissions on preseed.cfg? [20:02] debian-installer-utils: evand * r650 ubuntu/ (debian/changelog update-dev): [20:02] debian-installer-utils: * Avoid sound events as they will trigger audio to be played on every [20:02] debian-installer-utils: call to udevtrigger; udevsettle (LP: #178057). [20:05] cjwatson do you mean on the windows side? I think anyone can read it [20:05] can it be given stricter NTFS permissions somehow? [20:06] can try that [20:06] not that I think that will limit an attacker ability to access it anyway... [20:08] right, but if they have sufficient access on the Windows side they can do whatever they want anyway [20:08] what I want to avoid is the file being left around such that unprivileged users created on the Ubuntu side can read it [20:09] but if it's only on failed installs anyway, it's not a big deal [20:09] yeah I'd skip that if possible it would involve adding an ACL plugin just for that [20:17] debian-installer-utils: evand * r651 ubuntu/debian/changelog: releasing version 1.50ubuntu2 [20:26] evand: are there test cases documented for testing Wubi? Actually is it testable yet? [20:27] bdmurray: It is testable, there are no documented test cases yet. [20:28] umenu should also replace WinFOSS testing [20:29] In the test lists at iso.qa.ubuntu.com? [20:29] yes, WinFOSS is no longer used. [20:30] I'll add Testing/Cases/umenu and Testing/Cases/Wubi pages to the wiki if you'd like. [20:31] evand: that'd be great and I'll get them added to the iso testing tracker [20:32] how do those tests work? can I help on my side? [20:32] Is that arch specific at all? [20:32] sure [20:32] amd64 and i386 [20:33] works on both kubuntu and ubuntu (edubuntu is now an add on CD) [20:34] xivulon: The test cases are linked from http://iso.qa.ubuntu.com . bdmurray can talk to stgraber to get them added. The tests themselves are on the wiki [20:34] https://wiki.ubuntu.com/Testing/Cases [20:34] * xivulon reading [20:35] evand: I'll need to rework the testcases list anyway, so just put a list of what's wanted on the wiki Testing/TrackerUpdate (or something similar) or e-mail me [20:35] ah those are human tests [20:35] (following the Edubuntu changes and LTSP being now part of Ubuntu Alternate) [20:35] re Edubuntu I do have it in the wubi list of desktops [20:35] stgraber: ah, I had no idea you were in here :). Will do. [20:36] is it available as a Live ISO so that it can be targeted by wubi? [20:37] I mean I can see: http://cdimage.ubuntu.com/edubuntu/daily-live/current/ [20:38] and http://cdimage.ubuntu.com/edubuntu/releases/8.04/alpha-5/ [20:39] first link seems to indicate a full ISO, second link an addon [20:40] I'm not sure how long cdimage will continue to generate full live CD images. [20:40] ah pls let me know, in case we have to take it out of wubi [20:41] I hope they'll keep doing full CDs of course [20:46] well, the live CD for edubuntu isn't that usefull as we don't have enough place on it to put the educational softwares [20:47] and it ends up being just an ubuntu with a different artwork [20:47] the add-on CD contains all the educational stuff and is then installed on a standard Ubuntu [20:47] so if we wanted to install everything out of the box we would need ~900MB on the LiveCD (as the add-on contains ~200MB of usefull stuff at the moment) [20:48] stgraber: 900MB would not be an issue for wubi since no CD is burnt ;) [20:48] but of course that would be too much of a special case I guess [20:49] 15:45:28 < slangasek> my understanding was that edubuntu desktop would remain a discrete image, only server was being rearranged into an ubuntu-server adjunct? [20:49] so my understanding is that it will be around but not too usueful because of lack of packages [20:49] yes, we'll keep edubuntu desktop, it'll just be as usefull as it was in Gutsy [20:50] my point is that someone uses wubi to demo edubuntu might get the wrong impression since it won't be fully loaded [20:50] 15:50:06 < slangasek> evand: that's my understanding; plans may have changed when I wasn't looking [20:51] gotcha [20:51] for me it's fairly easy to add/remove distros, and I am not binded by ISO size restrictions, just let me know what you want to have in! [20:53] I'll let stgraber and the rest of the edubuntu people speak for their distribution and needs. [20:53] and its* [20:53] absolutely, stgraber, let me know what you decide [20:53] and then I can flip the necessary bits on cdimage, if any changes are needed [20:54] xivulon: we have a meeting this wednesday at 12:00 UTC. I'll ask here (you can also attend it depending on your timezone) [20:55] I'll try to. [20:55] as mentioned, 900MB ISO, is still an option as far as wubi go [21:32] evand: was bug 48355 fixed in dapper updates or just Hardy? [21:32] Launchpad bug 48355 in ubiquity "MASTER: partitioner should warn about too small disk while autopartitioning (some_device)" [Medium,Fix released] https://launchpad.net/bugs/48355 [21:32] hardy [21:32] That's weird the comment on the wiki pages says it was fixed in 6.06.1 [21:33] perhaps a different bug? Or does it explicitly reference that bug number? [21:34] That number explicity, I'll change it though. [22:22] evand: do you know what happened to the notes from the USB stick production thing we discussed at UDS? [22:23] xivulon: we've already stopped doing full Edubuntu CDs; the desktop is just an accidental hangover that nobody has got round to disabling yet, AFAIK [22:23] bdmurray: we probably ameliorated it in 6.06.1 [22:25] cjwatson, I cannot do multiple ISO installations at this stage, if edubuntu is to be added the only option is to have a 900MB ISO [22:25] cjwatson: I'll look through my laptop for it. [22:25] xivulon: you wouldn't have to. They install Ubuntu using wubi, then use the edubuntu addon CD. [22:26] yeah that would be good enough [22:26] bdmurray: I seem to have added that text deliberately but it was a long time ago [22:26] I will remove edubuntu then [22:26] evand: ta [22:26] the gobby notes may be available from IS if need be [22:26] re USB stick, I have vague memories and remember that Wubi was involved somehow [22:26] can you remind me briefly what was the objective? [22:27] * cjwatson -> bed, sorry, wife will be annoyed otherwise :) [22:27] another day [22:27] (it's not urgent) [22:27] sure [22:27] I'll be glad to hack something together anyway [22:29] I'll wait wednesday meeting before removing edubuntu from wubi, I guess there is no rush [22:34] cjwatson quick q [22:34] might be good to use low swappiness as well?