we have a result on the spins SIG meeting time. Unfortunately we were
not able to find a time that works for everybody. The maximum number of
people that could make it are 8 (out of 10) on Monday 20:00 UTC.
The following people would currently be excluded:
I'd like to ask both of you to look into the poll at
again, especially Jan as he is most inflexible person and Jaroslav,
since I really like to have him with us as a representative of KDE.
A note to all spin-kickstarts committers: Please be so kind as to
mention the ks or the spin at the beginning of your commit message.
"Save some space"
"KDE: Save some space"
"fedora-live*-kde.ks: Save some space" (affects both fedora-live-kde.ks
Only abandon the spin/kickstart if it is a global change, that affects
Most committers already do this, so please consider this only a small
reminder. I am convinced that this will make our lives easier.
Author: Joerg (kital) Simon <jsimon(a)fedoraproject.org>
Date: Mon Feb 28 14:45:40 2011 +0100
removed gmixer - caused build error
fedora-livecd-security.ks | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fedora-livecd-security.ks b/fedora-livecd-security.ks
index 7dabcf2..a94b105 100644
@@ -4,12 +4,12 @@
# A fully functional live OS based on Fedora for use in security auditing, forensics research, and penetration testing.
# Christoph Wickert <cwickert [AT] fedoraproject <dot> org>
-# Hiemanshu Sharma <hiemanshu [AT] fedoraproject <dot> org>
# Joerg Simon <jsimon [AT] fedoraproject <dot> org>
# Fedora LiveCD Xfce Spin team - some work here was inherited, many thanks!
# Fedora LXDE Spin - Copied over stuff to make LXDE Default
# Luke Macken, Adam Miller for the original OpenBox Security ks and all the Security Applications!
+# Hiemanshu Sharma <hiemanshu [AT] fedoraproject <dot> org>
# Beginning with Security Stuff - we use pattern to parse the kickstart-file for building the security menu - please use
# # Category: Categoryname <- for new Categories
@@ -31,7 +31,8 @@ xarchiver
Looking at bug https://bugzilla.redhat.com/show_bug.cgi?id=679880 it
seems that prelink does make things a bit faster if run on the live
image at compose time, as well as saving lots of memory if run for more
than a day (when the prelink cron kicks in).
Anyone have objections to adding a prelink call to the end of the live
base compose? Or should we just disable it entirely?