qubes-doc/managing-os/templates/fedora-minimal.md

76 lines
3.8 KiB
Markdown
Raw Normal View History

2014-07-07 05:11:06 -04:00
---
2015-04-10 16:17:45 -04:00
layout: doc
title: Fedora Minimal Template
permalink: /doc/templates/fedora-minimal/
redirect_from:
2016-05-21 10:49:01 -04:00
- /doc/fedora-minimal/
- /en/doc/templates/fedora-minimal/
- /doc/Templates/FedoraMinimal/
- /wiki/Templates/FedoraMinimal/
2014-07-07 05:11:06 -04:00
---
Fedora - minimal
================
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
------------
2014-07-07 05:11:06 -04:00
The Fedora minimal template can be installed with the following command:
2014-07-07 05:11:06 -04:00
~~~
[user@dom0 ~]$ sudo qubes-dom0-update qubes-template-fedora-23-minimal
~~~
2014-07-07 05:11:06 -04:00
The download may take a while depending on your connection speed.
Duplication and first steps
---------------------------
2014-07-07 05:11:06 -04:00
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.
2014-07-07 05:11:06 -04:00
~~~
[user@dom0 ~]$ qvm-clone fedora-23-minimal your-new-clone
~~~
2014-07-07 05:11:06 -04:00
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:
2014-07-07 05:25:02 -04:00
~~~
[user@your-new-clone ~]$ su -
[user@your-new-clone ~]$ dnf install sudo
~~~
2014-07-07 05:25:02 -04:00
Customization
-------------
2014-07-07 05:11:06 -04:00
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.
2014-07-07 05:11:06 -04:00
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.
2014-07-07 05:11:06 -04:00
~~~
[user@your-new-clone ~]$ sudo dnf install packages
~~~
2014-07-07 05:11:06 -04:00
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/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.
2014-07-28 10:23:49 -04:00
Logging
-------
2014-07-28 10:23:49 -04:00
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.
2014-07-28 10:23:49 -04:00
To access the `journald` log, use the `journalctl` command.
2014-07-28 10:23:49 -04:00