[02:12] <EntropyWorks> is there a way to add ufw rules during the install. I've tried adding
[02:12] <EntropyWorks> ufw ufw/allow_known_ports multiselect SSH
[02:12] <EntropyWorks> ufw ufw/allow_custom_ports string 22/tcp
[02:12] <EntropyWorks> ufw ufw/enable boolean true
[02:15] <EntropyWorks> but that doesn't work. and I can't run ufw in the late_command.sh either.
=== kentb_ is now known as kentb
[08:32] <FourDollars> cjwatson: How many UEFI boot entries of 'ubuntu' will be created for Secure Boot? I saw there are two 'ubuntu' UEFI boot entries. One points to File(\EFI\ubuntu\shimx64.efi), and the other points to File(EFI\Ubuntu\grubx64.efi).
=== buildslayer is now known as shadeslayer
[09:10] <FourDollars> cjwatson:
[09:10] <FourDollars> oops
[09:14] <FourDollars> cjwatson: I find File(\EFI\BOOT\grubx64.efi) (created by grub-install --removable) will not follow the content of File(\EFI\BOOT\grub.cfg) to search uuid.
[09:22] <FourDollars> cjwatson: grub2 1.99-21ubuntu3.7 in precise-proposed doesn't solve the problem of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1087653 .
[09:22] <ubot2`> Launchpad bug 1087653 in OEM Priority Project precise "grub2-signed doesn't support removable drive." [High,In progress]
[09:27] <FourDollars> cjwatson: I need to touch .disk/info manually to make it to work.
[10:10] <FourDollars> cjwatson: Would you remove the restriction of '.disk/info' for `grub-install --removable --uefi-secure-boot`?
[11:03]  * FourDollars looks at grub2/precise-proposed/debian/build-efi-images .
[11:13] <cjwatson> No, I won't
[11:13] <cjwatson> It's not so much a restriction as a "how on earth do we find what drive to boot from"
[11:14] <cjwatson> I didn't just put it in to get in people's way
[11:14] <cjwatson> To remove it I would have to have some other way to locate the EFI System Partition
[11:15] <cjwatson> This isn't going to be a priority for me for the rest of the year, FWIW
[11:18] <FourDollars> cjwatson: Will File(\EFI\BOOT\grubx64.efi) read File(\EFI\BOOT\grub.cfg) before it goes to check .disk/info or .disk/mini-info ?
[11:22] <cjwatson> No, because it doesn't know where \EFI\BOOT\ is
[11:23] <cjwatson> I consider having to touch /.disk/info a minor inconvenience
[11:23] <cjwatson> It would be nice to fix it, but there's so much else to do
[11:23] <FourDollars> I see.
[11:24] <FourDollars> Does it mean we will also put .disk/info in Ubuntu system partition?
[11:24] <cjwatson> Two UEFI boot entries seems like a bug, although it's possible it has something to do with testing successive versions?
[11:24] <cjwatson> No, because it's only an issue when using --removable
[11:24] <cjwatson> We have it on Ubuntu installation media
[11:24] <FourDollars> I see.
[11:26] <cjwatson> It's possible your boot manager is ignoring what was set by efibootmgr and is just displaying \EFI\*\*.efi or some such
[11:26] <cjwatson> As far as I can see we only ever call efibootmgr once
[11:26] <xnox> cjwatson: should grub-install touch .disk/info when envoked with removable & uefi-secure-boot flags?
[11:28] <FourDollars> xnox: I think so.
[11:30] <FourDollars> I am encountering a problem that BootCurrent points to HD File(EFI\BOOT\BOOTX64.efi), but it boots my USB stick.
[11:31] <cjwatson> No, I really disagree
[11:31] <cjwatson> The requirement for /.disk/info is temporary
[11:31] <cjwatson> We shouldn't entrench it by making tools create it automatically
[11:32] <cjwatson> I will fix it, just not this year when I have a couple of working days left and ~three other major things to finish
[11:32] <FourDollars> For me to create .disk/info manually is not a problem.
[11:33] <FourDollars> My problem is HDD parition has .disk/info and USB drive also has .disk/info.
[11:34] <FourDollars> HD File(EFI\BOOT\BOOTX64.efi) can not tell which one is the correct one.
[11:35] <FourDollars> Or should I say "HD File(EFI\BOOT\grubx64.efi) can not tell which one is the correct one."
[11:36] <FourDollars> cjwatson: Will you fix the problem of .disk/info in precise next year?
[11:37] <FourDollars> Err. I mean in Ubuntu 12.04.2 .
[11:42] <cjwatson> I don't know whether I'll squeeze it into .2, but at least for .3
[11:42] <cjwatson> Why on earth does your HD partition have .disk/info?  I can't imagine a reason for that
[11:43] <FourDollars> cjwatson: Because I am working on a feature like Ubuntu on-disk installer.
[11:44] <FourDollars> cjwatson: I will use the USB drive to install "Ubuntu on-disk installer" into HDD partition, and use `grub-install --removable` and create a UEFI boot entry points to it.
[11:44] <cjwatson> Ah.  Well, you're also demonstrating why the problem isn't simple, if you think about it
[11:45] <cjwatson> /efi/boot/grub.cfg is no more a unique path than /.disk/info is
[11:45] <xnox> FourDollars: for "factory reset"-like functionality ?
[11:45] <FourDollars> xnox: yes
[11:45] <cjwatson> So it needs to actually figure out the device it was booted from, not just add another check for /efi/boot/grub.cfg
[11:46] <FourDollars> I know this is not an easy task. :(
[11:47] <FourDollars> cjwatson: yes
[11:47] <FourDollars> cjwatson: I hope grub2 can check grub.cfg in the same filesystem and the same folder first.
[11:49] <FourDollars> And the search.fs_uuid in grub.cfg will find out the right parition of /boot/grub .
[11:51] <cjwatson> No, UUID search is useless
[11:51] <cjwatson> At least for finding grub.cfg
[11:51] <FourDollars> cjwatson: Why is it useless?
[11:51] <cjwatson> We have no way to embed a UUID into a signed image
[11:52] <FourDollars> Agree.
[11:52] <cjwatson> Well, OK, it would be useful for finding /boot/grub I suppose
[11:52] <cjwatson> Sorry, I have a really bad headache and can't think
[11:52] <cjwatson> Poking me about this right now probably isn't very useful
[11:52] <FourDollars> Not mind.
[11:55] <FourDollars> Never mind.
[11:55] <FourDollars> cjwatson: It is great to know these implementaion details, thanks a lot.
[12:18]  * FourDollars is wondering how ESP,File(\EFI\ubuntu\grubx64.efi) copied from grubx64.efi.signed can read ESP,File(\EFI\ubuntu\grub.cfg) and work well.
[12:27] <cjwatson> grubx64.efi.signed is configured differently from gcdx64.efi.signed, as I explained the other day
[12:44]  * FourDollars goes to check IRC logs.
[13:00] <FourDollars> Which config will be read first if we don't use '-c' to embed file as an early config? $prefix/grub.cfg?
[13:01] <cjwatson> Yes
[13:02] <FourDollars> So that is why ESP,File(\EFI\ubuntu\grubx64.efi) will read ESP,File(\EFI\ubuntu\grub.cfg).
[13:08] <FourDollars> And why ESP,File(\EFI\BOOT\BOOTX64.EFI) will read USB,File(\efi\boot\grub.cfg) is because we embed an early config "normal (memdisk)/grub.cfg" and "(memdisk)/grub.cfg" find the USB,File(\.disk\info) before HDD,File(\.disk\info) is to be found.
[13:10] <FourDollars> So the problem might be the search order of storage devices.
[13:12] <FourDollars> However we can not assume which search order is correct because of different usages. :(
[13:13] <cjwatson> The only correct fix is for gcdx64.efi to learn how to locate the device it was booted from rather than having to guess based on file names.
[13:14] <FourDollars> Yes.
[13:40] <FourDollars> It should be possible to find out the corresponding filesystem from BootCurrent.
[13:47] <FourDollars> I guess.
=== ray__ is now known as ray2
=== ray2 is now known as raymondjtoth
[19:00] <raymondjtoth> hi im tryingyo install wubi
[19:01] <raymondjtoth> and get boot err whats up
[19:01] <raymondjtoth> get err grldr
[19:06] <raymondjtoth> hi im tryingyo install wubi [13:00] <raymondjtoth> and get boot err whats up [13:01] <raymondjtoth> get err grldr
[19:14] <raymondjtoth> <raymondjtoth> and get boot err whats up [13:01] <raymondjtoth> get err grldr [13:06] <raymondjtoth> hi im tryingyo install wubi [13:00] <raymondjtoth> and get boot err whats up [13:01] <raymondjtoth> get err grldr
[19:17] <raymondjtoth> <raymondjtoth> and get boot err whats up [13:01] <raymondjtoth> get err grldr [13:06] <raymondjtoth> hi im tryingyo install wubi [13:00] <raymondjtoth> and get boot err whats up [13:01] <raymondjtoth> get err grldr