I have been using the LiveCD format extensively on majority of my
machines throughout the years as it brings, among other things, enhanced
protection to my root (/) image (as this is preserved throughout the
life of the session and is restored after each reboot). I have, however,
two fundamental issues I need to clear up:
1. How is the LiveCD file system constructed/built? I've read a variety
of articles and it seems that it is close to the UnionFS (rom+ram
"partitions"), but I am not sure that is used with the new versions of
Linux. I see there are multiple loop mounts on the system, but can't
figure out what they are.
2. My understanding is that all files that are modified in the "live"
image are stored "separately" on a "ram partition". If that is indeed
the case, can I look at what has been "modified" during the live
session? This is easily visible and implemented in UnionFS by a simple
"ls" on the ram (i.e. the read-write) part of the UnionFS, but I am not
sure how this is organised on the LiveCD system.
Any help and advice on the above two issues is appreciated. Thanks!
I'm trying to use livecd to test fedora upgrades non-destructively. To make this work, I really need to be able to use the persistent overlay to fix drivers. I'm using the standard command:
livecd-iso-to-disk --overlay-size-mb 2047 /path/to/live.iso /dev/sdb1
However, this is not working as I'd expect. If I boot from the resulting usb drive and change the configuration (eg to enable sshd), then the changes are lost on reboot.
Have I misunderstood how persistent overlays are supposed to work - I'd interpreted the documentation to mean that the overlay can persist changes from /, as well as just providing a persistent overlay to /home?
I've been building personal Fedora remixes since Fedora 9. I just started building one based on Fedora 16 yesterday. I have noticed two errors:
1) When it builds, everything goes fine... and then it counts down the percentage of the iso it is finishing up... and then it give an isohybrid error:
isohybrid: /var/tmp/imgcreate-1J2TbZ/out/MontanaLinux-F16-001-i686.iso: seek error - 6: Invalid argument
The .iso does finish and it is bootable... so perhaps that error is inconsequential.
2) When I boot the CD, it works fine... but when I do an install... the install goes fine but at the very end where it is installing the bootloader I get a really long anaconda error:
Attached file (MontanaLinux-F16-001-intsall-bug.txt.gz)
That is a big bug making a non-usable system. That was done in a KVM VM. I used gparted to partition the virtual disk before I ran the installer. It has a msdos partition table. I have not tried the install on physical machine... yet.
I was just curious if anyone has run into these errors.
704 Church Street
Belgrade, MT 59714
First of all, I apologize for my bad English level !
I'm trying to build a hardened live system. I want to encrypt the / partition. In my kickstart file I use : part / --size 1024 --encrypted --passphrase=pass1
It doesn't work ... I want to enter the passphrase before the system run ! Logically the system don't be able to boot without passphrase. But actually the system boot without it.
Are there anybody who have ever try to use encrypted partition in a live system ?
I'm new in fedora, if you have suggestion about hardening or if you have ever build a hardened live system, I will be happy to get some information ! :)
Thank you for your reply
Tag 'livecd-tools-16.7' created by Brian C. Lane <bcl(a)redhat.com> at 2011-10-24 17:48 +0000
Tag as livecd-tools-16.7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----
Changes since livecd-tools-16.6:
Brian C. Lane (2):
Add dracut args to EFI grub.conf creation (#748344)
Makefile | 2 +-
imgcreate/live.py | 11 ++++++++---
2 files changed, 9 insertions(+), 4 deletions(-)
How does one build a Fedora LIveCD without a desktop but with a WM and GUI?
I was looking at the fedora-livecd-lxde.ks file and noticed the following:
# create /etc/sysconfig/desktop (needed for installation)
cat > /etc/sysconfig/desktop <<EOF
# Show harddisk install on the desktop
sed -i -e 's/NoDisplay=true/NoDisplay=false/' /usr/share/applications/liveinst.desktop
cp /usr/share/applications/liveinst.desktop /home/liveuser/Desktop
How do I modify at least these parts? I would like to still have the ability to log in as a liveuser, and then install to HDD (for this, I guess I will need anaconda and firstboot).
In principle, I'd have thought that this was possible, if where binaries need to be run in the creation process the inputs/outputs are compatible between the architectures and the mappings between which binaries to use are properly managed.
however, it doesn't seem to work:
setarch x86_64 livecd-creator -c whatever.ks
setarch: x86_64: Unrecognized architecture
I'm using f15, util-linux-2.19.1-1.4.fc15.i686 (for setarch). livecd-tools-15.7-1.fc15.i686
(I'm assuming that using setarch is the right approach to use, otherwise, livecd-creator just builds for the architecture that it's run on .