You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Marek Marczykowski 3acbeb6d6f
Add standalone-template.conf to rpm
14 years ago
appmenus
base_rpms
clean_images
keys
mnt
netvm
qubeized_images
rpm
rpms_3rd_party
rpms_to_install_x64
template
vm_conf_files
vm_initramfs_patches
vm_kernels_x64
.gitignore
README
TODO
add_3rd_party_software.sh
appvm.buildlog
build_template_rpm
cleanup_image
create_apps_for_templatevm.sh
create_apps_templates.sh
dispvm-dotfiles.tbz
fedorize_image
mount_root.sh
qubeize_image
rpms_to_install
templates.spec Add standalone-template.conf to rpm 14 years ago
version_appvm
vm_kernels

README

The Template Builder
======================

1) First, create a clean image of Fedora Linux install. You can use the fedoraize_image
script for this:

fedorize_image <image> <file-with-packets-lists>

NOTE: The fedorize_image script can be also used to update an image -- it
automatically assumes the update mode if the <image> already exists.

The fedorize image takes care about creating proper partition table, that
contains root and swap partitions, to create the initial rpm database, and
install some core packages.

We assume that the image will have a two-partition layout:

img1 <--- the root fs (/)
img2 <--- the swap

2) Update symlinks in rpms_to_install_XXX/ so that they point to the current version
of Qubes-specific rpms to install you want to use (e.g. qubes-gui-vm, etc).

3) Now, you can "qubeize" the image. This must be done as root. E.g.:

# ./qubeize_image <img> <template-name>

4) Make sure the symlinks in vm_kernels_XXX/ point to correct kernel and initramfs
files you want to use for the template:

4a) In order to prepare a patched initramfs file, use the
patch_appvm_initramfs.sh program that is installed as part of
qubes-core-dom0.rpm:

# /usr/lib/qubes/patch_appvm_initramfs.sh \
	<original_initrafms> \
	 <filename_for_patched_initramfs> \
	 /abs_path/vm-initramfs-patches/qubes_cow_setup.sh 


5) Finally, build the Template RPM (do it as normal user, not root), e.g.: 

$./build_rpm <name>

The resulting rpm is stored in rpm/noarch directory.