mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-08-01 19:16:27 -04:00
Fix a few typos
This commit is contained in:
parent
5ae0d5dfb0
commit
0baa097f9b
39 changed files with 211 additions and 218 deletions
|
@ -15,7 +15,7 @@ Template installation
|
|||
|
||||
> [dom0]#qubes-dom0-update qubes-template-fedora-21-minimal
|
||||
|
||||
*Note*: the template may not start in qubes R3 when using kernel 3.19 (unstable). In this case, switch the AppVM or TemplateVM to the kernel 3.18.
|
||||
*Note*: the template may not start in Qubes R3 when using kernel 3.19 (unstable). In this case, switch the AppVM or TemplateVM to the kernel 3.18.
|
||||
|
||||
*Note*: If you have doubts about a set of tool or package you want to install, start installing and testing it in an AppVM. You can then reproduce it later in your TemplateVM if you are satisfied. That the (QubesOS?) template philosophy.
|
||||
|
||||
|
@ -27,7 +27,7 @@ Administration (documented)
|
|||
|
||||
sudo pciutils vim-minimal less tcpdump telnet psmisc nmap nmap-ncat usbutils
|
||||
|
||||
*Notes*: nmap can be used to discover a network (nmap -sP [network]), especially if you are inside a Microsoft network, because your AppVM will be protected/NATted behind Qubes firewall (microsoft / home network are heavily using autodiscovery technologies which require to beint in the same local network (no firewall/no NAT), eg: your printer.
|
||||
*Notes*: nmap can be used to discover a network (nmap -sP [network]), especially if you are inside a Microsoft network, because your AppVM will be protected/NATted behind Qubes firewall (microsoft / home network are heavily using autodiscovery technologies which require to be in the same local network (no firewall/no NAT), eg: your printer.
|
||||
|
||||
Some recommendation here: check your current network using the Network manager applet (eg: 192.168.1.65). Then run nmap in your current AppVM/TemplateVM to search for the selected printer/equipement: nmap -sP 192.168.1.-. Don't forget to allow temporarily the Qubes Firewall if you are inside a TemplateVM.
|
||||
|
||||
|
@ -86,9 +86,9 @@ Printer Setup
|
|||
|
||||
system-config-printer system-config-printer-applet cups
|
||||
|
||||
Dependency Note: depends on python3 + python3 additionnal libraries which takes more than 40 M once installed.
|
||||
Dependency Note: depends on python3 + python3 additional libraries which takes more than 40 M once installed.
|
||||
|
||||
Dependency Note: cups depends on ghostscript and require installing additionnal printing fonts (not documented here), so it can takes several dozen of MB
|
||||
Dependency Note: cups depends on ghostscript and require installing additional printing fonts (not documented here), so it can takes several dozen of MB
|
||||
|
||||
Manual operations
|
||||
---------------------------
|
||||
|
@ -97,7 +97,7 @@ Manual operations
|
|||
|
||||
- First you need to search for your printer. If you don't know its name or IP, search for it using nmap: check your current network using the Network manager applet (eg: 192.168.1.65). Then run nmap in your current AppVM/TemplateVM to search for the selected printer/equipement: nmap -sP 192.168.1.-. Don't forget to allow temporarily the Qubes Firewall if you are inside a TemplateVM.
|
||||
|
||||
- Once you identifed your printer, run system-config-printer GUI to install your printer
|
||||
- Once you identified your printer, run system-config-printer GUI to install your printer
|
||||
|
||||
- You man need to cancel the operation to install more adapted printer drivers (eg: if the driver cannot be found automatically). Use yum search printername to find potential drivers (eg yum search photosmart)
|
||||
|
||||
|
@ -112,9 +112,9 @@ lxterminal dejavu-sans-mono-fonts dejavu-sans-fonts gnome-settings-daemon
|
|||
*Note*: You need to install sans-mono fonts for the terminal or it will be unreadable (overlapping characters....), while the sans fonts are just to get nicer GUI menus.
|
||||
|
||||
*Scite* is a nice notepad that can also highlight scripts with very light dependencies
|
||||
|
||||
|
||||
scite
|
||||
|
||||
|
||||
*Meld* allow comparing two text files/ two configuration files easily.
|
||||
|
||||
meld
|
||||
|
@ -169,11 +169,11 @@ Cleaning the whole dconf settings is also possible by removing the following fil
|
|||
rm ~/.config/dconf/user
|
||||
~~~
|
||||
|
||||
*Note*: lxappearance only have effect on gtk3 theme so it won't work to change gtk2 themes (used by Firefox, Thunderbird ...).
|
||||
*Note*: lxappearance only have effect on gtk3 theme so it won't work to change gtk2 themes (used by Firefox, Thunderbird ...).
|
||||
However, it is very lightweight and can be used to identify the name and look of themes you are interested in.
|
||||
Once you have the name, you can apply it using gsetting command line or gconf-editor.
|
||||
|
||||
*Note*: if you really want a GUI theme editor, you can install gnome-tweak-tools, but this tool have a lot
|
||||
*Note*: if you really want a GUI theme editor, you can install gnome-tweak-tools, but this tool have a lot
|
||||
of gnome dependencies (~150MB of dependencies). Eventually install it and uninstall it as soon as you changed your theme.
|
||||
|
||||
#### Testing notes
|
||||
|
@ -184,7 +184,7 @@ The following programs can be used to see if theme has been correctly applied:
|
|||
* GTK3 program: lxterminal
|
||||
* QT program: keepassx
|
||||
|
||||
*Note*: testing in a TemplateVM will not work as expected because gnome-settings-daemon is not started in TemplateVM.
|
||||
*Note*: testing in a TemplateVM will not work as expected because gnome-settings-daemon is not started in TemplateVM.
|
||||
so test your themes in an AppVM and then update the TemplateVM accordingly.
|
||||
|
||||
### Forcing theme change for all AppVM depending on a TemplateVM
|
||||
|
@ -246,7 +246,7 @@ Finally, regenerate the dconf database
|
|||
|
||||
### Uniform look for QT & GTK
|
||||
|
||||
Getting an uniform look for QT & GTK is not acheaved yet. A good source is on the following link [UNIFORMTHEME]
|
||||
Getting an uniform look for QT & GTK is not achieved yet. A good source is on the following link [UNIFORMTHEME]
|
||||
|
||||
Two case:
|
||||
|
||||
|
@ -254,10 +254,10 @@ Two case:
|
|||
(eg: Adwaita which is the default theme. I did not found another cross framework theme on fedora default packages).
|
||||
|
||||
2. You want to use the GTK theme you selected for Qt but there is no qt package.
|
||||
In this case QGtkStyle will take precedence and convert the style automaticall.
|
||||
In this case QGtkStyle will take precedence and convert the style automatically.
|
||||
You can verify if it is enabled by searching for "style=GTK+" in /etc/xdg/Trolltech.conf.
|
||||
If style is changed to another name, it will be used instead of your GTK theme.
|
||||
|
||||
|
||||
*Note*: check that ~/.config/Trolltech.conf in your AppVMs is not defining another "style=" because it will take precedence over your global QT theme.
|
||||
|
||||
|
||||
|
|
|
@ -5,17 +5,17 @@ permalink: /doc/windows-template-customization/
|
|||
redirect_from: /en/doc/windows-template-customization/
|
||||
---
|
||||
|
||||
Disable/Uninstall unecessary features/services
|
||||
Disable/Uninstall unnecessary features/services
|
||||
=============================
|
||||
|
||||
Windows features
|
||||
----------------------------
|
||||
|
||||
Uninstall windows features from Control Panel > Turn windows features On/Off.
|
||||
Uninstall windows features from Control Panel > Turn windows features On/Off.
|
||||
|
||||
Generally, it will be required to reboot after features desinstallation.
|
||||
Generally, it will be required to reboot after features are uninstalled.
|
||||
|
||||
If you do not manage to uninstall some features, it is sometimes necessarry to uninstall them one by one or two by two.
|
||||
If you do not manage to uninstall some features, it is sometimes necessary to uninstall them one by one or two by two.
|
||||
|
||||
Only keep:
|
||||
|
||||
|
@ -36,8 +36,8 @@ Disable the following services that are not required or have no sense in a VM co
|
|||
* Base Filtering Engine (only required if your want to use Microsoft IPSEC)
|
||||
* DHCP Client
|
||||
* Function Discovery Provider Host
|
||||
|
||||
this will not work anyway because SSDP discovery uses multicast - need to be on the same network which is not the case because of qubes firewall
|
||||
|
||||
this will not work anyway because SSDP discovery uses multicast - need to be on the same network which is not the case because of Qubes firewall
|
||||
* Peer Name Resolution Protocol
|
||||
* Peer Netwoking Grouping
|
||||
* Peer Networking Identity Manager
|
||||
|
@ -67,10 +67,10 @@ System properties
|
|||
Right click on computer and go to Properties > Advanced > Performances:
|
||||
|
||||
* If your don't care about visual effect, in Visual Effect select "Adjust for best performance"
|
||||
* I personnally tweak the page file size to win some place on my root.
|
||||
|
||||
* I personally tweak the page file size to win some place on my root.
|
||||
|
||||
In Advanced>Performances>Advanced tab, change Virtual memory:
|
||||
|
||||
|
||||
1. unselect automatically manage paging file size for all drive
|
||||
2. click on drive C:
|
||||
3. select no paging file
|
||||
|
@ -80,22 +80,22 @@ Right click on computer and go to Properties > Advanced > Performances:
|
|||
7. use an initial size of 500 and a max size of 1000. If the page file is too small, you will notify a low memory pop up when working on windows. In this case, it often means that you should extend your AppVM RAM.
|
||||
|
||||
* System Protection
|
||||
|
||||
Here you can disable Shadow Folder because it has little sense in case of qubes because
|
||||
|
||||
Here you can disable Shadow Folder because it has little sense in case of Qubes because
|
||||
|
||||
* we do backup regularly of AppVMs/TemplateVMs;
|
||||
* we can revert at least one template change if we break something.
|
||||
|
||||
|
||||
Select drives where system protection is enabled and click Configure. "Turn of system protection" "Delete all restore points"
|
||||
|
||||
* Remote
|
||||
|
||||
Unselect Allow Remote Assistance connetions to this computer.
|
||||
|
||||
Unselect Allow Remote Assistance connections to this computer.
|
||||
|
||||
Task scheduler
|
||||
-----------------------
|
||||
|
||||
Open the task scheduler and *disable* the following tasks.
|
||||
Open the task scheduler and *disable* the following tasks.
|
||||
|
||||
If you remove these tasks they may be recreated automatically by various windows management tools (such as defragmentation)
|
||||
|
||||
|
@ -124,9 +124,9 @@ Manual tasks that can/should be started in the template
|
|||
===================================
|
||||
|
||||
* Disk defragmentation
|
||||
|
||||
|
||||
* Windows Update
|
||||
|
||||
|
||||
* Windows file cleaning
|
||||
1. Run windows drive cleaner as Administrator.
|
||||
2. Enable all the task and run the cleaner
|
||||
|
@ -136,32 +136,31 @@ Manual tasks that can/should be started in the template
|
|||
2. Copy the attached ccleaner configuration file in CCleaner program file folder
|
||||
3. Run ccleaner with all option set except "wipe free space" (it will also remove user history and preferences)
|
||||
4. Run ccleaner only with the option "wipe free space".
|
||||
|
||||
|
||||
It will write zeros in all unused space. This will allow you to strip the root.img file later
|
||||
|
||||
|
||||
* TemplateVM stripping
|
||||
|
||||
|
||||
Ensure that you know what you are doing in this section as you may destroy by error your template root.img file.
|
||||
|
||||
|
||||
* If you ran ccleaner with "wipe free space", follow the following procedure
|
||||
|
||||
|
||||
1. from dom0, go to /var/lib/templates-vm/yourtemplate
|
||||
|
||||
2. copy root.img using the following command
|
||||
|
||||
|
||||
> cp --sparse=always root.img root.img.clean
|
||||
|
||||
3. if the copy worked, you can move the new root file by running this command
|
||||
|
||||
> mv root.img.clean root.img
|
||||
|
||||
* If don't managed to fill the free space with zeroes, you can follow the following *unsafe* undocumented procedure
|
||||
|
||||
|
||||
* If don't managed to fill the free space with zeros, you can follow the following *unsafe* undocumented procedure
|
||||
|
||||
1. from dom0, go to /var/lib/templates-vm/yourtemplate
|
||||
2. check the partitionning to identify the filesystem offset of root.img
|
||||
2. check the partitioning to identify the filesystem offset of root.img
|
||||
3. mount the filesystem
|
||||
4. create a file with zeros inside the filesystem until the mounted filesystem is full
|
||||
5. remove the file
|
||||
6. unmount the partition
|
||||
7. make a copy of root.img in sparse mode.
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@ redirect_from:
|
|||
- "/wiki/UserDoc/XFCE/"
|
||||
---
|
||||
|
||||
XFCE installtion in dom0
|
||||
XFCE installation in dom0
|
||||
========================
|
||||
|
||||
**Disclaimer: XFCE isn't fully integrated with Qubes environment, it still require notable amount of manual configuration after install**
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue