Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow for persistence #37

Closed
wants to merge 4 commits into from
Closed

Allow for persistence #37

wants to merge 4 commits into from

Conversation

rcaught
Copy link
Contributor

@rcaught rcaught commented Jun 15, 2014

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.

rcaught added 4 commits June 15, 2014 15:03
@rcaught
Whitespace fixes
299e89c
@rcaught
Partition the disk
8275b1b 
Using HFS+ because MSDOS doesn’t support a case-sensitive volume name
(need volume name “Tails” for Tails persistence setup prerequisite).
Tried exFAT but Grub doesn’t have the load modules.

4GB partition is the minimum suggested by Tails, so using that.  Rest
is defined as free space.
@rcaught
Make sure we also provision Vagrant
106d199
@rcaught
Vagrant updates and resulting EFI
324557e 
- Ignore local files.
- Use HFS+ Grub load modules
@rcaught
Copy link
Contributor Author

rcaught commented Jun 15, 2014

Also see #7

@rcaught
Copy link
Contributor Author

rcaught commented Jun 24, 2014

Thoughts @hellais?

@hellais
Copy link
Owner

hellais commented Jun 25, 2014

@rcaught have you tested this and confirm that an image created this way will allow persistence to work?

@rcaught
Copy link
Contributor Author

rcaught commented Jun 25, 2014

@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).

@hellais
Copy link
Owner

hellais commented Jun 25, 2014

Yeah the only thing that worries me is the removal of fat from the grub-mkimage command. Why was that done?

@rcaught
Copy link
Contributor Author

rcaught commented Jun 26, 2014

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).

@rcaught
Copy link
Contributor Author

rcaught commented Jul 21, 2014

@hellais bump! 😄

@hellais
Copy link
Owner

hellais commented Aug 25, 2014

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.

@hellais
Copy link
Owner

hellais commented Aug 25, 2014

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 rcaught closed this Jan 17, 2015
@hellais
Copy link
Owner

hellais commented Jan 18, 2015

@rcaught why did you close this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rcaught @hellais