Error message, what might be wrong ?
by Juan Rodriguez
Hello, I've just tried out to create a custom live cd based on custom
Fedora Core 5 repository, and I'm experiencing the following error messages,
any help will be appreciated, thanks in advance:
[kadischi]: running post installation scripts
[kadischi]: Prelinking..
cannot determine current run level
setsebool: SELinux is disabled.
[kadischi]: Skipping user firewall and services configuration..
[kadischi]: Not going to interactive user accounts configuration..
[kadischi]: estimated fedora-live.iso size is between 293607330.0 and
318074607.5 bytes
[kadischi]: making initrd image
/usr/bin/find: kernel/drivers/cdrom: No such file or directory
/usr/bin/find: kernel/drivers/ide/ide-cd.ko: No such file or directory
18908 blocks
[kadischi]: 2.6.16-1.2133_FC5_patch_29smp initrd made successfully!
[kadischi]: moving files that should be on tmpfs
Traceback (most recent call last):
File "/usr/local/share/kadischi/movefiles.py", line 85, in ?
shutil.copytree (src, dst)
File "/usr/lib/python2.4/shutil.py", line 132, in copytree
raise Error, errors
shutil.Error:
[('/tmp/kadischi.6auIWk/system/livecd/tmpfs/etc/rc.d/rc6.d/K10webmin',
'/tmp/kadischi.6auIWk/system/etc/rc.d/rc6.d/K10webmin',
<exceptions.IOErrorinstance at 0xb7b6358c>),
('/tmp/kadischi.6auIWk/system/livecd/tmpfs/etc/rc.d/rc0.d/K10webmin',
'/tmp/kadischi.6auIWk/system/etc/rc.d/rc0.d/K10webmin',
<exceptions.IOErrorinstance at 0xb7b6384c>),
('/tmp/kadischi.6auIWk/system/livecd/tmpfs/etc/rc.d/rc5.d/S99webmin',
'/tmp/kadischi.6auIWk/system/etc/rc.d/rc5.d/S99webmin',
<exceptions.IOErrorinstance at 0xb7b638ac>),
('/tmp/kadischi.6auIWk/system/livecd/tmpfs/etc/rc.d/rc2.d/S99webmin',
'/tmp/kadischi.6auIWk/system/etc/rc.d/rc2.d/S99webmin',
<exceptions.IOErrorinstance at 0xb7b638ec>),
('/tmp/kadischi.6auIWk/system/livecd/tmpfs/etc/rc.d/rc1.d/K10webmin',
'/tmp/kadischi.6auIWk/system/etc/rc.d/rc1.d/K10webmin',
<exceptions.IOErrorinstance at 0xb7b6354c>),
('/tmp/kadischi.6auIWk/system/livecd/tmpfs/etc/rc.d/rc3.d/S99webmin',
'/tmp/kadischi.6auIWk/system/etc/rc.d/rc3.d/S99webmin',
<exceptions.IOErrorinstance at 0xb7b6386c>)]
Traceback (most recent call last):
File "/usr/local/share/kadischi/kadischi.py", line 501, in ?
rc = main()
File "/usr/local/share/kadischi/kadischi.py", line 206, in main
execute (args)
File "/usr/local/share/kadischi/kadischi.py", line 495, in execute
raise RuntimeError, "Failed to execute", args[0]
TypeError: raise: arg 3 must be a traceback or None
--
JFRH
17 years, 3 months
squashfs module not found
by Martin Steinmann
I ran into trouble with the 2.6.18 kernel on both FC5 and FC6. The
squashfs module is not included. 2.6.15 works fine.
Is there a simple solution to this?
Thanks
--maritn
17 years, 3 months
one-livecd-per-child?
by Jane Dogalt
Here is an idea I had which may be similar to other projects
(lfs,olpc), but interests me as it relates specifically to
fedora-livecds.
Imagine a spin/strain/variant of a fedora livecd, which had the
following properties-
###
a) boots up into firefox displaying a "howto program computers" page.
b) this howto presents a simple step by step procedure for creating a
simple text file with a favorite phrase in it (e.g. 'hello world').
Note
these steps include alt-tab or desktop-switching to-and-fro the howto
web browser page.
c) the howto then describes the steps (ideally one-button simple) to
create and test(virtual boot) and burn a new livecd which only differs
from the current one by displaying a splash screen with monster
letters, displaying the phrase created in the text file from (b), until
the user hits any key, at which point the splash screen disappears, and
things are otherwise normal (i.e. identical to the original livecd
environment)
###
basically what I am getting at is how to go about educating
children(/adults) about programming. Clearly the method I and others
went through (using logo on an atari, etc...) is not going to be the
way of teaching programming in the future.
What I like about the above self-reproducing-but-modified livecd
scenario, is that it is a very idealized complete system. I.e. "the
program" are these bits on the cd. As the programmer, you make a new
cd/program with a slight difference, and now the behavior is different
(big hello world splash screen).
>From there, I would add longer tutorials, starting with a hello world c
program (both as terminal under gnome-terminal, and graphical with some
educationally simple gui library). And then some simple html web page
programming.
I imagine of course that this sort of thing may have already been
discussed WRT OLPC. I've read a bit on LWN and slashdot, but haven't
really looked at it's development. But it seems like they are
targeting that type of education with the whole view source thing. I
wonder, will the firmware on OLPC be 'educationally reflashable' like
so? Maybe it would be ok, if there was an effectively irreplacable
boot option to restore the original firmware.
anything missing or wrong with this picture?
(of course I eventually want a full local copy of the
wiki-university-graduate-computer-engineering-video-lecture-series
included on the live-blu-ray as well...)
-dmc/jdog
____________________________________________________________________________________
Have a burning question?
Go to www.Answers.yahoo.com and get answers from real people who know.
17 years, 3 months
files_to_be_writable doesn't work if I add a new directory
by Juan Rodriguez
Hello,
I'm trying to make a directory called "/usr/local/sb" writable by editing
the
file "movefiles.py", then adding that directory to the
"files_to_be_writable"
array.
Then I lauch "kadischi" and I dont see any error, but when I execute the
iso image (using QEMU), the directory "/usr/local/sb/" is empty and it's not
writable.
Where's the problem?
Thanks.
--
JFRH
17 years, 3 months
Re: [Fedora-livecd-list] Failed to create LiveCD
by Adam M. Dutko
David,
Unfortunately the error:
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run
database recovery
Error installing packages
Error during installation...
fills the entire screen buffer and then some... I don't know of a way, other
than redirecting stdout to capture all of the information. Considering it
takes a long, long time to build on my system it will take a little while to
do it that way. I will capture the input and get back to you soon. Another
interesting thing that happens, the above error occurs at the same time as
an I/O error related to the loopback device. The following isn't an exact
duplicate but it is how it appears in my messages log:
/var/log/messages:Jan 7 21:11:37 laptop kernel: Buffer I/O error on device
loop0, logical block 772842
/var/log/messages:Jan 7 21:11:37 laptop kernel: lost page write due to I/O
error on loop0
I'm on the following... (uname -a)
Linux laptop.dux-linux.org 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006
i686 i686 i386 GNU/Linux
Here is my SELinux conf file:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
I will do the following:
1) Redirect stdout on the next build to capture the error and post my
findings.
2) Turn off SELINUX (set to SELINUX=disabled), then redirect stdout on
a different build to see if I can get the error again, and post my findings.
3) I will provide the complete I/O error in the the same post as 1 and
2.
Also, to reference your suggestion vnpenguin...
[amd59c@laptop python]$ rpm -ql kernel | grep squashfs
/lib/modules/2.6.15-1.2054_FC5/kernel/fs/squashfs
/lib/modules/2.6.15-1.2054_FC5/kernel/fs/squashfs/squashfs.ko
The kernel I am on appears to have squashfs support. :-)
Thank you for your help David, Thomas and vnpenguin.
-Adam
17 years, 3 months
Re: [Fedora-livecd-list] Failed to create LiveCD
by Adam M. Dutko
THIS IS VERY BASIC AND DOES NOT COVER ALL USE CASES. I will attempt to
patch this with better logic tomorrow. I'm trying to determine if it's best
to use 'du' (which can take a while, and is subject to permissions
issues...) or maybe 'sar' (which might not be universally installed...).
Any guidance on other potential tools and/or approaches is appreciated.
#!/usr/bin/python -tt
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; version 2 of the License.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU Library General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
# A very basic (and potential partial patch to livecd-creator)
# by Adam M. Dutko - (dutko.adam(a)gmail.com)
# This code is valid for systems with an actual /var partition.
# In cases where we only have a root (/), /boot and swap on the system
# it will fail. I need to write a patch for that case and append to
# this code. Will try to do this week.
#
import os
import string
# Get a print out of disk space
the_disk = os.popen("df -P")
# We have six columns when using the 'Posix Switch' (-P).
# partition_details[0] = Filesystem
# partition_details[1] = 1024-blocks
# partition_details[2] = Used
# partition_details[3] = Available
# partition_details[4] = Capacity
# partition_details[5] = Mounted on
for the_partitions in the_disk.readlines():
# Cleanup b/c internal pointers are messy for some reason
check_size = ""
check_var = ''
partition_details = the_partitions.split()
check_size = partition_details[3].strip()
check_var = partition_details[5].strip()
if check_var == '/var' and check_size < "3000000":
print "You do not have enough free space to proceed with the
installation. " \
" Please allocate at least 3 gigabytes of space to /var so
the " \
"livecd-creator tool can continue with the build under
/var/tmp/livecd-creator."
exit
-Adam
17 years, 3 months
Re: [Fedora-livecd-list] Failed to create LiveCD
by Adam M. Dutko
"That's the problem. The livecd-creator tools uses a temporary directory in
/var/tmp/livecd-creator/build-<random> so you need at least 3GB free disk
space in /var. One way to get out of this mess is to add more disk space to
your system and symlink /var/tmp/livecd-creator into that."
I'm using LVM, so I'll just resize. Thanks for the fix. I'll try that now
and abandon my other "debug" ideas for now... If it doesn't work, I'll
trudge on with the previous paths.
"(Your partitioning scheme is weird. Personally, I always just have / as a
single file system such as not to run into issues like these. YMMV.)"
I try to separate all of my data from my OS as much as possible. Makes
recovery much easier, and upgrades. Also, if my /home directory gets hosed,
or if my system gets compromised (worm, virus, etc.) then I can simple clean
up and get back up with minimal down-time.
"Oh.. If anyone got a patch for checking there is enough free disk space in
/var/tmp/livecd-creator please come forward. It would be nice to bail out
with a nice error message."
I'm working on a potential one right now.
Also, what does "YMMV" mean???
-Adam
17 years, 3 months
Re: [Fedora-livecd-list] Failed to create LiveCD
by Adam M. Dutko
"It should work on FC3 or later (the pilgrim tools for OLPC that this is
based on is running on RHEL4 which is a downstream of FC3) but I haven't
tested on anything but FC6 and Rawhide."
Correct. It should work. I'm glad I'm potentially indirectly helping
with OLPC with this debug session... :-) (That is of course if I'm not
reaching a hardware limit or overlooking something very simple.) I'm in the
middle of running the tests I mentioned earlier and should have results
before 10 EST -- I think.
"The response from kernel people to a _loop device_ experiencing I/O errors
was: "cute"."
Isn't it?
"They suggested your system is either OOM or you're running of disk space /
disk quota. Is this the case?"
A quick sample...
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 730672 11580 0 67924 336684
-/+ buffers/cache: 326064 416188
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 730920 11332 0 67940 336748
-/+ buffers/cache: 326232 416020
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 730920 11332 0 67940 336812
-/+ buffers/cache: 326168 416084
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 731044 11208 0 67940 336868
-/+ buffers/cache: 326236 416016
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 731044 11208 0 67944 336932
-/+ buffers/cache: 326168 416084
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 730096 12156 0 62700 338788
-/+ buffers/cache: 328608 413644
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$ free
total used free shared buffers cached
Mem: 742252 730220 12032 0 62700 338820
-/+ buffers/cache: 328700 413552
Swap: 1534196 300 1533896
[amd59c@laptop livecd-tools]$
I seem to be hovering around 11-12M free. I have a total of 756MB
physical ram but some is shared with the graphics card. Here is a quick
rundown of diskspace:
[amd59c@laptop livecd-tools]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VG_00-LV_000
961M 185M 727M 21% /
/dev/hda1 99M 9.7M 84M 11% /boot
tmpfs 363M 0 363M 0% /dev/shm
/dev/mapper/VG_00-LV_001
1.9G 555M 1.3G 31% /home
/dev/mapper/VG_00-LV_006
3.8G 210M 3.4G 6% /opt
/dev/mapper/VG_00-LV_007
5.7G 289M 5.1G 6% /sw
/dev/mapper/VG_00-LV_008
3.8G 72M 3.6G 2% /swdata/sys
/dev/mapper/VG_00-LV_009
2.9G 1.6G 1.2G 59% /swpkg/sys
/dev/mapper/VG_00-LV_002
961M 28M 884M 4% /tmp
/dev/mapper/VG_00-LV_004
1.9G 591M 1.3G 33% /var
/dev/mapper/VG_00-LV_003
6.8G 6.0G 460M 94% /usr
/dev/mapper/VG_00-LV_005
3.8G 212M 3.4G 6% /usr/local
/dev/loop0 3.0G 72M 2.9G 3% /var/tmp/livecd-creator/build
-tmpIG3wWz/install_root
/dev 363M 168K 363M 1%
/var/tmp/livecd-creator/build-tmpIG3wWz/install_root/dev
/var/tmp/livecd-creator/build-tmpIG3wWz/yum-cache
1.9G 591M 1.3G 33%
/var/tmp/livecd-creator/build-tmpIG3wWz/install_root/var/cache/yum
Yes /usr is high, but not to worry...I'm not building from there
because the "scratch" is mounted under /var/tmp ... Unless there is
something weird boing on???
I don't have quotas implemented on this system.
"Note that the files backing the loop devices are sparse files so the
creation of them works even when you don't have enough free space. The
reason for sparse files is that we don't have to spend time writing 4GB of
zero's to a file."
Yup. You did a good job on design.
-Adam
17 years, 3 months
