I'm a Fedora remix maker and the following refers to Fedora 13 and the version of livecd-tools and livecd-creator currently shipping with it. I haven't yet advanced to making rpm packages for my minor modifications. I currently just do a few copy operations in the %post --nochroot section of my kickstart file.
The only thing I haven't figured out yet is how to replace the /isolinux/splash.jpg on the Live media. I thought just copying my desired jpg file to /usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg would do the trick as that appears to be the file referenced per this snooping:
# grep jpg /usr/lib/python2.6/site-packages/imgcreate/live.py
if self.__copy_syslinux_background(isodir + "/isolinux/splash.jpg"):
background = "menu background splash.jpg"
That doesn't seem to work. What file do I need to replace?
I'd appreciate it if someone in the know would answer the question rather than questioning my wanting to do it in the first place. :)
Thanks in advance,
704 Church Street
Belgrade, MT 59714
Sorry for sending it twice, I forgot the most important thing.
Currently, running an x86_64 system I can also re-spin 32-bit versions
by using "setarch i686" in the command line:
su -c "setarch i686 livecd-creator
But it does not work other way around. For example,
su -c "setarch x86_64 livecd-creator
gives an error _if run on 32-bit Fedora_. Same for another architecture.
I think there's something
wrong with this. Is it possible to create spins for other architectures?
Can it be fixed?
Misha Shnurapet, Fedora Project Contributor
shnurapet at fedoraproject.org, GPG: 00217306
I'm a user of Fedora 12. And I wanna make my own Live CD by using some
ways. I noticed livecd-creator works well and I read its read me under
/usr/share/doc, it looks like here's a chapter named "HOW THE LIVE CD
CREATOR WORKS" tell us how to make a Live CD manually. So I'm very
curious how this magic happened then a Live CD created.
I don't know Python at all so I take the steps by reading the
instruction. I made a fake root directory then it's a small Linux file
root file system. And I also copied isolinux.bin and kernel into the
isolinux directory. Of course I build a small isolinux.cfg with
append initrd=initrd.img root=LABEL=livecd
But I just copied initramfs from the fake root so it's normal that it
cannot mount root file system correctly after I start from the ISO
image I created. I noticed following error message.
Can't mount root file system.
mount: /dev/sr0 already mounted or /sysroot busy
So my problem is could anyone show me details how to create a live cd
by using commands manually and show me some tips to modify init script
in initrd then can mount root fs correctly?
Thanks very much.
In cases where a livecd is created, the iso label and the ext root file system have the same label causing a race between what device is symlinked to /dev/live.
To avoid this confusion _ is prepended to the fslabel
imgcreate/fs.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/imgcreate/fs.py b/imgcreate/fs.py
index b8d61db..f5eed39 100644
@@ -395,7 +395,7 @@ class ExtDiskMount(DiskMount):
def __init__(self, disk, mountdir, fstype, blocksize, fslabel, rmmountdir=True):
DiskMount.__init__(self, disk, mountdir, fstype, rmmountdir)
self.blocksize = blocksize
- self.fslabel = fslabel
+ self.fslabel = "_" + fslabel
logging.debug("Formating %s filesystem on %s" % (self.fstype, self.disk.device))
Using the command,
the iso file was extracted and had the following files:
All the files under the folder "tftpboot" were kept at the location
(hd0,0)/test on *64-bit windows *machine.
The menu.lst contents:
title Launch Test Application
kernel (hd0,0)/test/vmlinuz0 root=/F10-x86_64-Live.iso rootflags=loop
rootfstype=auto ro liveimg quiet
On rebooting the system, the following error was displayed:
Error 16: Inconsistent filesystem structure
But on *32-bit windows machine it works *very properly without any
warning or error.
Can anyone let me know how to resolve the FileSystem inconsistency?
Lougher recently posted some patches to lkml to add extended attribute
support to squashfs.
I don't know if that will allow live images to not have to use ext3/4
on top of squashfs or not, but thought some people here might be interested
in knowing that eventually squashfs will be able to support some things it
Yes, it is the Intel 7300 chipset for server. It requires a discrete graphics chip which in this case is an ATI ES1000.
I did check out the link and it does appear to be similar but is not the same. This system I have does not have access to a network connection so I cannot try to remote login with SSH.
Monroe Taylor III
From: Mads Kiilerich [mailto:firstname.lastname@example.org]
Sent: Friday, May 14, 2010 5:30 PM
To: Taylor, Monroe E
Subject: Re: [Fedora-livecd-list] Live USB image does not complete the boot process
I assume you are using Intel chipset?
From the description it sounds a lot like a recent regression tracked
in https://bugzilla.redhat.com/show_bug.cgi?id=571525, but that is not
related to livecd at all ...
It is just a wild guess. Please let the list know if it helped you.
Taylor, Monroe E wrote, On 05/15/2010 01:34 AM:
> I use livecd-creator and a custom kickstart file to create F12 liveUSB
> images. I have created a few images which worked well until a month
> ago when I made some changes to allow root login and set SELinux to
> permissive mode.
> Now when I create an image, it does not work as expected in that the
> Fedora logo screen is not displayed and the Gnome Desktop does not
> launch on one out of 6 computers.
> What happens is when I install the USB and turn on the power the BIOS
> splash screen is displayed. Additionally, the Fedora count down screen
> is also displayed. However, after the count down has completed, the
> screen goes dark with only the cursor displayed. After a few seconds
> the monitor loses synchronization and the message "No input signal" is
> displayed and Gnome Desktop does not launch.
> This started occurring on or around March 25. Prior to that time I did
> not have this issue.
> The liveUSB I previously created still works all 6 computers.
> Also, I download the Fedora live image, burned it to a USB and tried
> it. It also exhibits the issue.
> In trying to diagnose this, I downloaded F12 installation DVD and
> installed it on the one computer which exhibits this issue and
> everything worked fine.
> I would at least like to see whether the computer is getting to the
> startup mode which allows for interactive boot...
> Is there a way to determine which (if any) of the boot scripts are
> executed before the message "No input signal" is displayed?
> Or is there a way that I can bypass or disable the live countdown
> splash screen altogether to see how far it is getting in the boot
> *Monroe** Taylor III
> Test engineering
> Intel Corporation*
> *Americas** Post Sales Support*
> (*480) 552-3041 Fax (480) 552-7565*
> *monroe.e.taylor(a)intel.com* <mailto:email@example.com>
> livecd mailing list
I use livecd-creator and a custom kickstart file to create F12 liveUSB images. I have created a few images which worked well until a month ago when I made some changes to allow root login and set SELinux to permissive mode.
Now when I create an image, it does not work as expected in that the Fedora logo screen is not displayed and the Gnome Desktop does not launch on one out of 6 computers.
What happens is when I install the USB and turn on the power the BIOS splash screen is displayed. Additionally, the Fedora count down screen is also displayed. However, after the count down has completed, the screen goes dark with only the cursor displayed. After a few seconds the monitor loses synchronization and the message "No input signal" is displayed and Gnome Desktop does not launch.
This started occurring on or around March 25. Prior to that time I did not have this issue.
The liveUSB I previously created still works all 6 computers.
Also, I download the Fedora live image, burned it to a USB and tried it. It also exhibits the issue.
In trying to diagnose this, I downloaded F12 installation DVD and installed it on the one computer which exhibits this issue and everything worked fine.
I would at least like to see whether the computer is getting to the startup mode which allows for interactive boot...
Is there a way to determine which (if any) of the boot scripts are executed before the message "No input signal" is displayed?
Or is there a way that I can bypass or disable the live countdown splash screen altogether to see how far it is getting in the boot process?
Monroe Taylor III
Americas Post Sales Support
(480) 552-3041 Fax (480) 552-7565