livecd January 2008

livecd@lists.fedoraproject.org

32 participants
34 discussions

Re: [Fedora-livecd-list] persistence testing howto
by Mike Dickson 07 Jan '08

07 Jan '08

Guys, I got a LiveCD + Persistence usb drive running from your scripts, but got I/O errors if I tried to do a yum update. Before that I was able to vi test.txt and put some text in and it survived a reboot. What can I do to address the i/o errors? MikeD "Messsage from syslogd@localhost at kernel: journal commit i/o error" On Wed, 2008-01-02 at 04:07 -0800, Mike Dickson wrote: > I have some time now. I am attempting this tonight and tomorrow. I > will let you know. > > MikeD >

2 8

[Fedora-livecd-list]
by Thiago Braga Santana 03 Jan '08

03 Jan '08

Hello List. I customizing the livecd of Fedora 6 you developed. I urgently need to understand two parameters of the kernel. "LIVEINST" and "LIVEIMG", must fully understand the usefulness of each. Recently I discovered a problem with the livecd, a problem which affects the software in the package lvm2, when do the livecd with bootparam "liveimg." This is the error: " /sbin/lvm.static Parse error at byte 996 (line 43) the expected value. Failed to load config file /etc/lvm/lvm.conf " The detail is key: this problem only occurs when livecd run on computers with hard drive-type SATA2. However, the problem does not occur if I use the bootparam "liveist" instead of "liveimg." I need you to help me understand the concept of these two bootparam because I believe I can help you fix this in the livecd CentOS. Please do me respond as soon as possible. Thank you. Thiago Santana

2 1

Trying to build from GIT
by Jeroen van Meeuwen 02 Jan '08

02 Jan '08

Hi, I'm building livecd-tools from the latest code in GIT, but rpmlint complaints like there's no tomorrow: [jmeeuwen@elwood devel]$ rpmlint /var/lib/mock/fedora-8-x86_64/result/livecd-tools-013-1.fc8.x86_64.rpm livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/kickstart.py 0644 livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/errors.py 0644 livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/creator.py 0644 livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/fs.py 0644 livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/yuminst.py 0644 livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/live.py 0644 livecd-tools.x86_64: E: non-executable-script /usr/lib/python2.5/site-packages/imgcreate/__init__.py 0644 livecd-tools.x86_64: W: invalid-license GPL livecd-tools.x86_64: E: no-binary livecd-tools.x86_64: E: only-non-binary-in-usr-lib Could these be fixed at some point in time please? Thanks, in advance. Kind regards, Jeroen van Meeuwen -kanarip

3 2

f8 gripe#2: why did f8's pm-hibernate regress?
by Douglas McClendon 01 Jan '08

01 Jan '08

Can someone tell me if there is anything I can do to de-regress f8's pm-hibernate? What I mean is that it seems like in f7, pm-hibernate saved the kernel buffer/filesystem caches as well as the minimal needed stuff. Now in f8, every time I resume, system performance is crap because everything needs to be read piecemeal from disk into the caches again. My analysis is pure speculation based on my understanding of how you can tune that behaviour with suspend2(tux-on-ice). But it is very noticable and very annoying and very clearly a f7->f8 change. -dmc

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

livecd January 2008