similar to: [PATCH node-image] readonly rootfs setup

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 fixes a few boot,install and reboot items - creates and adds entries in rwtab.d/ovirt for /live and /boot - unblacklists /boot so the directory is there on boot - touches random-seed to fix a reboot error --- common-blacklist.ks | 2 +- common-post.ks | 5 +++++ 2 files changed, 6 insertions(+), 1 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index

Virtual networks can now be created and destroyed with a r/o filesystem. Signed-off-by: Michael Burns <mburns at redhat.com> --- common-post.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/common-post.ks b/common-post.ks index 44a0270..5531e08 100644 --- a/common-post.ks +++ b/common-post.ks @@ -151,6 +151,7 @@ rm -f /etc/cron.daily/logrotate sed -i

Hello everyone, I have a problem with setting up a diskless system on CentOS. Currently I have successfully set up a small cluster of diskless clients following the following available HowTos: http://wiki.centos.org/HowTos/DisklessClients https://coda.jlab.org/wiki/index.php/CentOS6_Linux_Diskless_Setup The client system is CentOS 5.10 and the system is read-only. It has been working fine for a

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.

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.

Hi everyone I'm trying to create system with RO root filesystem, so i'm using /etc/sysconfig/readonly-root along wih /etc/rwtab and /etc/statetab. Apart of numerous problems with services running on RO filesystem (which i'm constantly resolving adding entries to /etc/statetab) one thing popped up. I'm unable to add user or change his password. Error is 'cannot lock

Due to a critical dracut bug, and a strong dev focus on F16, we're dropping all F15 recipes. Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/ovirt15-install.ks | 1 - recipe/ovirt15-minimizer.ks | 1 - recipe/ovirt15-pkgs.ks | 2 - recipe/ovirt15-post.ks | 145 ------------------------------------------ recipe/ovirt16-install.ks | 2 +-

Hi, I have OS 'image' that boots via PXE and mounts over NFS. (7.5.1804). I am wanting to explore allowing cgroup usage on this configuration. The root image is exported read-only over NFS and am using statetab & rwtab to allow some persistent parts of the filesystem as well as read/write where needed. I have tried setting /sys in the statetab and this causes the machine to fail,

> On 1/3/23 05:17, Orion Poplawski wrote: >> On 12/30/22 04:06, Jelle de Jong wrote: >>> On 12/27/22 22:55, Gordon Messmer wrote: >>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>>>> causing sssd.service systemctl failures all over my CentosOS >>>>>

I am looking at having a read only box, it will not use a swap partition. Any recommendations? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333

On 1/3/23 13:41, Simon Matter wrote: >> On 1/3/23 05:17, Orion Poplawski wrote: >>> On 12/30/22 04:06, Jelle de Jong wrote: >>>> On 12/27/22 22:55, Gordon Messmer wrote: >>>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>>>>> causing sssd.service

> On 1/3/23 13:41, Simon Matter wrote: >>> On 1/3/23 05:17, Orion Poplawski wrote: >>>> On 12/30/22 04:06, Jelle de Jong wrote: >>>>> On 12/27/22 22:55, Gordon Messmer wrote: >>>>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is

Starting udev: /sbin/restorecon set context /dev/.initramfs/live->system_u:object_r:device_t:s0 failed:'Read-only file system' Resolves: rhbz#675868 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-post.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/recipe/common-post.ks b/recipe/common-post.ks index a17e899..cf5bc72 100644 ---

Hello Marcin, On 2018-09-04, Marcin Trendota <moonwolf.rh at gmail.com> wrote: > > I'm trying to create system with RO root filesystem, so i'm using > /etc/sysconfig/readonly-root along wih /etc/rwtab and /etc/statetab. > > Apart of numerous problems with services running on RO filesystem (which > i'm constantly resolving adding entries to /etc/statetab) one

This will facilitate the switch to readonly rootfs. The current method will not work when symlinking /etc/mtab to /proc/mounts as the udev label /BOOT is used rather than /dev/sda1 or similar. The same output is generated and has been verified to install correctly. --- scripts/ovirt-config-boot | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git

This set of patches introduces support for multipath devices for storage. Comments and suggestions are appreciated. Mike

This patch goes with the node patch just sent, and is ready for pushing upstream. I'll be doing the blacklisting in a later patch once this is upstream.

The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated. These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated. Mike

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG: