similar to: Questions on custom LiveCD

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 |

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

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

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

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.

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

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe. Removes old sub packages form ovirt-node, stateless, logos, selinux. Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221 Added License file.

On Tue, Feb 14, 2017 at 09:12:10AM +0100, Pino Toscano wrote: > Introduce a new API to create a new squashfs filesystem out of a path > in the guest. It can be configured to exclude paths based on patterns, > and to select which compression use for the filesystem. > > The advantage of running mksquashfs directly in the appliance is that > ownerships are properly saved, as

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

2014-07-16 0:58 GMT+04:00 Richard W.M. Jones <rjones@redhat.com>: > BTW is there any reason to use FUSE instead of using the libguestfs > API directly? Using the API is going to be much more robust. I'm need to create squashfs from root file system. I see some methods like tar and cpio, but i can't find anything suitable for creating squashfs. Also i can't use root

Ray Van Dolson wrote: > On Tue, Apr 22, 2008 at 12:47:39PM +0100, Plant, Dean wrote: >> I would like one of my kickstart scripts to prompt for disk and >> networking only. Commenting out the disk and network settings makes >> the installer prompt for disk settings but not for network settings, >> they default to DHCP. Any idea's how to fix this? > > I'm

Hi, this patch series does changes mostly in virt-dib, few bug fixes and a couple of new features (mostly implemented upstream already). In addition, one new API is added, and a new optional argument for an existing API is added (the latter is not needed, but could be useful anyway). Thanks, Pino Toscano (10): dib: fix listing envvars in fake-sudo dib: source dib "die" script in

2014-07-16 1:12 GMT+04:00 Richard W.M. Jones <rjones@redhat.com>: > I believe I investigates making a squashfs from within libguestfs, and > although it's possible, it is not possible to stream the output > (unlike, say, guestfs_tar_out or guestfs_cpio_out). This means that > the maximum size of the squashfs would be quite small. > > Nevertheless we could add an API to

Hi, I've got a Redhat 7.2 system: Celeron 400 512MB RAM 18GB SCSI HD (/boot (ext2fs), / (ext3fs)) 40GB IDE HD (/ (ext3fs)) I run a bunch of services on the box (apache + mod_perl, MYSQL, Samba, etc) but the system is not under heavy load. This system has performance issues reading/writing to the ext3fs filesystems. The performance issues cropped up when I installed Redhat 7.2. Previously

Hello list, I use the livecd-creator to customize my own livecd iso. I use the kickstart config file from https://raw.githubusercontent.com/CentOS/sig-core-livemedia/master/kickstarts/centos-7-livecd.cfg. #livecd-creator -v --config centos-7-livecd.cfg --cache /var/cache/livecd finally I got a iso, but the iso is strange. The offical distribution iso is

Hello All, I have been doing some research to find a method to increase the performance of writes to the hard drives in my servers. I am running Samba and all writes to the server hard drives are taking at least 3 to 10 times (It varies) the amount of time it took to write such files on our older Windows NT 4.0 File Server. The following information is provided to keep this issue on track...

Hi! I've upgraded my seawolf to ext3fs with the packages from Roswell (kernel, filesystem, mount, ....), but when doing 'tune2fs -j', it mentions 'Ext3fs version 0.0.5b'...? Isn't version 0.0.7a the latest?? Why isn't that version included in the Roswell kernel, but an older version is? And how can i upgrade my version of ext3fs? Thanks! Bart Verwilst

Hi, I am having some problem with LOCALBOOT and menu.c32 This is my isolinux.cfg: ------------------------------------------- default menu.c32 timeout 50 prompt 0 ontimeout local menu title "TITLE" label livecd menu default manu label "LiveCD" kernel gentoo append initrd=initrd.igz root=/dev/ram0 init=/linuxrc looptype=squashfs loop=/ livecd.squashfs

Hello fellow syslinux/extlinux users! Please forgive the long post, but I believe my problem warrants the background info to understand the issue. I've developed a specialized spin of Fedora that runs off CompactFlash. The spin is actually produced by the livecd-tools package and is then transferred to the CF card -- which has been formatted with ext3 -- using livecd-tools'

Good evening. We have some heavy-loaded servers on ext2, and we want to migrate to ext3fs. But we need full and stable quota support. I have headrd that there are some problems in quota usage under ext3fs. Is it true? Should we decline the ext3 usage as impossible in our servers? We need high-level stability in our server (hosting). Thanks before. -- Best regards,