I'm actually not sure which version the boot.efi is from. The problems with ssh actually had nothing to do with ssh :( We ran into some bug with the atv-bootloader code (we still haven't discovered what the real problem is) where essentially if the initrd file used to create the mach_kernel image was too big the mach_kernel simply wouldn't boot. Unfortunately, adding dropbear or sshd actually exposed this problem so we just moved forward for the time being...
On Jun 25, 1:17 pm, Bharath Ramesh <bharat...@gmail.com> wrote: > On Jun 23, 11:52 pm, Travis Hansen <travisghan...@gmail.com> wrote: > > > > > > > > > > > All > > > You'll be happy to know we've released a new recovery image. > > >http://code.google.com/p/atv-bootloader/downloads/list > > > A couple of things to note... > > > 1. It does include support for pretty much every filesystem out there > > now. > > 2. It does include boot.efi so no need to go hunting that down. > > 3. It is twice the size of 0.6...so if you're looking for a speed > > demon it might not be for you (I haven't done any bootup time tests so > > it might not be bad either) > > 4. grub2 support is in there > > 5. It does not include ssh. We tried but hit bugs :( > > 6. Everything else is updated...parted, gdisk (added), rsync, proper > > dns resolving, wireless support, etc > > Awesome, I will give this a try today. Which version of the firmware > is the boot.efi from, is it from the latest 3.0.2. > Were there issues with dropbear or openssh? > > -- > Bharath -- To post to this group, send email to atv-bootloader@googlegroups.com For more options, visit this group at http://groups.google.com/group/atv-bootloader?hl=en
