livecd February 2009

livecd@lists.fedoraproject.org

14 participants
15 discussions

F7 general question about livecd-creator and timezones
by Skunk Worx 01 May '09

01 May '09

My ks scripts have the timezone set to PDT (America/Los_Angeles). Installation to a hard drive works as expected. PDT in startup and in shells, etc. Creating a livecd-creator iso with the same tz setting, then booting, shows A/L_A in the /etc/sysconfig/clock file, as expected. However the date is always EDT in the boot messages, shells, etc. During startup I see : (lvm) Press I to enter interactive startup Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007 (udev) I'm not clear on what is happening between lvm and udev in the Linux startup sequence. If someone could give me a hint about what to look for and where to look for it I would appreciate the help. --- John

3 3

Cannot create livecd from local repo
by Joshua C. 09 Apr '09

09 Apr '09

I cannot create a livecd image from a local repo. I have livecd-creator and all the ks files. I've downloaded all necessary files to a local dir (just copied them from previous downloaded cache) and then run createrepo on it. Then I edited the ks file with "repo --name=jdfhjdsfh --baseurl=file:///mnt/path to repodata". When starting livecd-creator it says "retrieving file=///mnt/dsfgsdhfshf ...OK", then it retrieves the repofiles for the other repos and starts downloading all the files again regardless of the fact that I've already downloaded them. How to make livecd-creator see the already downloaded files instead of downloading them twice?

4 5

LiveCD Vesa Mode, menu option like Anaconda install media?
by Warren Togami 27 Feb '09

27 Feb '09

The old answer to "how do I use LiveCD in vesa mode?" was xdriver=vesa. This doesn't seem to be working with Fedora 11 Alpha where X crashes the Radeon 7500 of my Thinkpad T41. Anyhow, I'm wondering if people would be in favor of adding a syslinux menu option to boot into vesa mode similar to how Anaconda install media now has? Warren Togami wtogami(a)redhat.com

2 1

Re: [Fedora-livecd-list] Cannot create livecd from local repo
by Joshua C. 22 Feb '09

22 Feb '09

