how does the new systemd effects the live-cd
by Ronen B
Hi there.
Iv'e making live cd's since Fedora8, and now, after a while I'm back for
the latest version.
I understand that since fedora 15 the new init system is systemd, so what's
the effect on the building or running process of the new Fedora15/16 ?
Is the old KS files still valid?
I would appreciate any info or references.
Thanks
R.B
12 years
Work around for recent zfs-fuse package addition
by Scott Dowdle
Greetings,
I periodically rebuild a personal Fedora remix to have all of the updates... and am not working with Fedora 16. In the x86_64 version of my remix I include all of the KVM virtualization stuff. It seems that a recent set of updates has caused zfs-fuse to become a dependency where it wasn't previously. That's fine... but I noticed that my remix would fail to build near the tail end of the process. Since the initial failure there have been a few more waves of updates and I've still been unable to complete a rebuild.
I finally figured out how to work around the issue. When zfs-fuse gets installed inside of the build root it appears to start up on the build host. By killing the top level zfs-fuse process manually with kill and making sure it is no longer running, I was able to finish the build process. From the host node context zfs-fuse was not enabled and the systemctl stop zfs-fuse would say it wasn't running... I'm guessing because it was installed and started up by the livecd-creator build process rather than on the host node proper. It appears that if zfs-fuse is allowed to stay running the build process will fail but by manually killing it ('pstree -nup | less' search for parent zfs-fuze process and kill it) it will complete. I haven't really looked for a way to automate the kill and just do it manually while the remix is building once I notice that the zfs-fuse service is running.
I haven't looked for nor filed a bug because the path of blame is unclear to me... and I don't know that it affects many Fedora users in the wild other than us respin / remix builders... but I thought I'd pass it along for anyone else who might care.
The only other time I've run into an issue with a particular package breaking the build process was with google-chrome browser. Over a year ago having google-chrome browser listed in my remix package list, when google-chrome gets installed it does a service restart (I don't recall which one, atd maybe?) and coincidentally the remix build process would fail near the tail end. I do not know if that is the case now because at that point I took google-chrome out of my package list and I have yet to add it back. It certainly is not a Fedora provided package so I wouldn't expect Fedora to troubleshoot such an issue.
Any any event, from those two incidents it has lead me to believe that if a package post-install script does something to the state of services, that the remix build process will probably fail. I'm not sure who cares or if they'd like further investigation in an effort to validate the problem and work towards a solution or not... but anyway... feel free to comment if desired.
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
12 years
Writing to /mnt/live/ on shutdown
by Mads Kiilerich
Hi
I have a custom built Live image that is based on fedora-live-desktop.
It is written to USB with livecd-iso-to-disk .
I would like to automatically stop some service and save a bit of data
to the USB device when shutting down.
There are many ways of doing it that works just fine and can write to
/mnt/live/ during normal operation. But for some (various?) reasons none
of them works when shutting down. Working on a live image and during
shutdown makes it a bit tricky to debug.
Have you been able to do something like that?
Or how would you do it and which obstacles do you expect to meet?
/Mads
12 years
Boot over NFS/PXE
by Francesco Frassinelli
Hi all,
I need to boot a livecd on some hard disk less clients. I tried to use
livecd-iso-to-pxe, but in my case it unacceptable to load the whole iso
into initrd (the iso is not small).
I made a custom livecd adding dracut-network package, I mounted
squashfs/root image, exported with nfs, and I've tried to boot the clients
with root=nfs:192.168.1.50:/home/frafra/root/ selinux=0, but Fedora gives
me many errors because it can't write on it.
I found this old thread
http://comments.gmane.org/gmane.linux.redhat.fedora.livecd/4261 but it
doesn't work for me.
Is there a way to get a livecd behaviour with this nfs directory? Or can I
combine the isolinux.cfg livecd options with
root=nfs:192.168.1.50:/home/frafra/
(where it could found the iso or the mounted iso)?
I'm using dnsmasq with its internal tftp server, which gives vmlinuz0 and
initrd0.img (copied from livecd), pxelinux.0 and a configuration file with
the above root=nfs:[...] selinux=0 options.
Thanks,
Francesco Frassinelli
12 years
Branch 'f14-branch' - Makefile
by Brian C. Lane
Makefile | 1 +
1 file changed, 1 insertion(+)
New commits:
commit 0e40e82d2450491710ebd25dcfc0615eebe0b1db
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Fri Nov 18 09:52:39 2011 -0800
Install edit-livecd to /usr/bin
diff --git a/Makefile b/Makefile
index c15696d..43a1607 100644
--- a/Makefile
+++ b/Makefile
@@ -26,6 +26,7 @@ install: man
$(INSTALL_PROGRAM) -D tools/image-creator $(DESTDIR)/usr/bin/image-creator
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-disk.sh $(DESTDIR)/usr/bin/livecd-iso-to-disk
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-pxeboot.sh $(DESTDIR)/usr/bin/livecd-iso-to-pxeboot
+ $(INSTALL_PROGRAM) -D tools/edit-livecd $(DESTDIR)/usr/bin/edit-livecd
$(INSTALL_PROGRAM) -D tools/mkbiarch.py $(DESTDIR)/usr/bin/mkbiarch
$(INSTALL_DATA) -D AUTHORS $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/AUTHORS
$(INSTALL_DATA) -D COPYING $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/COPYING
12 years
Branch 'f15-branch' - Makefile
by Brian C. Lane
Makefile | 1 +
1 file changed, 1 insertion(+)
New commits:
commit 610e0bd7b36a5c5ba1bcaee3de2ed3e906eb7604
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Fri Nov 18 09:52:39 2011 -0800
Install edit-livecd to /usr/bin
diff --git a/Makefile b/Makefile
index a71f6f7..6cb072b 100644
--- a/Makefile
+++ b/Makefile
@@ -26,6 +26,7 @@ install: man
$(INSTALL_PROGRAM) -D tools/liveimage-mount $(DESTDIR)/usr/bin/liveimage-mount
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-disk.sh $(DESTDIR)/usr/bin/livecd-iso-to-disk
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-pxeboot.sh $(DESTDIR)/usr/bin/livecd-iso-to-pxeboot
+ $(INSTALL_PROGRAM) -D tools/edit-livecd $(DESTDIR)/usr/bin/edit-livecd
$(INSTALL_PROGRAM) -D tools/mkbiarch.py $(DESTDIR)/usr/bin/mkbiarch
$(INSTALL_DATA) -D AUTHORS $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/AUTHORS
$(INSTALL_DATA) -D COPYING $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/COPYING
12 years
Branch 'f16-branch' - Makefile
by Brian C. Lane
Makefile | 1 +
1 file changed, 1 insertion(+)
New commits:
commit 22f663f369bcfadd6fd6fb91bfa052b30e248832
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Fri Nov 18 09:52:39 2011 -0800
Install edit-livecd to /usr/bin
diff --git a/Makefile b/Makefile
index a2f9f78..e35cacf 100644
--- a/Makefile
+++ b/Makefile
@@ -26,6 +26,7 @@ install: man
$(INSTALL_PROGRAM) -D tools/liveimage-mount $(DESTDIR)/usr/bin/liveimage-mount
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-disk.sh $(DESTDIR)/usr/bin/livecd-iso-to-disk
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-pxeboot.sh $(DESTDIR)/usr/bin/livecd-iso-to-pxeboot
+ $(INSTALL_PROGRAM) -D tools/edit-livecd $(DESTDIR)/usr/bin/edit-livecd
$(INSTALL_PROGRAM) -D tools/mkbiarch.py $(DESTDIR)/usr/bin/mkbiarch
$(INSTALL_DATA) -D AUTHORS $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/AUTHORS
$(INSTALL_DATA) -D COPYING $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/COPYING
12 years
Makefile
by Brian C. Lane
Makefile | 1 +
1 file changed, 1 insertion(+)
New commits:
commit 985d25d92777b08b7d3db2951e9e256a785cb3a1
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Fri Nov 18 09:52:39 2011 -0800
Install edit-livecd to /usr/bin
diff --git a/Makefile b/Makefile
index c2617f8..ca9c004 100644
--- a/Makefile
+++ b/Makefile
@@ -26,6 +26,7 @@ install: man
$(INSTALL_PROGRAM) -D tools/liveimage-mount $(DESTDIR)/usr/bin/liveimage-mount
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-disk.sh $(DESTDIR)/usr/bin/livecd-iso-to-disk
$(INSTALL_PROGRAM) -D tools/livecd-iso-to-pxeboot.sh $(DESTDIR)/usr/bin/livecd-iso-to-pxeboot
+ $(INSTALL_PROGRAM) -D tools/edit-livecd $(DESTDIR)/usr/bin/edit-livecd
$(INSTALL_PROGRAM) -D tools/mkbiarch.py $(DESTDIR)/usr/bin/mkbiarch
$(INSTALL_DATA) -D AUTHORS $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/AUTHORS
$(INSTALL_DATA) -D COPYING $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION)/COPYING
12 years
Restoring LiveCD via the Network.
by Williamson Grant
Maybe this is a question for the anaconda mailing list, let me try here first.
Is there anyway to restore a livecd via the Network?
i.e.
Boot from a boot.iso, launches anaconda performs a network/livecd downloading/installing via the network the squashfs.img.
Why would I want to do this? Looking for an alternative to Clonezilla. i.e. native anaconda install ensures luks encryption is unique for each machine.
I know how to create a Network installation and perform a package for package automated installation, however looking for a quicker alternative.
I am not asking how to implement this, just wondering if anyone knows what parameters Anaconda would require, if indeed this is possible.
12 years, 1 month
