4d4f46e94c
Unfortunately our Copy-to-VM action is supported only by dolphin. We would probably like to switch to nautilus at some point, because it just starts up faster ;) But not now. |
||
---|---|---|
appmenus | ||
base_rpms | ||
clean_images | ||
fedorized_images | ||
keys | ||
mnt | ||
qubeized_images | ||
rpm | ||
rpms_3rd_party | ||
rpms_to_install_x64 | ||
vm_conf_files | ||
vm_initramfs_patches | ||
vm_kernels_x64 | ||
.gitignore | ||
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 | ||
README | ||
rpms_to_install | ||
templates.spec | ||
version_appvm | ||
vm_kernels |
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. 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.