Request
by Geraldo Barros
I wonder if RedHat, you can help me by sending Fedora CDs and
promotional material (200 CDS, Schedules 10, 10 books, 10 Shirts, 10
Hats, Posters 3, 100 pens, 50 Cartons of Adhesives, Page 100 markers,
100 pamphlets, 10 T, 5 Bags and other materials available.), these
materials will be used to help criração an event that has the
objective to promote Fedora.
Atenciosamente,
Geraldo Barros
E-mail: geraldoweb(a)gmail.com
Contato: +55 (19) 9508-7962
Esta mensagem e seus anexos se dirigem exclusivamente ao seu
destinatário, pode conter informação privilegiada ou confidencial é
para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
senhoria o destinatario indicado, fica notificado de que a leitura,
utilização, divulgacao e/ou copia sem autorização pode estar proibida
em virtude da legislação vigente. Se recebeu esta mensagem por erro,
rogamos-lhe que nos o comunique imediatamente por esta mesma via e
proceda a sua destruição. Esta mensagem isenta a Geraldo Barros
(pessoa física) de qualquer responsabilidade sobre o mau uso e
incorreta distribuição das informações contidas nas referidas
mensagens.
This message and its attachments are addressed solely to the
addressee, may contain privileged or confidential information is for
the exclusive use of the target person or entity. If your lordship is
not the addressee indicated hereby notified that reading, use,
disclosure and / or copying without authorization may be prohibited
under the legislation. If you received this message in error, we
beseech you to immediately report the same path and proceed to its
destruction. This message exempts Geraldo Barros (individual) of any
responsibility for the misuse and improper distribution of the
information contained in those messages.
11 years, 8 months
too many packages
by James Heather
Now this really does need some sort of explanation!
See the progress count in the bottom right.
Anyone seen this before?
James
11 years, 9 months
Weird livecd failure
by James Heather
Can anyone explain this? I can provide more details if relevant, but
it's running livecd-creator on a kickstart file that's been working up
to now. There doesn't seem to be enough info at the crucial point where
the error occurs.
This is a fully up-to-date F17 machine.
James
---------------
[root@zoe james]# nice build-live-cd
Using title 'Jah Live' and product 'Jah Live'
/usr/lib/python2.7/site-packages/pykickstart/commands/partition.py:251:
UserWarning: A partition with the mountpoint / has already been defined.
warnings.warn(_("A partition with the mountpoint %s has already been
defined.") % pd.mountpoint)
Extending sparse file /var/tmp/imgcreate-KXcnKG/tmp-tC8OlB/ext3fs.img to
12884901888
Losetup add /dev/loop0 mapping
to /var/tmp/imgcreate-KXcnKG/tmp-tC8OlB/ext3fs.img
Formating ext4 filesystem on /dev/loop0
mke2fs 1.42 (29-Nov-2011)
Discarding device blocks: done
Filesystem label=_JAH-live-F17-x8
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
786432 inodes, 3145728 blocks
31457 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3221225472
96 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Tuning filesystem on /dev/loop0
tune2fs 1.42 (29-Nov-2011)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Extending sparse file /var/tmp/imgcreate-KXcnKG/tmp-tC8OlB/ext3fs.img to
12884901888
Mounting /dev/loop0 at /var/tmp/imgcreate-KXcnKG/install_root
Skipping (/sys/fs/selinux,/sys/fs/selinux) because source doesn't exist.
Retrieving
http://linuxdownload.adobe.com/linux/i386/repodata/repomd.xml ...OK
Retrieving
http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml ...OK
Retrieving
http://linux.dell.com/repo/firmware/cross-distro/repodata/repomd.xml ...OK
umount: /var/tmp/imgcreate-KXcnKG/install_root/var/cache/yum: target is
busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
Unable to unmount /var/tmp/imgcreate-KXcnKG/install_root//var/cache/yum
normally, using lazy unmount
lazy umount succeeded
on /var/tmp/imgcreate-KXcnKG/install_root//var/cache/yum
lazy umount succeeded
on /var/tmp/imgcreate-KXcnKG/install_root//var/cache/yum
Unmounting directory /var/tmp/imgcreate-KXcnKG/install_root
Losetup remove /dev/loop0
Traceback (most recent call last):
File "/usr/bin/livecd-creator", line 215, in <module>
sys.exit(main())
File "/usr/bin/livecd-creator", line 198, in main
creator.install()
File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line
636, in install
ayum.setup(yum_conf, self._instroot)
File "/usr/lib/python2.7/site-packages/imgcreate/yuminst.py", line
100, in setup
self.doTsSetup()
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 129, in
doTsSetup
return self._getTs()
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 137, in
_getTs
if not remove_only and self._tsInfo.pkgSack is None:
File "/usr/lib/python2.7/site-packages/yum/transactioninfo.py", line
129, in <lambda>
pkgSack = property(fget=lambda self: self._getPkgSack(),
File "/usr/lib/python2.7/site-packages/yum/transactioninfo.py", line
126, in _getPkgSack
self._pkgSack = self._pkgSackCtor()
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 76, in
__call__
return self.ayum.pkgSack
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1013, in
<lambda>
pkgSack = property(fget=lambda self: self._getSacks(),
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 777, in
_getSacks
self.repos.populateSack(which=repos)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 337, in
populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 186, in
populate
if self._check_db_version(repo, mydbtype):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 294, in
_check_db_version
return repo._check_db_version(mdtype)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1358, in
_check_db_version
repoXML = self.repoXML
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1536, in
<lambda>
repoXML = property(fget=lambda self: self._getRepoXML(),
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1532, in
_getRepoXML
self._loadRepoXML(text=self)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1523, in
_loadRepoXML
return self._groupLoadRepoXML(text, self._mdpolicy2mdtypes())
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1497, in
_groupLoadRepoXML
if self._commonLoadRepoXML(text):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1332, in
_commonLoadRepoXML
self._revertOldRepoXML()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1168, in
_revertOldRepoXML
raise Errors.RepoError, "Can't download or revert repomd.xml"
yum.Errors.RepoError: Can't download or revert repomd.xml
[root@zoe james]#
11 years, 9 months
Kickstart post priority
by Jens Ruda
Hi
I have a kickstart which includes several other ks files. One of them is /usr/share/spin-kickstart/fedora-live-desktop.ks.
The fedora-live-desktop.ks %post creates some files that I need to modify.
How to determine the order of %post in all the included ks files? I can not get my %post script to run after fedora-live-desktop.ks.
I have collected this information from fedoraforum.org:- The %post sections from the %include are run first.- When a .ks that is called by %include calls another .ks with %include the second included %post runs first.
Is there any way to solve my problem so that the order/priority is always the same? And what about livemedia-creator?
Regards,
Jens
11 years, 9 months
Expanding the ext3 partition size in livecd
by Karthikeyan
Hi,
We are using the release version livecd tools we installed
using the yum tool. The version the package says is
PYTHON-IMGCREATE-17.11-1.FC17.I686. I am new to the mailing list and so
may not be exact about the terminologies you normally use. Pardon me for
that.
We normally create custom fedora spins on top of Fedora
Electronic labs (FEL) using the base-on option. The ext partition size
in the FEL used to be 8gb and we had enough space to install over
packages. But now we wanted to create our custom spin over standard
fedora core image. But the partition size of the fedora core was 4GB and
there was not enough space in the partition to install our packages.
So we wanted to increase the partition size by 8gb and so we specified
the following in the kickstart file
part / --size=8192 --fstype ext4
The ext3.mg file size changed from 4Gb to 8Gb but the problem was the
partition size remained as 4 Gb only. So we tried to debug the issue.
After the ext3.img is copied from the base-on image, the following
code is executed.
in fs.py, the method _mount_instroot of class
LoopImageCreator, the following line (Line no:930)
self.__instloop.mount()
calls the ExtDiskMount.mount() method (file:
fs.py Line no: 494). This method calls self.__create()
[ExtDiskMount.__create() file: fs.py line: 482] which calls
self.disk.create() (file: fs.py, line no:487). This function
[SparseLoopbackDisk.create() file: fs.py, line : 358] calls
self.expand(create=True) [SparseLoopbackDisk.expand(), file: fs.py,
line:331 ] and it changes the size of the file and does not change the
partition size. NOW IT SHOULD BE NOTED THAT THE SIZE OF THE FILE HAS
ALREADY INCREASED TO THE GIVEN SIZE BUT NOT THE PARTITION. Later in
ExtDiskMount.__create() [file: fs.py line: 482], the
self.__resize_filesystem() is called to resize the file system. In
__resize_filesystem() [ExtDiskMount.__resize_filesystem() file: fs.py
line: 467], the following logic checks [file: fs.py, line: 473]
if
size == current_size:
return
if the current size of the file (not
the partition size) is equal to the size asked to resize (which at this
stage will always be true) then return from the function.
So the logic
for resize2fs is never reached. So we commented out the above if
condition and tested the livecd and at this time the partition got
increased to 8gb and the custom spin was created successfully.
I am
not very sure of the exact fix for the bug as I am not sure about the
reason behind calling expand [SparseLoopbackDisk.expand(), file: fs.py,
line:331 ] method.
It would be helpful for us if you rectify the bug
and let us know if our approach was right.
--
Thanks &
Regards,
Karthikeyan G A
11 years, 9 months
Progress Report: Upping the 4gb filesystem limit
by David Laban
Just a heads up that I'm working on a couple of patches to
livecd-iso-to-disk that let you up the filesystem limit.
The current setup is:
filesystem
|_ livecd.iso
|_ squashfs.img --read-only?
|_ ext3fs.img
I have prototyped it, and I had to:
* cp --sparse=always ext3fs.img <filesystem with sparse support and
2.5GB free> // If I could mount the squashfs image read-write or do
some kind of snapshot/overlay, this would be unneccesary
* dd seek=8GB of=ext3fs.img
* losetup ext3fs.img
* resize2fs /dev/loopX // automatically expands to fill the whole
'partition' == 8GB
* mkdir -p tmp/LiveOS/
* mv ext3fs.img tmp/LiveOS/
* mksquashfs tmp squashfs.img // takes ages: has to re-compress 2.5GB
Can anyone give any hints on making this more efficient, or should I
submit a patch to
http://git.fedorahosted.org/git/?p=hosted/livecd;a=blob;f=tools/livecd-is...
as it is?
Also, I need to do more research into snapshots (had a wild goose
chase grepping the kernel source for "overlay") but I think that I
might be able to re-compact the overlay file into the squashfs using
the above process. Would anyone be interested in seeing a patch of
that form?
Also, I think that pre-allocating 2GB from /dev/zero on FAT
filesystems is pointless and needlessly slow. Doesn't the overlay grow
itself anyway? Also, isn't the limit 4GB for FAT32?
David.
11 years, 9 months
imgcreate/kickstart.py
by Brian C. Lane
imgcreate/kickstart.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit e23da6b92dca314e3ccdef99c4dd314e4c019aaf
Author: Brian C. Lane <bcl(a)redhat.com>
Date: Tue Jun 12 12:18:02 2012 -0700
imgcreate: Use copy2 for TimezoneConfig (#829032)
diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py
index ad69a87..aca4043 100644
--- a/imgcreate/kickstart.py
+++ b/imgcreate/kickstart.py
@@ -154,7 +154,7 @@ class TimezoneConfig(KickstartConfig):
f.write("UTC=" + utc + "\n")
f.close()
try:
- shutil.copyfile(self.path("/usr/share/zoneinfo/%s" %(tz,)),
+ shutil.copy2(self.path("/usr/share/zoneinfo/%s" %(tz,)),
self.path("/etc/localtime"))
except OSError, e:
log.error("Error copying timezone: %s" %(e.strerror,))
11 years, 9 months
GRUB2 booting from LiveCD ISO files?
by Joe Boyle
Hi there,
I've been experimenting with the livecd-creator tools on CentOS for
about a week now and made a lot of great headway for a project I'm
working on.
I'm hoping someone can help me with a problem I've bumped into - I am
struggling to create a GRUB2 entry which I can use to boot the LiveCD
ISO files I am creating with LiveCD. (I understand I could use
livecd-iso-to-disk to copy the contents of the ISO to a partition,
which I may ultimately have to do, however, I am hoping to be able to
boot the ISO directly.)
I think I'm quite close, as the following entry will correctly locate
and start the ramdisk:
menuentry "test image" {
set isofile="/iso/livecd-centos-livecd-minimal-201205310801.iso"
loopback loop (hd0,3)$isofile
# everything below here is suspect and made with imagination sauce:
linux (loop)/isolinux/vmlinuz0 setkmap=us isoloop=$isofile
initrd (loop)/isolinux/initrd0.img
}
However, during device detection, I receive this:
WARNING: Cannot find root filesystem!
I recognize this isn't entirely a LiveCD creator issue, as it relates
to both GRUB2 and kernel boot options, but I am hoping someone has
covered some of this ground in the past and can suggest something
helpful.
I suspect I'm not using the right kernel options, and am not sure
which kernel options would be appropriate for the centos livecd.
Thanks for reading, any/all advice is appreciated,
Joe
11 years, 9 months
F17 imgcreate SELinux failures
by Daniel Drake
Hi,
We use python-imgcreate to build OLPC images:
http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/buil...
and we distribute this to our customers to build their own, customised
images too.
Under F17, we aren't able to build images in this way when selinux is
enforcing on the host system.
When packages get installed and want to run ldconfig or groupadd,
selinux blocks them.
audit.log says e.g.:
type=SELINUX_ERR msg=audit(1338332428.453:68272):
security_compute_sid: invalid context
unconfined_u:unconfined_r:ldconfig_t:s0-s0:c0.c1023 for
scontext=unconfined_u:unconfined_r:rpm_script_t:s0-s0:c0.c1023
tcontext=system_u:object_r:ldconfig_exec_t:s0 tclass=process
type=SYSCALL msg=audit(1338332428.453:68272): arch=40000003 syscall=11
success=no exit=-13 a0=994dc48 a1=994c2f8 a2=994bfa0 a3=994c2f8
items=0 ppid=19050 pid=19051 auid=1009 uid=0 gid=0 euid=0 suid=0
fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=5527 comm="sh"
exe="/usr/bin/bash"
subj=unconfined_u:unconfined_r:rpm_script_t:s0-s0:c0.c1023 key=(null)
Is this a known issue?
Thanks,
Daniel
11 years, 9 months