Closed rcaught closed 9 years ago
Also see #7
Thoughts @hellais?
@rcaught have you tested this and confirm that an image created this way will allow persistence to work?
@hellais yes, I did and have it working on my MacBook Air (2013). I went through the setup and enabled persistence successfully.
I'm not sure if any of the EFI changes have invalided any historic tested_on.md
, but works well for my setup (minus wifi - but that didn't work before regardless).
Yeah the only thing that worries me is the removal of fat
from the grub-mkimage
command. Why was that done?
I used HFS+ because FAT doesn’t support case-sensitive volume names (needed the volume name “Tails” to satisfy the Tails persistence setup). Tried exFAT but Grub doesn’t have the load modules (at least the Vagrant image being used didn't).
@hellais bump! :smile:
Ok sorry for the long lag.
So two things:
1) I think this should be a command line option and not the default way of burning the image.
2) You should note that the TAILS devs are going to soon support natively using TAILS with UEFI.
Anyways if you make this into an optional thing I will be sure to merge it.
Also can you add to the repo in data/
the BOOTX64.efi
for the provided configuration and make it so that the persistence options picks the one built with HFS+ support and the non-persistent one picks the original one supporting FAT?
@rcaught why did you close this PR?
Using this method, the user can simply boot into Tails after running TAILS-OSX and use the inbuilt encrypted persistence storage configuration tools.
This pull request changes the volume name and file format to match an expectation on the Tails side.