2009/2/22 Bruno Wolff III <bruno(a)wolff.to>: > On Sat, Feb 21, 2009 at 20:00:35 +0100, >> >> Maybe the problem is in yum, since it sees all the repos, it should >> know that the files in my local repo are the same with the others but >> it choose to use the *offcial* ones and starts the download. why when >> they've been already donwloaded? > > Maybe. I have the entire repos locally and have yum configured to use the > local repos as well. So that might be why things work for me and don't > for you. > Let me clarify something: I've downloaded all the necessry file to my repo1. in the ks file I've specified some other repos (from the internet) so that when creating the live image yum can compare the downloaded with the internet packages and choose the latest. After this I move the cached to repo1. This means on run1 yum should download only the updated packges and make the iso image. on run2 (for instance 2 hours later) it shoud repeat the process and because there should be no new packges (since we've checked for 2 hours) it should use the files from repo1. therefore it's easier for run2 to copy the files from repo1 to the cache and use them instead of going back to the internet repos. this is what i want. I can periodically add different packges to repo1 and keep it up to date (usb pen). i use repo1 as my rawhidea dn when yum see a newer version in it, it uses it. This means that yum hasn't forgotten my repo1. but about the other files in repo1 which are the same to one on the internet: It should know that local-copy is faster than download. So yum see the lastes version and chooses it regardless of the downlaod distance and for the rest of the packges goes to.............. the internet. why? My repo1 should have the highest priority. Is there any way to do this?

1 0

Re: Fedora-livecd-list Digest, Vol 46, Issue 3
by himanshu lad 21 Feb '09

21 Feb '09

Hey sorry for replying so late, the mail went some where , I saw it while sifting through all mails in gmail. I tried following: 1. modifying isolinux.cfg to point to the initrd in the new directory structure on DVD(/fel_x86/boot/).Did not work. 2. tried to modify init file in initrd0.img but not able to find suitable solution Regards Himanshu On Thu, Feb 5, 2009 at 10:30 PM, <fedora-livecd-list-request(a)redhat.com>wrote: > > 1. Re: Working to support multiple images from amedium (Kam) > > > ---------------------------------------------------------------------- > > > --snip > What do people think? Is this worth doing? Other ideas on > implementation? Anyone want to start whipping up any patches? > > Jeremy > > > I feel we could do a better job documenting what is possible with the live > image and its configuration. Having the procedures for implementing a > multi-image flash drive available is better than changing how the live image > works. > > For example, just send me your process for a multi-image Fedora Live flash > drive and I will find a place for it in the wiki and write the beats for it > for F11. > > -- > Kam > http://kamsalisbury.com > GPG key: FAF1751E > > > > ------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > > End of Fedora-livecd-list Digest, Vol 46, Issue 3 > ************************************************* >

1 0

Changes to 'refs/tags/livecd-tools-021'
by Jeremy Katz 16 Feb '09

16 Feb '09

Changes since livecd-tools-020-23: --- 0 files changed ---

1 0

Creating live cd from complex software development setup (Eclipse)
by sarikan 13 Feb '09

13 Feb '09

Dear members, I have a quite complex setup in my computer that covers about three large scale Java applications. They are all open source apps, with various application servers and postgresql databases. There is even an openldap installation, and there are more than 20 Eclipse Java projects The whole setup takes a horrible amount of time, but it is a setup that I must share with others. I've given a try to a tool for an ubuntu setup, that produced acceptable results, but my configuration is quite complex. Especially Eclipse projects take hours to configure, with inter-project dependencies, build paths, jars, custom libraries etc. I am afraid, this is not a common case, where I can simply select the pre-installed packages in my installation and get a nice live distribution as a result. Would Fedora live-cd options let me create a highly specialized distrubution? These are the things I have in my mind: A shortcut to a pre-configured Eclipse environment on desktop, which will start with a workspace with projects in it, and compile and execute it etc.. Postgresql with databases which include populated data, security settings etc. Ldap server starting automaticaly, with settings etc. Custom background images, icons etc.. (assuming I can do the previous things :) ... I'm sure you can see the picture here. Would you please provide pointers to documents that outline the important factors to obtain this result? If a live cd that can't work as I want it to when it is in live mode, then I'd still be happy if it could install the final setup to another computer. Your help would be appreciated a lot. Kind regards Seref -- View this message in context: http://www.nabble.com/Creating-live-cd-from-complex-software-development-se… Sent from the Fedora Livecd List mailing list archive at Nabble.com.

2 3

create live cd
by shivam tiwari 11 Feb '09

11 Feb '09

hey guys, I just copied my fedora 10 dvd to my computer, and created its iso image but its not booting because i just copied it insted of burning. please tell me how i can make it live

3 3

docs/livecd-creator.pod docs/livecd-iso-to-disk.pod
by Jeremy Katz 10 Feb '09

10 Feb '09

docs/livecd-creator.pod | 22 +++++++++++----------- docs/livecd-iso-to-disk.pod | 20 +++++++++++--------- 2 files changed, 22 insertions(+), 20 deletions(-) New commits: commit 0e54ced6f35c8dd8b79da7719581ce96975384c1 Author: Chris Curran <ccurran(a)redhat.com> Date: Tue Feb 10 13:56:50 2009 -0500 Update man pages (#484627) diff --git a/docs/livecd-creator.pod b/docs/livecd-creator.pod index dcaddc7..b275e65 100644 --- a/docs/livecd-creator.pod +++ b/docs/livecd-creator.pod @@ -2,7 +2,7 @@ =head1 NAME -livecd-creator, creates live cd or dvd images. +livecd-creator - creates live CD or DVD images. =head1 SYNOPSIS @@ -10,7 +10,7 @@ B<livecd-creator> [OPTIONS] =head1 DESCRIPTION -B<livecd-creator> creates live cd or dvd images from kickstart files. Kickstart files contain the information about packages and configurations that are built into the image. +B<livecd-creator> creates live CD or DVD images(ISO images) from kickstart files. Kickstart files contain information about packages and configuration settings which are used to build the image. =head1 OPTIONS @@ -18,7 +18,7 @@ B<livecd-creator> creates live cd or dvd images from kickstart files. Kickstart =item -h, --help -Shows a help message and exits. +Shows the help message and exits. =back @@ -30,7 +30,7 @@ These options define the created image. =item -c KSCFG, --config=KSCFG -Path to kickstart config file +Path to kickstart configuration file. =item -b BASE_ON, --base-on=BASE_ON @@ -38,23 +38,23 @@ Add packages to an existing live CD iso9660 image. =item -f FS_LABEL, --fslabel=FS_LABEL -File system label (default based on config name) +Defines the file system label. The default is based on the configuration name. =back =head1 SYSTEM DIRECTORY OPTIONS -These options define directories used on your system for creating the live image +These options define directories used on your system for creating the live image. =over 4 =item -t TMPDIR, --tmpdir=TMPDIR -Temporary directory to use (default: /var/tmp) +defines the temporary directory to use. The default directory is /var/tmp. =item --cache=CACHEDIR -Cache directory to use (default: private cache) +Defines the cache directory to use (default: private cache). =back @@ -77,14 +77,14 @@ David Zeuthen, Jeremy Katz, Douglas McClendon and a team of many other contribut =head1 BUGS -Report bugs to the mailing list C<http://www.redhat.com/mailman/listinfo/fedora-livecd-list> or directly to BugZilla C<http://bugzilla.redhat.com/bugzilla/> against the C<Fedora> product, and the C<livecd-tools> component. +Report bugs to the mailing list C<http://www.redhat.com/mailman/listinfo/fedora-livecd-list> or directly to Bugzilla C<http://bugzilla.redhat.com/bugzilla/> against the C<Fedora> product, and the C<livecd-tools> component. =head1 COPYRIGHT -Copyright (C) Fedora Project 2008, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License C<http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. +Copyright (C) Fedora Project 2008,2009, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License C<http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. =head1 SEE ALSO C<livecd-iso-to-disk(1)>, project website C<http://fedoraproject.org/wiki/FedoraLiveCD> -=cut \ No newline at end of file +=cut diff --git a/docs/livecd-iso-to-disk.pod b/docs/livecd-iso-to-disk.pod index ffe9add..7449c17 100644 --- a/docs/livecd-iso-to-disk.pod +++ b/docs/livecd-iso-to-disk.pod @@ -2,15 +2,17 @@ =head1 NAME -livecd-iso-to-disk, install livecd-creator images in usb stick +livecd-iso-to-disk - installs bootable CD images on a USB storage devices. =head1 SYNOPSIS -B<livecd-iso-to-disk> [--reset-mbr] [--noverify] [--overlay-size-mb <size>] <isopath> <usbstick device> +B<livecd-iso-to-disk> [--reset-mbr] [--noverify] [--overlay-size-mb <size>] <path-to-iso> <usb storage device> =head1 DESCRIPTION -B<livecd-iso-to-disk> converts a live cd or dvd image into a bootable USB stick. This is not a destructive process; any data you currently have on your USB stick will be preserved. +B<livecd-iso-to-disk> installs a live CD or DVD image(ISO image) onto a USB storage device. The USB storage device can then boot the installed operating system on systems which support booting via USB. B<livecd-iso-to-disk> requires an ISO image and a USB storage device. ISO images can be created with B<livecd-creator>. + +B<livecd-iso-to-disk> is not a destructive process; any data you currently have on your USB stick is preserved. =head1 OPTIONS @@ -18,29 +20,29 @@ B<livecd-iso-to-disk> converts a live cd or dvd image into a bootable USB stick. =item --reset-mbr -Resets Master Boot Record of usb stick by copying syslinux's mbr.bin. +Sets the Master Boot Record(MBR) of the USB storage device to the mbr.bin file from the image's syslinux directory. =item --noverify -Disables image validation before installing it. +Disables the image validation process which occurs before the image is installed. When this option is enabled the image is not verified before installation on the USB storage device. =item --overlay-size-mb -Overlay's size in megabytes. Note that you'll need to have space on your USB stick for the live image plus your overlay plus any other data you want on the stick. +This option sets the overlay size in megabytes. The overlay is additional storage available to the live operating system if the operating system supports it. The USB storage device must have enough free space for the image and the overlay. =back =head1 CONTRIBUTORS -David Zeuthen, Jeremy Katz, Douglas McClendon and a team of many other contributors. See the AUTHORS file in the source distribution for the complete list of credits. +David Zeuthen, Jeremy Katz, Douglas McClendon, Chris Curran and other contributors. See the AUTHORS file in the source distribution for the complete list of credits. =head1 BUGS -Report bugs to the mailing list C<http://www.redhat.com/mailman/listinfo/fedora-livecd-list> or directly to BugZilla C<http://bugzilla.redhat.com/bugzilla/> against the C<Fedora> product, and the C<lived-tools> component. +Report bugs to the mailing list C<http://www.redhat.com/mailman/listinfo/fedora-livecd-list> or directly to Bugzilla C<http://bugzilla.redhat.com/bugzilla/> against the C<Fedora> product, and the C<lived-tools> component. =head1 COPYRIGHT -Copyright (C) Fedora Project 2008, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License C<http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. +Copyright (C) Fedora Project 2008,2009, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License C<http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law. =head1 SEE ALSO

1 0

3 commits - imgcreate/errors.py tools/livecd-creator tools/livecd-iso-to-disk.sh
by Jeremy Katz 09 Feb '09

09 Feb '09

imgcreate/errors.py | 23 +++++++++++++++++++++++ tools/livecd-creator | 2 +- tools/livecd-iso-to-disk.sh | 14 ++++++++------ 3 files changed, 32 insertions(+), 7 deletions(-) New commits: commit e182dda3d58a25a08d5057faf5d140f08806ed7e Author: Felix Schwarz <felix.schwarz(a)oss.schwarz.eu> Date: Sat Feb 7 12:01:30 2009 +0100 Patch for unicode error messages when I tried to build a custom live cd I noticed some problems in the error reporting when there were unicode error messages (e.g. some dependency was missing). Example: ... > anaconda-11.4.1.63-1.i386 von updates hat Abhängigkeitsauflöse-Probleme > --> Fehlende Abhängigkeit: booty wird benötigt von Paket anaconda-11.4.1.63-1.i386 (updates) > Traceback (most recent call last): > File "./tools/livecd-creator", line 140, in <module> > sys.exit(main()) > File "./tools/livecd-creator", line 132, in main > logging.error("Error creating Live CD : %s" % e) > UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 42: ordinal not in range(128) My patch ensures that unicode error messages can be printed correctly every time. To get 100% unicode support, one should go through all log calls and ensure that all strings are unicode so that localized error messages are always shown correctly. With my patch, there should be no unicode exceptions anymore, even when the error message may be printed as 'Fehlende Abh\xe4ngigkeit' instead of 'Fehlende Abhängigkeit' (notice the '\xe4' in the first string). diff --git a/imgcreate/errors.py b/imgcreate/errors.py index ba08563..a29b841 100644 --- a/imgcreate/errors.py +++ b/imgcreate/errors.py @@ -21,6 +21,29 @@ class CreatorError(Exception): def __init__(self, msg): Exception.__init__(self, msg) + # Some error messages may contain unicode strings (especially if your system + # locale is different from 'C', e.g. 'de_DE'). Python's exception class does + # not handle this appropriately (at least until 2.5) because str(Exception) + # returns just self.message without ensuring that all characters can be + # represented using ASCII. So we try to return a str and fall back to repr + # if this does not work. + # + # Please use unicode for your error logging strings so that we can really + # print nice error messages, e.g.: + # log.error(u"Internal error: " % e) + # instead of + # log.error("Internal error: " % e) + # With our custom __str__ and __unicode__ methods both will work but the + # first log call print a more readable error message. + def __str__(self): + try: + return str(self.message) + except UnicodeEncodeError: + return repr(self.message) + + def __unicode__(self): + return unicode(self.message) + class KickstartError(CreatorError): pass class MountError(CreatorError): diff --git a/tools/livecd-creator b/tools/livecd-creator index 1aab882..39f7478 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -129,7 +129,7 @@ def main(): creator.unmount() creator.package() except imgcreate.CreatorError, e: - logging.error("Error creating Live CD : %s" % e) + logging.error(u"Error creating Live CD : %s" % e) return 1 finally: creator.cleanup() commit 75201f2180bb2e35cc439f9219aaf333d9577daa Author: Jeremy Katz <katzj(a)redhat.com> Date: Tue Feb 3 14:58:04 2009 -0500 Move syslinux path to be under LiveOS to prep for multiple livedirs diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index c310936..7d5ba1d 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -246,7 +246,7 @@ checkSyslinuxVersion() { if ! syslinux 2>&1 | grep -qe -d; then SYSLINUXPATH="" else - SYSLINUXPATH="syslinux" + SYSLINUXPATH="LiveOS/syslinux" fi } commit 9188aba5d6d9a71933c910dc076e5a108bf2f57d Author: Stewart Adam <maillist(a)diffingo.com> Date: Mon Jan 26 23:44:04 2009 -0500 Fix $BOOTCONFIG being overwritten There's also a small bug that I forgot to account for in the last patch - $BOOTCONFIG is overwritten if --mactel is set, so the syslinux.cfg file is left in an inconsistent state with root=CDLABEL=<...> and rootfstype=iso9660. The attached patch fixes this problem by using $BOOTCONFIG and $BOOTCONFIG_EFI. diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 85dba7e..c310936 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -509,6 +509,8 @@ fi cp $CDMNT/isolinux/* $USBMNT/$SYSLINUXPATH BOOTCONFIG=$USBMNT/$SYSLINUXPATH/isolinux.cfg +# Set this to nothing so sed doesn't care +BOOTCONFIG_EFI= if [ -n "$mactel" ];then if [ -d $CDMNT/EFI/boot ]; then cp $CDMNT/EFI/boot/* $USBMNT/EFI/boot @@ -541,14 +543,14 @@ EOF fi # this is a little ugly, but it gets the "interesting" named config file - BOOTCONFIG=$USBMNT/EFI/boot/boot?*.conf + BOOTCONFIG_EFI=$USBMNT/EFI/boot/boot?*.conf rm -f $USBMNT/EFI/boot/grub.conf fi echo "Updating boot config file" # adjust label and fstype -sed -i -e "s/CDLABEL=[^ ]*/$USBLABEL/" -e "s/rootfstype=[^ ]*/rootfstype=$USBFS/" $BOOTCONFIG -if [ -n "$kernelargs" ]; then sed -i -e "s/liveimg/liveimg ${kernelargs}/" $BOOTCONFIG ; fi +sed -i -e "s/CDLABEL=[^ ]*/$USBLABEL/" -e "s/rootfstype=[^ ]*/rootfstype=$USBFS/" $BOOTCONFIG $BOOTCONFIG_EFI +if [ -n "$kernelargs" ]; then sed -i -e "s/liveimg/liveimg ${kernelargs}/" $BOOTCONFIG $BOOTCONFIG_EFI ; fi if [ "$overlaysizemb" -gt 0 ]; then echo "Initializing persistent overlay file" @@ -559,8 +561,8 @@ if [ "$overlaysizemb" -gt 0 ]; then else dd if=/dev/null of=$USBMNT/LiveOS/$OVERFILE count=1 bs=1M seek=$overlaysizemb fi - sed -i -e "s/liveimg/liveimg overlay=${USBLABEL}/" $BOOTCONFIG - sed -i -e "s/\ ro\ /\ rw\ /" $BOOTCONFIG + sed -i -e "s/liveimg/liveimg overlay=${USBLABEL}/" $BOOTCONFIG $BOOTCONFIG_EFI + sed -i -e "s/\ ro\ /\ rw\ /" $BOOTCONFIG $BOOTCONFIG_EFI fi if [ "$swapsizemb" -gt 0 ]; then

1 0

Patch for unicode error messages
by Felix Schwarz 09 Feb '09

09 Feb '09

Hi, when I tried to build a custom live cd I noticed some problems in the error reporting when there were unicode error messages (e.g. some dependency was missing). Example: ... > anaconda-11.4.1.63-1.i386 von updates hat Abhängigkeitsauflöse-Probleme > --> Fehlende Abhängigkeit: booty wird benötigt von Paket anaconda-11.4.1.63-1.i386 (updates) > Traceback (most recent call last): > File "./tools/livecd-creator", line 140, in <module> > sys.exit(main()) > File "./tools/livecd-creator", line 132, in main > logging.error("Error creating Live CD : %s" % e) > UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 42: ordinal not in range(128) My patch ensures that unicode error messages can be printed correctly every time. To get 100% unicode support, one should go through all log calls and ensure that all strings are unicode so that localized error messages are always shown correctly. With my patch, there should be no unicode exceptions anymore, even when the error message may be printed as 'Fehlende Abh\xe4ngigkeit' instead of 'Fehlende Abhängigkeit' (notice the '\xe4' in the first string). fs diff --git a/imgcreate/errors.py b/imgcreate/errors.py index ba08563..071d4b8 100644 --- a/imgcreate/errors.py +++ b/imgcreate/errors.py @@ -20,6 +20,29 @@ class CreatorError(Exception): """An exception base class for all imgcreate errors.""" def __init__(self, msg): Exception.__init__(self, msg) + + # Some error messages may contain unicode strings (especially if your system + # locale is different from 'C', e.g. 'de_DE'). Python's exception class does + # not handle this appropriately (at least until 2.5) because str(Exception) + # returns just self.message without ensuring that all characters can be + # represented using ASCII. So we try to return a str and fall back to repr + # if this does not work. + # + # Please use unicode for your error logging strings so that we can really + # print nice error messages, e.g.: + # log.error(u"Internal error: " % e) + # instead of + # log.error("Internal error: " % e) + # With our custom __str__ and __unicode__ methods both will work but the + # first log call print a more readable error message. + def __str__(self): + try: + return str(self.message) + except UnicodeEncodeError: + return repr(self.message) + + def __unicode__(self): + return unicode(self.message) class KickstartError(CreatorError): pass diff --git a/tools/livecd-creator b/tools/livecd-creator index 1aab882..39f7478 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -129,7 +129,7 @@ def main(): creator.unmount() creator.package() except imgcreate.CreatorError, e: - logging.error("Error creating Live CD : %s" % e) + logging.error(u"Error creating Live CD : %s" % e) return 1 finally: creator.cleanup()

2 1

Re: Fedora-livecd-list Digest, Vol 46, Issue 3
by himanshu lad 06 Feb '09

06 Feb '09

guys I need to carry both 32 and 64 bit versions of Fedora electronics lab for my friends and faculty. It would be better to have both in one dvd for ease.Besides I it would help in reducing e-waste in long run i.e. less dvds to burn lesser the e-waste. Thanks OPENFREAK

1 0

livecd-create Bootable Fedora LiveCD Failed in Fedora 10
by Dino Lopez 05 Feb '09

05 Feb '09

I try to create a Bootable Fedora LiveCD but it Failed in Fedora 10 Fedora_Minimal.ks #################### lang en_US.UTF-8 keyboard us timezone US/Central auth --useshadow --enablemd5 selinux --permissive firewall --disabled part / --size 1024 repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/ mirrorlist?repo=rawhide&arch=$basearch %packages @core bash kernel passwd policycoreutils chkconfig authconfig rootfiles /usr/sbin/lokkit %end #################### livecd-creator --config=./Fedora_Minimal.ks --fslabel=Your_Distro if you don't add the line: /usr/sbin/lokkit will stop with error !!!, once you add the line wait until the process finish... After the iso image gets generated the following message appear : Error on boot: mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Bug in initramfs /init detected. Dropping to a shell. Good luck! bash: no job control in this shell bash-4.0# I really like to see a way to create your own custom Fedora Minimal LIveCD or USB. Maybe add the option to boot in about 5 seconds like reported at: http://lwn.net/Articles/299483/ And why not to handle the awesome speed & compression from: http://www.slax.org/ Seems like Build aufs kernel module and squashfs kernel module (optionally patched to support LZMA) is the way to go. If somebody have some ideas will be really appreciated... Dinooz

1 0

Re: [Fedora-livecd-list] Working to support multiple images from amedium
by Kam Salisbury 05 Feb '09

05 Feb '09

--snip What do people think? Is this worth doing? Other ideas on implementation? Anyone want to start whipping up any patches? Jeremy I feel we could do a better job documenting what is possible with the live image and its configuration. Having the procedures for implementing a multi-image flash drive available is better than changing how the live image works. For example, just send me your process for a multi-image Fedora Live flash drive and I will find a place for it in the wiki and write the beats for it for F11. -- Kam http://kamsalisbury.com GPG key: FAF1751E

1 0

Working to support multiple images from a medium
by Jeremy Katz 03 Feb '09

03 Feb '09

It keeps coming up that people would like to support multiple live images running off the same USB stick/hard drive/$arbitrary medium and so it's probably worth considering some of the ways that it could possibly be supported. Also, for the personal reason, it would make it easier for me to effectively use my netbook with the super-slow SSD if I just put a new rawhide live image on it regularly and keep my homedir on the (faster) SD card :-) Breaking it down into components, I think there are a few things which we have to worry about 0) Where to put things on the disk. The more I think about it, the more I think that having "everything" for one image (including the bootloader bits) will be easiest. The part we had talked about last about using the iso label for namespacing seems to make reasonable sense 1) Boot loader config There are a couple of possibilities here... the simplest would just be that we edit the syslinux.cfg and append more entries. A little bit more complicated would be to just have a simple "top-level" syslinux.cfg which uses CONFIG directives to load the additional config files. Third would be a com32 module to iterate and set up the menu items automatically. I lean towards the second, at least for at first. 2) How to know the new directory There are multiple places scattered that have hard-coded looking for LiveOS. There's the initrd, there's the livesys initscript and there's livecd-iso-to-disk/liveusb-creator. While we could add a kernel command line option[1] and go and change each of these to set it/respect it, it feels like maybe the less general solution. Maybe it's just that we should always have livelabel= available so that we can use it other places ? I don't know. Open to other thoughts and suggestions. What do people think? Is this worth doing? Other ideas on implementation? Anyone want to start whipping up any patches? Jeremy [1] Till Maas sent a patch along these lines back in November and I've kept meaning to get back to it. So consider this doing so :)

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

livecd February 2009