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