From a8d09e79f22ba6fae188f60354247e725bb08004 Mon Sep 17 00:00:00 2001 From: Will Morrison Date: Sun, 12 Jun 2016 08:50:34 -0400 Subject: [PATCH] Spelling and grammatical changes in live-usb.md --- installing/live-usb.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/installing/live-usb.md b/installing/live-usb.md index ad630bfb..c3b25227 100644 --- a/installing/live-usb.md +++ b/installing/live-usb.md @@ -16,8 +16,8 @@ can continue to improve it. Introduction ------------ -We have faced several challenges when making this Live USB edition of Qubes OS, -which traditional Linux distros don't have to bother with: +When making this Live USB edition of Qubes OS, we faced several challenges which +traditional Linux distros don't have to bother with: 1. We needed to ensure Xen is properly started when booting the stick. In fact we still don't support UEFI boot for the stick for this reason, even though @@ -39,20 +39,20 @@ few tens of MBs per VM, sometimes even more. Also, each VM's private image, which essentially holds just the user home directory, typically starts with a few tens of MBs for an "empty VM". Now, while these represent rather insignificant numbers on a disk-basked system, in the case of a live USB all -these files must be stored in RAM, which is a scare resource on any OS, but +these files must be stored in RAM, which is a scarce resource on any OS, but especially on Qubes. We have implemented some quick optimizations in order to minimize the above problem, but this is still far from a proper solution. We're planning to work more on this next. -Now, there are three directions in how we want to work further on this Qubes +There are three directions in which we want to do further work on this Qubes Live USB variant: 1. Introduce an easy, clickable "install to disk" option, merging this with the Qubes installation ISO. So, e.g. make it possible to first see if the given - hardware is compatible with Qubes (run the HCL reporting tool) and only then - install on the main disk. Also, ensure UEFI boot works well. + hardware is compatible with Qubes (by running the HCL reporting tool) and + only then install on the main disk. Also, ensure UEFI boot works well. 2. Introduce options for persistence while still running this out of a USB stick. This would be achieved by allowing (select) VMs' private images to be @@ -74,7 +74,7 @@ Live USB variant: Current limitations ------------------- -(Remember that Qubes Live USB is currently in alpha, so please meter your +(Remember that Qubes Live USB is currently in alpha, so please meter your expectations accordingly.) 1. Currently just the 3 example VMs (untrusted, personal, work), plus the @@ -90,10 +90,10 @@ expectations accordingly.) from a large Qubes backup blob. 5. It's easy to generate Out Of Memory (OOM) in Dom0 by creating lots of VMs which are writing a lot into the VMs filesystem. -6. There is no DispVM savefile, so if one starts one the savefile must be - regenerated which takes about 1-2 minutes. -7. UEFI boot doesn't work, and if you try booting it via UEFI Xen will not be - started, rendering the whole experiment unusable. +6. There is no DispVM savefile, so if you start a DispVM the savefile must be + regenerated, which takes about 1-2 minutes. +7. UEFI boot doesn't work, and if you try booting Qubes Live USB via UEFI, Xen + will not be started, rendering the whole experiment unusable. Downloading and burning