similar to: How to rebuild the Centos 6.4 iso images with the same contents as officially released iso images ?

Use findfs LABEL=ABC and mount LABEL=ABC instead. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 29 ++++++++++++++++------------- scripts/ovirt-config-storage | 2 -- scripts/ovirt-functions | 18 ++++++++++-------- 3 files changed, 26 insertions(+), 23 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index

- dracut does not currently support booting a dmsquash file system on an iscsiroot - can not be configured in standalone mode since networking is not up, although works fine if ovirt-config-setup is run once booted. Signed-off-by: Joey Boggs <jboggs at redhat.com> --- recipe/common-pkgs.ks | 1 + scripts/ovirt-config-boot | 67 ++++++++++++++++----

This lays the groundwork for setting Root and RootBackup onto individual partitions for multiple disk installations in the future. Install, removal, upgrade testing has been performed and all seems to work at this point. --- scripts/ovirt-config-boot | 15 ++++++++------- scripts/ovirt-config-storage | 28 +++++++++++++++------------- scripts/ovirt-config-uninstall | 2 ++

This is the second generation of the edit-livecd tool that replaces our original bash script with a python version and aims to reuse as much as the livecd-creator libraries as possible. The main reason for the new creator class is to avoid the need for a kisckstart file in order to edit an existing livecd image. edit-livecd is useful for people who don't have the development and yum

Quote everywhere that we reference wwid in o-c-storage, o-c-boot and ovirt-functions. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 6 +- scripts/ovirt-config-storage | 178 +++++++++++++++++++++--------------------- scripts/ovirt-functions | 38 +++++----- 3 files changed, 111 insertions(+), 111 deletions(-) diff --git

I recently asked about copying a running system to a new drive. As a postscript, I'm wondering if it would have been preferable to run the machine under a Live OS, and simply copy the root partition to the new drive? Eg while running under the LiveOS, # mkdir /mnt/old /mnt/new # mount /dev/sda7 /mnt/old # mount /dev/sdb6 /mnt/new # cp -avx /mnt/old /mnt/new or # rsync -ax

Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com: > Reason: Message body is too big: 1780404 bytes with a limit of 512 KB So previous not on the mailinglist. > Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST) > From: Michael Szerencsits <szerencsits.michael at gmx.at> > To: syslinux at zytor.com > Subject: efi64 boot fail during download from kernel and initrd

Hi, Do CentOS 7 installs not automatically use a closest mirror for installing like Fedora does, or is that due to the way I'm starting the install (virt-install)? Background: I'm trying to find the best way to do installs using basic local media (network install, but *without* the need to download the squashfs.img for every install) but without a full local mirror. On Fedora (25), it

This completes the switch to ext3 backed root partitions. /boot is now contained on each Root/RootBackup partition. On install grub is updated to read and boot from the correct partition as well. --- scripts/ovirt-config-boot | 29 ++++++++++++------------ scripts/ovirt-config-storage | 47 +++++++++++---------------------------- scripts/ovirt-config-uninstall | 5 +---

Used in conjunction with livecd-iso-to-iscsi. Creates a local boot partition with vmlinuz/initrd and grub configuration. Disk Partitioning > enable iscsi target > configure storage > local install and reboot --- scripts/ovirt-config-boot | 131 +++++++++++++++++++-------------- scripts/ovirt-config-storage | 164 +++++++++++++++++++++++++----------------- tools/livecd-iso-to-iscsi

Hi, I have two questions: (1) In 7.3 CentOS released a rootfs tar for ARM64. I can no longer find this under the 7.5 release. Furthermore, I could also not find anything on the ISO that seems rootfs-like in any near complete state. The closest was the LiveOS/rootfs.img, but it seems this is not a complete fs as yum is missing components, for example. So my question is: Is there any way to still

--- scripts/install.py | 247 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 247 insertions(+), 0 deletions(-) create mode 100755 scripts/install.py diff --git a/scripts/install.py b/scripts/install.py new file mode 100755 index 0000000..ddffb53 --- /dev/null +++ b/scripts/install.py @@ -0,0 +1,247 @@ +#!/usr/bin/python +# +# install.py - configure local boot/root disk

Previous implementation had staticly defined partitions to remove. This would break in the case of split Root and HostVG devices. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 11 +-------- scripts/ovirt-config-uninstall | 48 ++++++++++++++++++++++++--------------- scripts/ovirt-functions | 33 +++++++++++++++++++++++++++ 3 files

Patch set fixes issues with image size increase when using edit-livecd Also address issue with ext4 root fs

Old edit-livecd just kept adding to the ext2 fs image which meant it never decreased in size even if files were removed. New functionality does multiple passes of ext2fs creation. First pass creates a new ext2fs from the image file inside the squashfs. This first pass is to allow the user to optionally increase the filesystem size. If the -s parameter is omitted the existing size is used and

top-level kickstart file contains only includes, example custom-template.ks is provided with documented customization points. Signed-off-by: Alan Pevec <apevec at redhat.com> --- recipe/common-manifest-post.ks | 31 +++++++++++ recipe/common-manifest-pre.ks | 11 ++++ recipe/common-post-chroot.ks | 46 ++++++++++++++++ recipe/common-post.ks | 24 +++++++++

This enables the ability to take the ovirt-node-image iso and deploy it to an iscsi disk. It also provides a sample pxe configuration for booting based on the iscsi root device. Includes support for user/password as well as reverse chap user/password. --- Makefile.am | 1 + livecd-iso-to-iscsi | 201 ++++++++++++++++++++++++++++++++++++++++++++++ ovirt-node-image.spec.in |

rebased it against current next-devel --- scripts/ovirt-config-boot | 15 ++++++++------- scripts/ovirt-config-storage | 28 +++++++++++++++------------- scripts/ovirt-config-uninstall | 2 ++ scripts/ovirt-functions | 8 +++++--- 4 files changed, 30 insertions(+), 23 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index ed2bb9f..01c1821

Purpose : fail iso build on encountering error in arbitrary code '$CODE' 1. export 'WDIR' , for 'CODE' to pick-up location to create 'fail' file to indicate failure, note that it may not always be possible to return some error code on failure in 'CODE' 2. 'set' commands enclosing 'CODE' will not be required 3. 'CODE' is

Hi, On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way it always has worked for other versions, incl. Fedora 22 VM's), does not work for me. I use virt-install with a local copy of the "images/pxeboot" tree. It all stops with: ... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. dracut-initqueue[551]: Warning: Could not boot.