[09:30] <davmor2> morning xivulon cjwatson and a happy new year :)
[10:00] <cjwatson> morning
[10:00] <xivulon> happy new year davmor2 and all the rest! :)
[10:17] <TheMuso> Happy new year all, hope everyone had a refreshing break.
[13:42] <arthur_l> hi
[13:42] <arthur_l> i'm looking for help on driving partman from d-i
[13:42] <arthur_l> am I in the right place ?
[13:43] <cjwatson> yes
[13:43] <cjwatson> what's up?
[13:44] <arthur_l> I would like have an if (i have 1 disk) do this, else if (i have 2 disks) do somethingelse, else do that
[13:46] <arthur_l> cjwatson: do you know if that's possible ?
[13:46] <cjwatson> version of Ubuntu?
[13:46] <cjwatson> (it's possible either way, just affects complexity)
[13:46] <arthur_l> 8.0.4
[13:47] <cjwatson> (that's 8.04)
[13:47] <arthur_l> indeed
[13:47] <arthur_l> my fingers slipped
[13:47] <cjwatson> ok, so you get the more complex option :-/
[13:47] <_MMA_> Hi all.
[13:48] <arthur_l> cjwatson: where should i be looking ?
[13:48] <_MMA_> cjwatson: Any ETA on enabling the new Alt installer?
[13:48] <_MMA_> (in Jaunty)
[13:49] <cjwatson> arthur_l: here are the pieces you need: preseed/early_command specifies a script to run towards the start of installation (although not necessarily after disks are detected); if you write an executable script from there into /lib/partman/display.d/00yournamehere, then that script will be executed just before the partitioner starts; you can use list-devices to output the available disks; you can use debconf-set or ...
[13:49] <cjwatson> ... debconf-set-selections to dynamically preseed things
[13:49] <cjwatson> arthur_l: (8.10 simplifies the first two into partman/early_command)
[13:49] <cjwatson> _MMA_: can you be more verbose please/
[13:49] <cjwatson> ?
[13:49] <cjwatson> what "new alternate installer"?
[13:50] <_MMA_> cjwatson: Sorry. The GTK one.
[13:50] <cjwatson> no ETA, GTK/directfb is busted
[13:50] <_MMA_> Um... Unsure the exact name.
[13:50] <_MMA_> Ahhh. Ok. Thanx for the info.
[13:50] <arthur_l> cjwatson: thanks... I'll looking into that (stuck with 8.04 unfortunately)
[13:50] <cjwatson> it crashes messily on startup
[13:52] <_MMA_> cjwatson: Barring that, is there any info as to what's needed/involved for customization? Since I'm still learning about it, I'm unsure as to what to search for.
[13:52] <cjwatson> _MMA_: what sort of customisation/
[13:52] <cjwatson> ?
[13:52] <cjwatson> damn that shift key anyway
[13:54] <_MMA_> cjwatson: Well I assume there's a certain amount of branding involved. Correct? So I'm looking into it to make sure Studio is ready.
[13:56] <cjwatson> _MMA_: there'll be no information on customisation until it actually boots at all, which may not be for jaunty
[13:56] <cjwatson> so I wouldn't put the cart before the horse :) customisation is the least of my worries at the moment ...
[13:58] <_MMA_> cjwatson: Oh sure. Sure. I'm not trying to *do* anything now. Other than gather info on how it's *supposed to work. I don't wanna get caught at the last min on this. I'll bug you later in the cycle. Or maybe next UDS. (If you attend) :)
[13:59] <cjwatson> I honestly don't know myself yet; I had been planning to look into it after it actually works. All I know is that it's all in the rootskel-gtk package; I hadn't been expecting it to be all that hard to customise
[13:59] <cjwatson> ... and therefore hadn't been worrying about preparing in advance
[13:59] <arthur_l> i have the d-i svn checkedout but which revision is used for 8.04 ?
[13:59] <arthur_l> is there a branch ? tag ?
[13:59] <_MMA_> cjwatson: np. Thanx for the info.
[14:01] <cjwatson> arthur_l: not in svn at all. http://wiki.ubuntu.com/InstallerDevelopment
[14:01] <arthur_l> or should i use the bzr
[14:02] <cjwatson> there is no easy way to get "whatever was in 8.04" short of apt-get source, I'm afraid; although no doubt one could put it together using bzr
[14:03] <arthur_l> cjwatson: thanks
[16:22] <CIA-3> debian-installer: cjwatson * r930 hardy-proposed/ (9 files in 4 dirs): Move to 2.6.24-23 kernels.
[16:32] <CIA-3> debian-installer: cjwatson * r931 hardy-proposed/debian/changelog: releasing version 20070308ubuntu40.7
[17:00] <CIA-3> partman-md: cjwatson * r909 ubuntu/ (debian/changelog init.d/md-devices):
[17:00] <CIA-3> partman-md: init.d/md-devices: Check for the existence of /dev/md as well as
[17:00] <CIA-3> partman-md: /proc/mdstat before exiting early, in order to cope with kernels where
[17:00] <CIA-3> partman-md: md-mod is built-in.
[17:01] <CIA-3> partman-md: cjwatson * r910 ubuntu/debian/changelog: bug reference
[17:04] <CIA-3> partman-md: cjwatson * r911 ubuntu/debian/control: Maintainer and Vcs-Bzr for Ubuntu
[17:19] <CIA-3> mdcfg: cjwatson * r1072 ubuntu/ (debian/changelog mdcfg.sh):
[17:19] <CIA-3> mdcfg: Do initial scan if /dev/md is missing as well as if /proc/mdstat is
[17:19] <CIA-3> mdcfg: missing, in order to cope with kernels where md-mod is built-in
[17:19] <CIA-3> mdcfg: (LP: #309555).
[17:21] <CIA-3> mdcfg: cjwatson * r1073 ubuntu/debian/control: Maintainer and Vcs-Bzr for Ubuntu
[17:30] <CIA-3> partman-md: cjwatson * r912 ubuntu/debian/changelog: releasing version 44ubuntu1
[17:41] <CIA-3> mdcfg: cjwatson * r1074 ubuntu/debian/changelog: releasing version 1.28ubuntu1
[19:17] <kirkland> cjwatson: hi, i just downloaded and installed from the jaunty-server-amd64 daily iso
[19:17] <kirkland> cjwatson: it seems that you disabled the encrypt-my-home-directory screen
[19:17] <kirkland> cjwatson: i think the relevant bits are in the kernel now
[19:18] <kirkland> cjwatson: i'd like to test it in tomorrow's daily build
[19:18] <kirkland> cjwatson: could you, per chance, re-enable that code?
[19:22] <kirkland> cjwatson: actually, i have mispoken
[19:22] <kirkland> cjwatson: it's not in the kernel on the installer yet :-(
[19:38] <kirkland> cjwatson: well, that's not necessarily true ... rtg says that they're built in
[19:38] <kirkland> cjwatson: and i know we've gone in circles about this for several weeks now, builtin vs. crypto-modules-udeb
[20:19] <phobiac> I'm having a problem with the ubuntu installer that I thought I should ask the developers. Is anyone there?
[20:20] <kirkland> phobiac: ask your questions, and someone will answer, if they know
[20:21] <phobiac> Okay. During the install process, it doesn't auto detect my hard drive and asks me what driver to use. It's a Toshiba MK6028GAL ATA device according to windows, any ideas on what driver I should use?
[20:21] <kirkland> phobiac: what version of ubuntu?
[20:21] <phobiac> The newest, I'm trying to to a netboot install over the internet.
[20:21] <phobiac> to do
[20:22] <kirkland> do you mean the one that's under development right now?
[20:22] <kirkland> or the newest one to have officially released?
[20:22] <phobiac> No, intrepid.
[20:22] <kirkland> ah
[20:22] <kirkland> phobiac: that's an odd error
[20:22] <kirkland> phobiac: is this a notebook or a desktop?
[20:22] <phobiac> It's notebook, or I guess a "netbook"
[20:23] <phobiac> Fujitsu U820
[20:23] <phobiac> It doesn't have a built in CD/DVD drive, so I figured netboot over internet was the easiest way to go.
[20:24] <kirkland> yeah
[20:24] <kirkland> it should just be a simple ATA disk driver
[20:25] <phobiac> Should I just pick whatever driver has ATA in the name?
[20:25] <kirkland> what are your options?
[20:25] <phobiac> Is it possible to break the HD or mess it up if I choose the wrong driver and try to partition it?
[20:25] <phobiac> It gives me a huge list of drivers
[20:26] <kirkland> if you pick the wrong driver, the hard drive just won't show up in the installer
[20:26] <kirkland> until you find the right driver
[20:26] <phobiac> Okay. I'll just go through the list then. I should look for something with ata though?
[20:27] <kirkland> phobiac: sure.  what's odd is that it's not autodetected already for you....
[20:28] <phobiac> I've looked around on the internet, and it's a ZIF drive if that changes anything.
[20:28] <cjwatson> kirkland: OK, not right now, but I'll have a look in a bit
[20:28] <phobiac> Yeah, I don't understand how it can even read the files if it doesn't know what driver to use?
[20:28] <cjwatson> phobiac: it's very unlikely that any selection from that list will help you
[20:29] <kirkland> cjwatson: thanks.  i'd really like to syncronize about this as soon as possible
[20:29] <kirkland> cjwatson: so that it doesn't slip another alpha
[20:29] <cjwatson> phobiac: it can read the initial installer code because the BIOS does that; the problem is in getting Linux to do it
[20:29] <phobiac> cjwatson: Oh. What should I do then?
[20:29] <kirkland> cjwatson: i think a 3-way conversation, among you, me, and rtg would be beneficial
[20:29] <cjwatson> phobiac: the easiest way to help us fix this is to boot a desktop CD, then run 'sudo lspci -vvnn' and post the output
[20:29] <cjwatson> phobiac: it may just be that we need to tweak some simple things to get the driver delivered to the installer
[20:30] <cjwatson> (I'm off to watch Heroes now though, so stick around ...)
[20:30] <phobiac> It doesn't have a CD drive and I have no external one, would running the live CD in a virtual environment work the same?
[20:30] <cjwatson> no
[20:30] <cjwatson> you could try running 'lspci -vvnn' from alt-f2 in the installer environment
[20:30] <cjwatson> you then just have to get the output out of it somehow
[20:31] <cjwatson> running 'anna-install openssh-client-udeb' will get you scp, if that helps
[20:31] <phobiac> Alright, I can just hand type it out into pastbin.
[20:31] <cjwatson> it'll take a while
[20:31] <cjwatson> but if you have plenty of patience, sure
[20:32] <phobiac> Thanks for your help.
[20:32] <kirkland> cjwatson: heroes airs early for the UK?
[20:32] <cjwatson> 'lspci -n' is shorter and less convenient for us, but possibly more convenient for you to type out
[20:32] <cjwatson> kirkland: DVD
[20:32] <kirkland> cjwatson: its not on here for another 5.5 hours!
[20:32] <kirkland> cjwatson: oh :-)
[20:33] <kirkland> cjwatson: i'll try to ping you very early my time tomorrow, to sync about encrypt-home in the installer/kernel bits
[20:33] <cjwatson> kirkland: I'll look at it later today, it may not require any further kernel action
[20:33] <cjwatson> if it's built-in, it shouldn't require any further kernel action
[20:34] <kirkland> cjwatson: rtg says it's builtin as of -4.5
[20:34] <cjwatson> then that should be enough, let me poke at it
[20:34] <kirkland> cjwatson: in my vm, the installer kernel says 2.6.28-4-generic
[20:34] <kirkland> cjwatson: but cat /proc/crypto seems to disagree
[20:34] <kirkland> cjwatson: i need the cbc and ecb crypto drivers
[20:36] <phobiac> Is there a specific lspci entry you want? I can try to find just the section about the disk drive.
[20:36] <cjwatson> if you can, yes
[20:36] <cjwatson> I basically just need the ID of the disk drive so I can look up what driver is supposed to drive it
[20:36] <phobiac> Ah okay
[20:36] <cjwatson> (but in general we just ask for the whole output since that saves on back-and-forth)
[20:37] <kirkland> phobiac: hit ctrl-alt-f2
[20:37] <kirkland> phobiac: anna-install openssh-client-udeb
[20:37] <kirkland> phobiac: lspci -vvnn > /tmp/out
[20:37] <kirkland> phobiac: scp /tmp/out you@somewhere:/tmp
[20:38] <kirkland> phobiac: and pastebin that
[20:38] <phobiac> kirkland: I'll try that
[20:39] <phobiac> When I do anna-install openssh-client-udeb, it doesn't give me an output.
[20:39] <kirkland> cjwatson: fyi, encrypted LVM is not working (yet) in the daily jaunty server build
[20:39] <phobiac> The screen acts like I typed clear
[20:39] <kirkland> phobiac: do you have the scp command at your disposal now?
[20:39] <phobiac> scp: not found
[20:40] <phobiac> Oh wait
[20:40] <phobiac> I'll try configuring the network.
[20:43] <phobiac> No, that didn't work either.
[20:46] <phobiac> Is there a way to pause the output or something?
[20:46] <phobiac> lspci -vvnn is too large, I lose it about halfway through when I scroll back up.
[20:57] <phobiac> cjwatson, kirkland: http://pastebin.com/m5a03e4bf That's the output of lspci -n
[20:58] <kirkland> phobiac: can you do lspci -vvnn ?
[20:58] <kirkland> phobiac: that's more verbose
[20:59] <phobiac> Yeah, but I lose the output about halfway through.
[20:59] <phobiac> I can do lspci -v
[20:59] <kirkland> phobiac: what about -vv ?
[21:00] <phobiac> Nope, I lose it about halfway again.
[21:00] <kirkland> phobiac: "lose it" ?
[21:01] <phobiac> The buffer isn't large enough, I think that's what it's called? When I shift+pageup to go back, it only goes back so far.
[21:01] <kirkland> phobiac: redirect to file
[21:01] <kirkland> lspci -vvnn > /tmp/out
[21:01] <CarlFK> cjwatson:  https://bugs.edge.launchpad.net/ubuntu/+source/debconf/+bug/313950
[21:03] <phobiac> kirkland: That worked, how do I read the file though?
[21:03] <phobiac> Oh wait, I have scp now.
[21:03] <kirkland> yup
[21:03] <kirkland> phobiac: and you can use cat /tmp/out | more
[21:03] <kirkland> phobiac: or nano /tmp/out
[21:03] <CarlFK> kirkland: http://dev.personnelware.com/carl/a/isshd.sh  script I use to install ssh and keys into the installer
[21:04] <phobiac> kirkland: What was it you wanted me to use scp for? I'm not sure what the command does, what do I put in the you@somewhere part?
[21:04] <phobiac> Oh duh, cat and nano.
[21:04] <CarlFK> kirkland: http://dev.personnelware.com/carl/a/e18/cpl.sh  script to tar/scp everything that might be useful
[21:05] <CarlFK> oh wait.. who has the bugy box?
[21:05] <kirkland> CarlFK: phobiac is the one
[21:06] <kirkland> phobiac: scp copies files
[21:06] <CarlFK> opps.
[21:06] <kirkland> phobiac: do you have another Linux machine on your network, running ssh?
[21:06] <kirkland> phobiac: if so, you can use scp to copy /tmp/out to another machine
[21:07] <phobiac> kirkland: I have the one you're talking to me on right now, I don't think I have ssh on it though.
[21:07] <kirkland> phobiac: is it Ubuntu?
[21:07] <phobiac> kirkland: Yes
[21:07] <kirkland> phobiac: if so, 'sudo apt-get install openssh-server'
[21:07] <kirkland> phobiac: then get your ip address, with 'ifconfig'
[21:08] <kirkland> phobiac: then, from the machine you're installing, do:
[21:08] <kirkland> phobiac: scp /tmp/out your-username@your-ip-address:/tmp
[21:08] <kirkland> phobiac: you need to figure out the values of your-username and your-ip-address
[21:10] <phobiac> kirkland: On the buggy box, when it asks for my password for ssh do I give it my user logon password?
[21:10] <phobiac> That worked
[21:12] <phobiac> kirkland: http://pastebin.com/m1a5e6b7f That's the output of lspci -vvnn
[21:12] <kirkland> phobiac: excellent, that's what cjwatson needs
[21:12] <kirkland> phobiac: now, for bonus points, and to ensure that cjwatson doesn't loose it, i'd suggest filing a bug report in Launchpad ;-)
[21:12] <phobiac> kirkland: Okay.
[21:13] <kirkland> phobiac: otherwise, you're just "hoping" that cjwatson comes back after Heroes and notices your message in IRC
[21:13] <kirkland> phobiac: Launchpad would ensure that he takes care of it
[21:13] <phobiac> kirkland: I'll file one then.
[21:13] <kirkland> phobiac: https://bugs.edge.launchpad.net/ubuntu/+source/debian-installer/+filebug
[21:13] <kirkland> phobiac: attach that output to the bug
[21:15] <phobiac> kirkland: What should I name the bug?
[21:15] <kirkland> phobiac: Fujitsu U820 Hard Disk not detected by the installer
[21:16] <kirkland> phobiac: or something like that
[21:16] <phobiac> kirkland: I'll go with that
[21:17] <phobiac> Should I put the actual output, or the link to pastebin?
[21:20] <phobiac> I'll just put both.
[21:21] <phobiac> kirkland, cjwatson: https://bugs.edge.launchpad.net/ubuntu/+source/debian-installer/+bug/314175 That's the bug, is there anything else I should put into it?
[21:24] <phobiac> I have to go. Thank you for your help, if there's anything else I can do to help out with the bug just contact me through launchpad or something.
[22:24] <kirkland> cjwatson: actually, good news ...
[22:24] <kirkland> cjwatson: i dropped to a command shell in the installer and did "adduser --encrypt-home foo1"
[22:24] <kirkland> cjwatson: that seemed to work well
[22:24] <kirkland> cjwatson: so if possible, please re-enable the encrypt-home debconf question
[22:30] <cjwatson> kirkland: ok, will do
[22:30] <kirkland> cjwatson: thx much!
[22:30] <cjwatson> kirkland: some build system context might help you for the kernel confusion you had
[22:31] <cjwatson> kirkland: firstly, I've probably said in the past that the installer kernel is an exact copy of the kernel in the archive (and modules are spread out among various other udebs, and built into the initrd)
[22:31] <cjwatson> kirkland: what I may not have said is that the kernel is not copied afresh from the archive on each CD build
[22:31] <cjwatson> kirkland: it's only copied when the debian-installer source package is built, by way of an ordinary source upload; and then CD builds fetch the pieces from its output
[22:32] <cjwatson> kirkland: so put that together with the fact that d-i was last built against the *first* kernel in the -4 series, and that the set of things built in has changed throughout the -4 ABI series - and that explains the discrepancies you're seeing
[22:32] <kirkland> cjwatson: ah, so it's somewhat manually sync'd into the installer
[22:32] <cjwatson> CarlFK: dunno why you've filed a bug showing an I/O error on /dev/sdb5 against debconf
[22:33] <kirkland> cjwatson: gotcha, i did seem to run up against various sync/race conditions, as to whether or not the kernel in the installer had the magik i needed ;-)
[22:33] <cjwatson> CarlFK: you sure you don't have hardware trouble?
[22:40] <cjwatson> kirkland: we used to do automatic daily builds, but that didn't work so easily when we switched to Soyuz, and we decided it wasn't all that important to continue doing so. It's very rare that it makes a difference - you've just been unlucky :-)
[22:41] <kirkland> cjwatson: :-)  gotcha.  i do realize this is quite the exceptional situation
[22:41] <kirkland> cjwatson: i did file a bug against partman-lvm, regarding lvm+crypt in jaunty, not yet working
[22:41] <cjwatson> yes, I reassigned it to partman-crypto
[22:41] <cjwatson> probably more fallout from building in dm modules
[22:42] <cjwatson> will have a look in a bit
[22:50] <kirkland> cjwatson: doh, sorry, i should have known partman-crypto
[22:50] <kirkland> cjwatson: i thought that might be the case (fallout of builtins)
[22:51] <kirkland> cjwatson: which is why i tested that case
[22:55] <CarlFK> cjwatson: i think it was caused by a improperly shut down win/ntfs session (probably just killed power)