I have been trying to create a simple livecd of fedora 9 for myself including some apps like brltty, w3m, and epic.
I started with the fedora-live-base.ks file, and included that in my afl.ks file.
I added my packages in the %packages section of afl.ks, and added a %post section to set my passwords and perform a few housekeeping tasks.
When I generate the iso using livecd-creator, all seems to go fine, and when I boot off of the cd it seems fine as well.
The problem comes in that I have no networking on the livecd.
There is no refference to my nic card in /etc/sysconfig/network-scripts. I would have expected an ifup-eth0 script there, but nothing.
In the fedora-livecd-ks file,
services --enable=networkmanager is set.
Any thoughts would be appreciated.
Donald Raikes | Accessibility Specialist
Phone: +1 602 824 6213 | Fax: +1 520 744 0826 | Mobile: +1 520 271 7608
Oracle JDeveloper Quality Assurance
| Tucson, Arizona
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
Let's begin with an apology, shall we? Sorry for cross posting, but
this does concern people on multiple mailing lists.
I would like to announce the formation of a Fedora Geo Spin with tools
for integration into Open Street Map. For more information, please see
the following link:
In short, the Fedora Geo Spin will be a respin of Fedora with packages
for doing OSM and cartography installed out of the box, or included on
a LiveCD and/or LiveUSB. For OSM people, the primary advantage is a
live usb stick that can be used at mapping parties to save time
configuring user computers to do mapping. The USB stick can then be
brought home, and the user can continue doing mapping there. For
Fedora people, it gives us better Fedora exposure.
Right now, the spin is a draft, and once completed will be submitted
to the Fedora Spins process for approval and inclusion in Fedora as a
The link above will be the canonical todo list, for anyone looking to
participate. If you wish to help, please feel free to contact me on
or off these email lists.
As you might be aware already, Red Hat Legal has been working on the
text for a licensing agreement that will be used to formally give
permission for groups outside the Fedora Project to use the Fedora
name in their domains, group names, and so forth. Red Hat recognizes
there is great value in this to Fedora and Red Hat itself, so the
intent is to have the agreement cover uses to which we know people are
putting the Fedora trademarks now.
One of those uses is the Fedora Respins. I want to make sure that the
agreement is explicitly allowing coverage of the Respins, but to do
that I wanted to make sure I have the construction clear in my mind.
If the Fedora Respins include software that Fedora hasn't explicitly
released verbatim, like a patched anaconda, I want the trademark
license agreement to permit that use. If patches to anaconda are now
being mainlined by its upstream, regardless of whether they're issued
in an updated package, then the language might need to be slightly
Jeroen, can you tell me what the current process is for issuing
Respins, and where, if any, packages or content on the Respins differ
from what Fedora has officially released in its software repositories?
Then I can make sure the proper language gets into the agreement.
Once I have that agreement in hand, I'll send a copy to the
appropriate contact for Fedora Unity (along with its other
destinations) to be executed.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
For reviews to go smoothly, I've set up a page that lists some of the
prerequisites, and so forth, resulting in a checklist for our Review stage:
Regrettably, I do not have an endless imagination, so this list is
probably getting bigger and bigger, and amended as we go along.
We will want to determine whether this is a good starting point on
Monday, 17:00 UTC, during our Spins SIG meeting.
Meanwhile, feel free to add checks to the checklist, ask questions on
specific items in there already, and discuss things using the Talk: page
or through this mailing list.
FWIW: This checklist does not yet have localized spins and checks for
submitted localized spins, yet.
Jeroen van Meeuwen
Following is more information on the PROPOSED Spins process.
As we move forward I think the first place we need to have agreement is
that while a "spin may be a feature of a release" it is confusing to
refer to them as "Features" in the traditional Fedora sense. Therefore
they should simply be referred to as "Spins" or "Fedora 11 Spins". From
the previous thread I realize there is lots of past history around this
topic. I'd propose we focus our energy on moving forward to creating
something that can work for Fedora 11 versus rehashing the "whys" of the
After meeting last Friday at FUDCon there was still not a well laid out
process around how all the details for each spin would be tracked. A
few of us talked more on Sunday and came up with a proposed process. It
mirrors the Feature Process in the way wiki pages and categories are
used and deviates from it by using a different Spins page template and
different required approvals.
I am volunteering to act as the "Spins Wrangler" for Fedora 11 if the
Spins SIG would like me to--no hard feelings if they prefer someone else :)
I expect this will all be discussed at Monday's meeting. If you have
proposed changes or other ideas I'd suggest adding them to the wiki page
so they don't get lost on this mailing list.
I'd like to request technical approval for a new Spin for F11 on behalf
of the Education SIG. As you may know, we've had an "education-math"
spin for F10 around, but for the new release, we've worked out
completely new concept, and that's why we'd like to withdraw the old
spin and replace it with a new one.
I've already drafted up a kickstart file, which is available here .
It's pretty much complete right now, but it might be that we'd like to
add the one or other app within the next few days or so. Nevertheless, I
thought it would be a good idea to bring this up before the meeting.
If you're searching for further information, we've also got a wiki page
The Spins SIG is going to have regular, bi-weekly meetings. I've chosen
Mondays at 18:00 UTC, on even weeks, and it will not take more then one
Obviously, we can pre-discuss most of the items on the agenda on our
mailing list fedora-spins -at- lists.fedoraproject.org.
With help of several key people in the current Spins process, including
Process-Guru and current Feature Wrangler John Poelstra, we've come up
with a real Spins Process during this last FUDCon.
If you are a member of Release Engineering, Quality Assurance, FESCo or
Infrastructure, I would like you to attend.
Our first meeting (in the series of regular meetings) would be January
19th, 18:00 UTC, for which I'm going to set the Agenda now:
== Agenda ==
# Finalizing Spins Process, vote
#* Writing up details on the Wiki, where necessary
#* Writing our Spins_SIG_Review_Checklist, and what to do if something
#* Maintainer responsiveness and responsibilities for current releases
#* Checklist of DOs and DONTs, SHOULDs and SHOULD NOTs
#* Defining permanent vs. non-permanent spins, the procedure to change
status, and the consequences for the Spins Process.
# Set our final meeting time and schedule, vote
# Determine our workflow (using the spin-kickstarts Trac instance?)
#* Branching and tagging (based on milestones to be determined)
#* Creating daily spins for compose tests and reporting results
#* Having maintainers (re-)create spins regularly for tests and
# Determine our process for recurring releases and reviewing current
spins for the upcoming release
# Current Spins Requests:
#* Games Spin
#** Has been previously approved
#** Failed during Fedora 10
#** Revamped for Fedora 11 by Bruno Wolff III
#* A dozen or so localized spins
# Review of all current spins
#* Who's the maintainer of each spin, and where can we reach them?
#* Fedora AOS
#* Fedora BrOffice.org
#* Fedora Developer
#* Fedora Education Math
#* Fedora Electronic Lab
#* Fedora Games
#* Fedora Sugar
#* Fedora XFCE
This agenda is also available (in a more readable format) on:
Additional Agenda items you may have can go to that Wiki page as well.
Again, if you are a member of Release Engineering, Quality Assurance,
FESCo or Infrastructure, I would like you to attend also. In the new
process, the Spins SIG meetings are where you can say "no" or "yes" to a
spin, or raise concerns. I would like to know if you agree with that.
Also, I'd like to know if you (or a delegate of your team) wants to
attend our meetings, or settles with being notified by the Spins SIG
every step of the way.
Now, in my Agenda, the time for our first meeting would already conflict
with a very important appointment I have with Max next week -which I'm
not going to reschedule, it includes dinner :P I'll make it work one way
or the other, though, so there'll definitely be a meeting at January
19th, 18:00 UTC. Be there or forever hold your peace ;-)
Jeroen van Meeuwen
We would like to include a base-pkg list in the snippets directory for the Appliance operating system definition or spin.
One of the main pourposes of the AOS is to define a minimal package set that others can build on. The hope is that this package set will evolve overtime.