Creation of livecd on fc6 fails - Help!!!
by Konstantin N.Kozlov
I tried to create the base live cd with livecd-creator.
I am running Fedora 6 on host machine (Dell, 2xXeon 2.4 GHz). The
repositories are on my hard drive. SELinux is disabled on host and I
want it to be disabled on LiveCD.
I've got the following errors:
rpmdb: fsync I/O Error
error: cannot open Packages index using db3 - I/O Error (5)
error: cannot open Packages database
in /var/tmp/livecd-creator/build-tmpJugyMn/install_root/var/lib/rpm
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in ?
yummain.main(sys.argv[1:])
File "/usr/share/yum-cli/yummain.py", line 82, in main
base.getOptionsConfig(args)
File "/usr/share/yum-cli/cli.py", line 205, in getOptionsConfig
errorlevel=opts.errorlevel)
File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 125, in
doConfigSetup
self.conf = config.readMainConfig(startupconf)
File "/usr/lib/python2.4/site-packages/yum/config.py", line 598, in
readMainConfig
yumvars['releasever'] = _getsysver(startupconf.installroot,
startupconf.distroverpkg)
File "/usr/lib/python2.4/site-packages/yum/config.py", line 661, in
_getsysver
idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed
Message from syslogd@freya at Tue Mar 27 13:16:46 2007 ...
freya kernel: journal commit I/O error
Error installing packages
Error during installation...
What to do? Help me please!
Best regards
--
Konstantin N.Kozlov
Research Fellow at
Department of Computational Biology,
Center for Advanced Studies,
St.Petersburg State Polytechnical University
195251, St.Petersburg,
Polytechnicheskaya ul. 29,
Russia
17 years
Groundwork for booting from USB sticks
by Jeremy Katz
These patches provide the infrastructure to support nicely booting off
of a live USB stick. The pieces are to include vfat modules on the
disk and to allow having the live image under a live subdirectory.
Jeremy
17 years
Current desktop livecd kickstart config
by Jeremy Katz
Sorry for the lag in getting around to sending this, but here's the
config I'm using right now for the test3 live CD.
Things to note:
* Just pulls in the init script by cat'ing it in the %post. This is a
tad messy, but functional for now. Longer term, this should probably be
in a package that gets installed for live CD images
* Don't do auto-login. With the facebrowser stuff and gdm work that
davidz has done, we want to let people choose a language, etc there
* Right now is doing rm -rf /usr/share/doc/* to try to get to fitting.
Even with that, we're still way too close for my level of comfort.
I think that committing as configs/livecd-fedora-desktop.ks looks
reasonable. Sound good to you David?
Jeremy
17 years
liveinst conflicts with anaconda
by Rahul Sundaram
Hi
Doing a harddisk installation of the Fedora 7 Test 2 live CD ended up
retaining the liveinst package which also shows up a menu entry "install
to harddisk" even after the hard disk installation is complete. Running
that exits with a not a live cd error however. On a installed system
this menu entry should be hidden somehow.
The latest update of this system today results in
Transaction Check Error:
file /usr/sbin/liveinst from install of anaconda-11.2.0.40-1
conflicts with file from package liveinst-0.01-1
file /usr/share/applications/liveinst.desktop from install of
anaconda-11.2.0.40-1 conflicts from package liveinst-0.01-1
Rahul
17 years, 1 month
livecd-creator (git) and selinux
by Sebastian Vahl
Hi.
Just a small question: Should selinux be enabled on the host system or doesn't
it matter? I'm asking because I have problems with selinux since I use the
git version. On my rawhide installation selinux is normally disabled and I
also don't have much experience with selinux itself or interpreting the
errors. The version of livecd-creator from test2 works fine with this, but
now I'm getting errors like this:
http://img462.imageshack.us/my.php?image=rootjj4.png
Kickstart file is attached. With this one I only can login in runlevel 3 when
I boot with selinux=0 or enforcing=0 (with this one I shot the screenshot).
Other versions with X will boot into X. But some tools (like system-config-*)
also only work with selinux disabled.
If selinux must be enabled I'll setup a clean installation to produce my isos.
But before I do this I just want to ask this question. :)
Sebastian
17 years, 1 month
F7 livecd login screen is confusing.
by Will Woods
Hi, folks.
So the current F7 LiveCD gives us the gdm greeter, which lets you choose
a language and options and such. So that's nice. Unfortunately it's not
at all clear how you actually log in.
There's four options on the screen - Language, Options, Shut Down, and
Username. The user is not informed of what username to use.
*I* know that I can just click "Fedora live CD" in the face browser to
log in, but it's not at all obvious.
Could we do something to make this clearer? Changing the full name for
the user to "Fedora LiveCD - Click to start" would be a really easy fix.
Thanks,
-w
17 years, 1 month
[PATCH] Fix SELinux errors with livecd udev rule
by Jeremy Katz
udev has SELinux policy now and rules must be labeled appropriately. Since
the initramfs runs before policy is loaded, we can't label files we create
so we should instead append to an existing file
---
creator/mayflower | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/creator/mayflower b/creator/mayflower
index b5062bf..0ef6a09 100755
--- a/creator/mayflower
+++ b/creator/mayflower
@@ -556,12 +556,12 @@ do_livecd_from_loop121() {
# create rule so udev creates /dev/livecd symlink on real rootfs
if [ "\$livecd_ram" == "1" ] ; then
- echo "KERNEL==\"loop118\", SYMLINK+=\"livecd\"" > /sysroot/etc/udev/rules.d/00-livecd.rules
+ echo "KERNEL==\"loop118\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules
else
- echo "KERNEL==\"hd[a-z]\", BUS==\"ide\", SYSFS{removable}==\"1\", ATTRS{media}==\"cdrom\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" > /sysroot/etc/udev/rules.d/00-livecd.rules
- echo "KERNEL==\"sr[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/00-livecd.rules
- echo "KERNEL==\"scd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/00-livecd.rules
- echo "KERNEL==\"pcd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/00-livecd.rules
+ echo "KERNEL==\"hd[a-z]\", BUS==\"ide\", SYSFS{removable}==\"1\", ATTRS{media}==\"cdrom\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules
+ echo "KERNEL==\"sr[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules
+ echo "KERNEL==\"scd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules
+ echo "KERNEL==\"pcd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules
fi
mount -n -o ro,remount /sysroot
--
1.5.0.2
17 years, 1 month
[PATCH] RFC: Use nash for root switch instead of run-init
by Jeremy Katz
The attached patch switches so that we use nash instead of the run-init
from the livecd-creator for switching to the real system root. There's
up and downsides to this, but I think that overall it's the right thing
to do.
Pros:
* Not using binaries from the "host" system when creating the live CD
image. Makes building x86 and x86_64 live CDs on the same box far
easier
* Makes creator bits all noarch
* Uses infrastructure that we use on "real" systems for the live CD
* Moves more in the direction so that hopefully we can use nash for all
of the initramfs bits in the live CD eventually
Cons:
* Might end up being a little bigger
* nash is bigger and thus debugging it instead of run-init requires a
little more poking/knowledge.
Other thoughts?
Jeremy
17 years, 1 month
