similar to: unionfs and centos 4.4

I want to install centos 4.4 in a CF card and use a ram disk for operations. It means no hard disk attached to the computer. The machine will only run an antispam antivirus gateway. What documents can I read to make /var and /tmp sit on a ram disk and boot the operating system in read write and switch to read only after booting? thanks, --

G'day ... David Schultz, in his spare time, has been working through some of the issues I've been able to 'tweak' in the unionfs code ... as he is currently working on forward-patching it to -CURRENT right now, he can't commit the code to the -STABLE tree ... in order to allow others using unionfs to test the patch (I've been running it a few weeks now on a very heavily

Is it possible to emulate a unionfs with zfs and zones somehow? My zones are sparse zones and I want to make part of /usr writable within a zone. (/usr/perl5/mumble to be exact) I can''t just mount a writable directory on top of /usr/perl5 because then it hides all the stuff in the global zone. I could repopulate it in the local zone but ugh that is unattractive. I''m hoping

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

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 |

Subject of Hint: How to create a Bootable Live CD/DVD from your Linux From Scratch (LFS) build Good day from Singapore, I am Mr. Turritopsis Dohrnii Teo En Ming, based in Singapore. I have recently *successfully* created my own custom Linux distribution called Teo En Ming Linux 2020.03 (FINAL), which is based on Linux From Scratch 20200302-systemd book and Linux Kernel 5.5.7, on 12 March

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.

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'

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

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

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, I've been trying to setup a dual livecd. However I am getting an error with parsing the isolinux.cfg. I am using 3.84. the relevant section of the isolinux.cfg is as follows label LiveCD1 kernel vmlinuz1 append livecd=livecd1 initrd=initrd1.gz root=/dev/rd/3 acpi=on splash=silent vga=788 keyb=us fstab=rw,noauto label LiveCD2 kernel vmlinuz2 append livecd=livecd2

Would it be possible to append the device syslinux booted from to /proc/cmdline? It would be nice to have a method of grepping /proc and /sys to locate the correct boot device for a LiveCD/USB instead of looking for it or manually appending it to the cfg file. I'm the creator of Parted Magic and people are starting to do odd things with it. They will boot the CD and have Parted Magic on a USB

Hello Peter & Jeremy, I've found an ordinary desktop PC (with Phoenix Award BIOS 6.00PG) that won't boot off a USB stick created by livecd-tools-024 with syslinux (tested both versions 3.75 and 3.81). The boot process drops to the "boot:" prompt with an error message: could not find kernel image: linux The same USB stick boots fine on any other computer I could find.

Hi people Just switched to Dovecot yesterday, and I've already got about five reports of users with duplicate mail in their inbox :-/. Not as bad as lost email, mind you, but pretty annoying still. Checking the server log, it says: postfix/smtpd: disconnect from unknown deliver: msync() failed with index file maildir/dovecot.index: Input/output error unionfs: new lower inode mtime

I tried making my own LiveCD according to the instructions on the project site. First, applause, the basic procedure works like a charm. It's really easy to do and works right from the beginning (I'm building it inside a VM). I tried the minimal and the desktop version (with a few changes). I have encountered a few problems and have some questions. The German keyboard I set in the

http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz.sig http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz.sig A combined release announcement for a change. :) Largest changes since v1.1.4: * Dovecot prints an informational message about authentication problems

http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP

http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz.sig http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz.sig A combined release announcement for a change. :) Largest changes since v1.1.4: * Dovecot prints an informational message about authentication problems

http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP