[01:42] <ev> indeed, that's been the plan for some time.  DX is working on it (specifically Ted, last I checked)
[01:43] <ev> though yes, I do sit right next to mpt :)
[10:44] <CIA-4> usb-creator: evand * r327 usb-creator/ (3 files in 2 dirs):
[10:44] <CIA-4> usb-creator: * debian/control, usbcreator/frontends/gtk:
[10:44] <CIA-4> usb-creator:  - Remove python-gnome2 dependency by switching help_display_uri to
[10:44] <CIA-4> usb-creator:  gtk.show_uri. LP: #661289
[11:03] <CIA-4> usb-creator: evand * r328 usb-creator/debian/changelog: releasing version 0.2.26
[11:07] <CIA-4> ubiquity: evand * r4435 trunk/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[11:07] <CIA-4> ubiquity: Expose the navigation control in the GTK frontend API.
[11:07] <CIA-4> ubiquity: Thanks Ying-Chun Liu!
[13:49] <soren> Is there any particular reason why the root filesystem is placed at the start of the disk rather than at the end?
[13:49] <soren> I'm sure there is, but what is it? :)
[13:52] <soren> It would be handy if they were at the end. If you install Ubuntu in a VM on a virtual disk and decide to expand the disk later, it's a bit of a bummer that you can't just extend the partition.
[13:53] <soren> Alternatively, maybe it's time we use lvm by default? :)
[14:45] <ev> lvm> what doesn't btrfs solve?
[16:14] <ev> I appear to have lost the magic runes to shoving a partman-auto udeb kicking and screaming into a running d-i instance
[16:15] <cjwatson> does it involve new debconf templates?
[16:16] <ev> yes
[16:16] <ev> which I separately imported using debconf-loadtemplate after sed'ing out the underscores
[16:17] <cjwatson> yeah, that doesn't really work
[16:17] <ev> still hanging on a description metaget
[16:17] <ev> ah
[16:17] <ev> fail
[16:17] <cjwatson> because you end up talking to the wrong debconf instance
[16:17] <ev> right!
[16:17] <ev> ugh
[16:17] <cjwatson> build the udeb, and edit some random victim postinst script (I usually use load-cdrom.postinst, after the call to anna)
[16:17] <cjwatson> make it do wget and udpkg -i
[16:17] <cjwatson> (or udpkg --unpack if the udeb you're using has a postinst, but partman-auto doesn't)
[16:26] <ev> ah, thanks!
[19:13] <soren> ev: Well, not everyone uses btrfs, but does btrfs let you add another block device to it like lvm does?
[21:27] <corecode> hi
[21:27] <corecode> will the installer/preseed only use eth0
[21:27] <corecode> or will it probe other cards as well?
[21:27] <corecode> somehow the automatic install on this machine didn't work out
[22:01] <cruejones> hi, why am i able to user an ubuntu DVD iso loopback shared via http as a local mirror but standard debian fails with the same setup?
[22:01] <cruejones> for netinstalls
[22:03] <cjwatson> to make that work you have to include a few extra packages on the iso (things that aren't on the netboot initrd but are in the cdrom initrd) and Debian may well not do that
[22:03] <cjwatson> I don't think either of us really consider it a properly supported setup, it just happens to work in Ubuntu at the moment
[22:04] <cruejones> thanks - any pointers on what files might be needed?
[22:04] <cjwatson> corecode: you should be able to preseed netcfg/choose_interface.  I think the default is something like the first interface that seems to have a link, or possibly just the first interface
[22:05] <cjwatson> cruejones: sorry, I don't have a list
[22:05] <cruejones> cjwatson: any pointers on where to look?
[22:05] <cjwatson> there's a udeb manifest alongside the initrds
[22:05] <cruejones> ok
[22:05] <cjwatson> http://ftp.debian.org/debian/dists/testing/main/installer-i386/current/images/ or something like that
[22:06] <cjwatson> you'd need to subtract the files in the netboot initrd from those in the cdrom initrd, and include the difference
[22:06] <cruejones> already having to use unionfs on iso to fix some symlink issues so I might be able to fake a mirror by adding those files to the iso via the union
[22:07] <cruejones> and please consider it an important configuration for future support - network shared loopback isos is a classic scenario for space savings
[22:08] <cruejones> and in my case I need to use a different non-debian based distro as the pxe/netboot install source so creating a local mirror is non-trivial
[22:11] <cruejones> cjwatson: so I just thought about it and I am confused as to why I need to care about the netboot vs. dvd initrd?  I am using the kernel/ramdisk from the netboot (mini.iso) which works just fine.  Then I loopback mount the main DVD and share it via http.
[22:12] <cruejones> when I point the netboot installer to the dvd/iso http share it returns that it is a bad mirror - so I would assume I am missing some repo/mirror type files on the main DVD?
[22:12] <cruejones> and thanks for helping - seeing as this is more pure debian question
[22:16] <cjwatson> cruejones: because the way the installer works is that it only ships the necessary core of itself in the initrd, and fetches more bits of itself at run-time
[22:16] <cjwatson> (udebs)
[22:16] <cjwatson> cruejones: the "necessary core" depends on the installation method - netboot, cdrom, etc.
[22:16] <cjwatson> for netboot initrds it has to include the network configuration components etc. in the initrd; for cdrom initrds it needs to know how to mount the cdrom
[22:17] <cjwatson> however, when netbooting, there are bits that still need to be performed *eventually*, just not necessarily so early that they have to be in the initrd
[22:17] <cjwatson> so the udebs for those tasks need to be available somehow
[22:18] <cruejones> ok, but in theory what I am doing is a pure netinstall, just that my mirror is really a loopback mount of the main DVD shared via http
[22:18] <cjwatson> mind you returning "bad mirror" is actually something a bit different, now that I read it
[22:18] <cruejones> right
[22:18] <cjwatson> you may well have the same problem later though
[22:18] <cjwatson> for Debian, could we move this to #debian-boot on irc.oftc.net please?
[22:19] <cjwatson> that's the corresponding Debian channel
[22:19] <cruejones> ok, thanks
[22:52] <corecode> what could be the reason that list-devices disk returns empty?
[22:56] <cjwatson> corecode: what's in /sys/block (excluding the ram* entries)?
[22:56] <corecode> loop
[22:57] <cjwatson> then the kernel hasn't found your disks
[22:57] <corecode> 0f:04.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064 PCI-X Fusion-MPT SAS (rev 02)
[22:57] <corecode> yea, but why
[22:57] <cjwatson> could be because the module for that disk isn't in the installer initrd for some reason
[22:57] <cjwatson> what's the numeric pci id for that?
[22:58] <cjwatson> never mind, looked it up, 1000:0050
[22:58] <corecode> yep
[22:58] <corecode> lspci -nv over 9600bps is a bit slow
[22:58] <corecode> on that machine in particular
[23:01] <cjwatson> lsmod | grep mptsas
[23:01] <corecode> nop
[23:01] <cjwatson> what release?
[23:02] <corecode> maverick
[23:03] <corecode> obscure
[23:03] <corecode> let me reboot
[23:03] <cjwatson> no wait!
[23:03] <corecode> maybe that fixes something
[23:03] <corecode> ok
[23:03] <cjwatson> nano -v /var/lib/dpkg/status
[23:03] <cjwatson> Ctrl-w message-modules ENTER
[23:03] <cjwatson> does that show anything?  if so what's the Status field?
[23:03] <corecode> nothing
[23:04] <cjwatson> no match?
[23:04] <corecode> no match
[23:04] <cjwatson> can you extract /var/log/syslog and put it on paste.ubuntu.com for me?
[23:04] <corecode> yes
[23:04] <corecode> hang on
[23:04] <corecode> if i can get scp on this box
[23:05] <cjwatson> anna-install openssh-client-udeb
[23:05] <corecode> hm, that just clears the screen
[23:05] <cjwatson> yes, but now you have scp
[23:06] <cjwatson> or should do
[23:06] <corecode> no :/
[23:06] <corecode> something is a bit wrong
[23:06] <cjwatson> try "save debug logs" from the installer main menu
[23:06] <cjwatson> sounds like your installer is incapable of installing extra components of itself for some reason
[23:06] <cjwatson> what installer image are you using?
[23:06] <corecode> the maverick amd64 netboot image
[23:07] <corecode> but that worked for all other machines
[23:07] <cjwatson> no, which url
[23:07] <cjwatson> exactly
[23:08] <corecode> i can't tell right now
[23:08] <cjwatson> ok, well, you mentioned a network configuration problem
[23:08] <corecode> yes
[23:08] <cjwatson> how did you resolve that, and what did you do afterwards?
[23:08] <corecode> i did manually dhclient eth1
[23:08] <corecode> and then let the installer continue
[23:09] <corecode> then it must have rebooted, but didn't finish the installation + preseed post script
[23:09] <corecode> hmmm
[23:09] <cjwatson> sounds like some bit of network configuration wasn't properly set up
[23:09] <corecode> maybe there is some nfsv4 issue there as well
[23:09] <cjwatson> and therefore it couldn't fetch installer components off the network
[23:09] <corecode> but that's unrelated
[23:10] <corecode> quite possible
[23:10] <cjwatson> you're probably right to reboot at this point
[23:11] <corecode> how can i find out why it didn't manage to pull up the network?
[23:11] <cjwatson> read through /var/log/syslog I guess
[23:11] <cjwatson> everything should be in there somewhere, though it's pretty verbose
[23:11] <corecode> http://pastebin.ca/1995057
[23:13] <corecode> it keeps talking about eth1: link is not ready
[23:14] <corecode> but that seems to be due to a missing ifconfig up
[23:14] <cjwatson> not sure I have any idea, sorry
[23:14] <cjwatson> normally you shouldn't need ifconfig up to get a link indication
[23:14] <corecode> Nov 17 23:05:25 kernel: [ 3720.533354] ADDRCONF(NETDEV_UP): eth1: link is not ready
[23:14] <corecode> Nov 17 23:05:25 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
[23:14] <corecode> Nov 17 23:05:27 kernel: [ 3722.590977] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[23:14] <corecode> Nov 17 23:05:27 kernel: [ 3722.594115] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[23:14] <corecode> magical
[23:15] <cjwatson> the MII link indication is what tells you that you can do ifconfig up
[23:15] <cjwatson> as I understand it
[23:15] <cjwatson> but this isn't particularly my field of expertise, so "I don't know, sorry"
[23:15] <corecode> yea
[23:15] <corecode> mmm
[23:22] <corecode> oh also the kernel doesn't seem to reliably number the network cards the same way
[23:28] <cjwatson> no, that has been a bit of a saga to try to fix I understand
[23:41] <corecode> hmm