suzanne.soy/qubes-doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Spelling and grammatical changes in live-usb.md

Browse Source
This commit is contained in:
Will Morrison 2016-06-12 08:50:34 -04:00 committed by GitHub
parent 4fadbec0c9
commit a8d09e79f2
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
installing/live-usb.md
View File

@ -16,8 +16,8 @@ can continue to improve it.
Introduction Introduction
------------ ------------
We have faced several challenges when making this Live USB edition of Qubes OS, When making this Live USB edition of Qubes OS, we faced several challenges which
which traditional Linux distros don't have to bother with: traditional Linux distros don't have to bother with:
1. We needed to ensure Xen is properly started when booting the stick. In fact 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 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 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 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 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. especially on Qubes.
We have implemented some quick optimizations in order to minimize the above 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 problem, but this is still far from a proper solution. We're planning to work
more on this next. 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: Live USB variant:
1. Introduce an easy, clickable "install to disk" option, merging this with the 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 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 hardware is compatible with Qubes (by running the HCL reporting tool) and
install on the main disk. Also, ensure UEFI boot works well. 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 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 stick. This would be achieved by allowing (select) VMs' private images to be
@ -74,7 +74,7 @@ Live USB variant:
Current limitations 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.) expectations accordingly.)
1. Currently just the 3 example VMs (untrusted, personal, work), plus the 1. Currently just the 3 example VMs (untrusted, personal, work), plus the
@ -90,10 +90,10 @@ expectations accordingly.)
from a large Qubes backup blob. from a large Qubes backup blob.
5. It's easy to generate Out Of Memory (OOM) in Dom0 by creating lots of VMs 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. which are writing a lot into the VMs filesystem.
6. There is no DispVM savefile, so if one starts one the savefile must be 6. There is no DispVM savefile, so if you start a DispVM the savefile must be
regenerated which takes about 1-2 minutes. 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 7. UEFI boot doesn't work, and if you try booting Qubes Live USB via UEFI, Xen
started, rendering the whole experiment unusable. will not be started, rendering the whole experiment unusable.
Downloading and burning Downloading and burning