Merge branch 'sprig-florist-master'

This commit is contained in:
Andrew David Wong 2016-11-12 12:29:36 -08:00
commit 33bd4950f2
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17

View File

@ -12,71 +12,64 @@ redirect_from:
Fedora - minimal Fedora - minimal
================ ================
The template weighs only about 300MB and has most of the stuff cut off, except for minimal X and xterm. It is really just a barebone and not even usable in this form - but you can customize it to meet your needs. You can find some usage examples in the section below. The template only weighs about 300 MB and has only the most vital packages installed, including a minimal X and xterm installation.
The minimal template, however, can be easily extended to fit your requirements. The sections below contain the instructions on duplicating the template and provide some examples for commonly desired use cases.
Installation
------------
The Fedora minimal template can be installed with the following command:
Install
-------
It can be installed via the following command:
~~~ ~~~
[user@dom0 ~]$ sudo qubes-dom0-update qubes-template-fedora-23-minimal [user@dom0 ~]$ sudo qubes-dom0-update qubes-template-fedora-23-minimal
~~~ ~~~
The download may take a while. The download may take a while depending on your connection speed.
Usage Duplication and first steps
----- ---------------------------
It is a good idea to clone the original template, and make any changes in the new clone instead: It is higly recommended to clone the original template, and make any changes in the clone instead of the original template. The following command clones the template. Replace `your-new-clone` with your desired name.
~~~ ~~~
[user@dom0 ~]$ qvm-clone fedora-23-minimal <your new template name> [user@dom0 ~]$ qvm-clone fedora-23-minimal your-new-clone
~~~ ~~~
The sudo package is not installed by default, so let's install it: You must start the template in order to customize it.
A recommended first step is to install the `sudo` package, which is not installed by default in the minimal template:
~~~ ~~~
[user@F23-Minimal ~]$ su - [user@your-new-clone ~]$ su -
[user@F23-Minimal ~]$ dnf install sudo [user@your-new-clone ~]$ dnf install sudo
~~~ ~~~
The rsyslog logging service is not installed by default. All logging is now being handled by the systemd journal. Users requiring the rsyslog service should install it manually. Customization
-------------
To access the journald log, use the `journalctl` command. Customizing the template for specific use cases normally only requires installing additional packages.
The following table provides an overview of which packages are needed for which purpose.
### as a NetVM As expected, the required packages are to be installed in the running template with the following command. Replace "packages` with a space-delimited list of packages to be installed.
If you want to use this template to for standard NetVMs you should install some more packeges:
~~~ ~~~
[user@F21-Minimal ~]$ sudo dnf install NetworkManager NetworkManager-wifi network-manager-applet wireless-tools dbus-x11 dejavu-sans-fonts tinyproxy [user@your-new-clone ~]$ sudo dnf install packages
~~~ ~~~
And maybe some more optional but useful packages as well: Use case | Description | Required steps
--- | --- | ---
**Standard utilities** | If you need the commonly used utilities | Install the following packages: `pciutils` `vim-minimal` `less` `psmisc` `gnome-keyring`
**FirewallVM** | You can use the minimal template as a [FirewallVM](/doc/qubes-firewall/), such as the basis template for `sys-firewall` | No extra packages are needed for the template to work as a firewall.
**NetVM** | You can use this template as the basis for a NetVM such as `sys-net` | Install the following packages: `NetworkManager` `NetworkManager-wifi` `network-manager-applet` `wireless-tools` `dbus-x11 dejavu-sans-fonts` `tinyproxy`.
**NetVM (extra firmware)** | If your network devices need extra packages for the template to work as a network VM | Use the `lspci` command to identify the devices, then run `dnf search firmware` (replace `firmware` with the appropriate device identifier) to find the needed packages and then install them.
**Network utilities** | If you need utilities for debugging and analyzing network connections | Install the following packages: `tcpdump` `telnet` `nmap` `nmap-ncat`
**USB** | If you want USB input forwarding to use this template as the basis for a [USB](/doc/usb/) qube such as `sys-usb` | Install `qubes-input-proxy-sender`
**VPN** | You can use this template as basis for a [VPN](/doc/vpn/) qube | Use the `dnf search "NetworkManager VPN plugin"` command to look up the VPN packages you need, based on the VPN technology you'll be using, and install them. Some GNOME related packages may be needed as well. After creation of a machine based on this template, follow the [VPN howto](/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager) to configure it.
~~~ Logging
[user@F21-Minimal ~]$ sudo dnf install pciutils vim-minimal less tcpdump telnet psmisc nmap nmap-ncat gnome-keyring -------
~~~
If your network device needs some firmware then you should also install the corresponding packages as well. The `lspci` and `dnf search firmware` command will help to choose the right one :) The `rsyslog` logging service is not installed by default, as all logging is instead being handled by the `systemd` journal.
Users requiring the `rsyslog` service should install it manually.
### as a ProxyVM To access the `journald` log, use the `journalctl` command.
If you want to use this template as a ProxyVM you may want to install even more packages
#### Firewall
This template is now ready to use for a standard firewall VM.
#### VPN
The needed packages depend on the VPN technology. The `dnf search "NetworkManager VPN plugin"` command may help you to choose the right one. You should also install the corresponding GNOME related packages as well.
[More details about setting up a VPN Gateway](/doc/vpn/#proxyvm)
#### TOR
[UserDoc/TorVM](/wiki/UserDoc/TorVM)