spins August 2008

spins@lists.fedoraproject.org

11 participants
13 discussions

Appliance Operating System (AOS) Spin submission
by Bryan Kearney 28 Aug '08

28 Aug '08

I would like to submit for approval an Appliance Operating System (AOS) Spin. This spin is part of the appliance-tools feature [1] and also part of the thincrust project [2]. The Kickstart file can be found in the repo [3] but I have flattened it and attached it to this email. The goal of this spin is to provide a minimal base upon which software appliances can be built. The main deployment for appliances is expected to be virtual machine, but since there are no kernel changes this could work bare metal as well. This would be the fedora implementation of a JeOS [4]. We would like to target this for Fedora 10. Please let me know what next steps would be. Thank you. -- bk [1] https://fedoraproject.org/wiki/Features/appliance-tools [2] http://www.thincrust.net [3] http://git.et.redhat.com/?p=act.git;a=tree;f=config [4] http://en.wikipedia.org/wiki/Just_enough_operating_system_(JeOS)

4 15

Help creating a spin
by Jonathan Roberts 28 Aug '08

28 Aug '08

Hi all, I'm working as an intern with the Open Rights Group this summer, and my personal project for the next six weeks is to create a spin of Fedora that is going to be bundled with lots of free content, promoting the importance of the public domain and a vibrant commons, and then sent out to MPs (members of parliament). Kanarip said if I stopped by here people would be able to help me out with the spin side of it? I think we're going to use the standard Fedora live disc as our basis, and then we want to add symlinks on the desktop to the media folders that will be kept on the root of the disc. As well as this we're going to want to autostart Firefox and have it open up a copy of a local web page that will help to provide context to the content, as well as navigation. What do you guys think, will you be able to help out? Even a few links pointing me in the right direction will be a huge help as it's a big project even without the live cd. Thanks! Jon

5 11

Re: [Fedora-spins] rpmfusion based spin
by Jeroen van Meeuwen 26 Aug '08

26 Aug '08

CC'ing the Fedora Spins SIG mailing list as this concerns most of the subscribers there as well. KH KH wrote: > 2008/8/26 Rahul Sundaram <metherid(a)gmail.com>: >> Hi, >> >> I have been keep a tab on rpmfusion progress by reading the archives and it >> seems the repository is getting reading for launch soon. Congrats on that. >> >> My primary interest here at the moment is creating a spin based on rpmfusion >> and Fedora which Thorsten Leemhuis mentioned as desirable in one of his >> earlier mails to this list. > I don't know if Thorsten ever mention such "spin" but having both > rpmfusion and fedora on the same media is a very hard legal issue. > Actually that's even not possible at all without removing the name > Fedora from such spin. (meaning removing artworks and some others > packages i don't remember). FWIW, if RPMFusion wishes to provide and distribute their own version of Fedora, including whatever packages not in Fedora, either Free or free or not free at all, right now this is enough: %packages # Remove the fedora-logos package and include something without # Fedora trademarked material -fedora-logos generic-logos (or: rpmfusion-logos if you have the artwork) # Include rpmfusion-release as well rpmfusion-release %end %post # Substitute the Fedora name in /etc/fedora-release and /etc/issue, # which are both owned by package fedora-release, so that it doesn't # pop up in all kinds of weird places such as when booting the machine # ("Welcome to .... Press I to start interactive ..." comes to mind). # Note that _all_ trademarks are supposed to be in fedora-logos. sed -i -e 's/Fedora/RPMFusion/g' /etc/fedora-release /etc/issue %end And you're done. > To be more accurate: You can do such spins for yourself (either with > free only or with nonfree packages), but you cannot redistribute the > spin telling it is Fedora. (because it won't be fedora anymore). But > you can (have to ?) tell this work is based (derived?) on Fedora. > This (being able to say "based on Fedora") is pending the new trademark policy at https://fedoraproject.org/wiki/User:Pfrields/NewTrademarkGuidelines I hope this clarifies some of the issues wrt. a RPMFusion spin. Kind regards, Jeroen van Meeuwen -kanarip

3 3

Privacy Spin
by Jonathan Roberts 14 Aug '08

14 Aug '08

Hey, Is anyone interested in putting together a Fedora spin that comes with Tor + Privoxy fully preconfigured and turned on for all the internet apps that can use it in a default Fedora spin? Been doing some reading on this as part of my internship, and I think it would be a cool addition to our list of spins. Will happily do the leg work myself on it but I probably won't get the time to do it until September, so maybe I'll see about doing it at FUDCon if anyone was interested in joining me. Can't imagine it would take *that* long. Best wishes, Jon

2 3

[Fwd: [Fwd: Re: Appliance Operating System (AOS) REVIEW - NEEDINFO]]
by Bryan Kearney 14 Aug '08

14 Aug '08

Forwarding from David huff, who is having posting permissions fun. -- bk -------- Original Message -------- Subject: [Fwd: Re: [Fedora-spins] Appliance Operating System (AOS) REVIEW - NEEDINFO] Date: Thu, 14 Aug 2008 10:52:46 -0400 From: David Huff <dhuff(a)redhat.com> To: Bryan Kearney <bkearney(a)redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -------- Original Message -------- Subject: Re: [Fedora-spins] Appliance Operating System (AOS) REVIEW - NEEDINFO Date: Thu, 14 Aug 2008 10:20:27 -0400 From: David Huff <dhuff(a)redhat.com> To: Jeroen van Meeuwen <kanarip(a)kanarip.com> CC: The Spin Special Interest Group mailing list <fedora-spins(a)lists.fedoraproject.org> References: <48A172BD.9060109(a)redhat.com> <48A369CB.7060002(a)kanarip.com> <48A4200E.9010907(a)redhat.com> <48A4319A.4070003(a)kanarip.com> Jeroen van Meeuwen wrote: >>> >>> == Kickstart == >>> >>> First of all, since this is a unique spin concept in that it has a >>> specific goal, these notes and corresponding feedback needs to be >>> taken into account by the Spin SIG as well as the spin maintainers... >>> >>> 1) SELinux on this spin is disabled. Although understandable, we >>> would like to see if SELinux could be enabled, or hear about why it >>> is disabled entirely (rather then set permissive). SELinux is a major >>> major feature in Fedora as well as RHEL, so we would like to preserve >>> SELinux as a feature on all spins. >> >> There is an issue with the appliance-tools and selinux. I will need to >> defer to David Huff on this and have him respond in a separate message. >> > > The existing issue is that if livecd-tools and so also probably > appliance-tools is run on a box with SELinux in enforcing mode, inside > the chroot the right context cannot be set. Spins are therefor composed > on hosts with SELinux set to permissive mode. This is exactly the case. Also in order to cut down on size we have removed a lot of the selinux packages in the kickstart file, which im not really sure how much size that saves. I agree that it would be nice to have selinux enable by default which would require building the image on a box that has selinux enabled. However the sad reality is that most isvs and/or 3rd party software run with selinux disabled. However I do not have a problem with enabling selinux by default. > >>> 2) A root password is set, which is understandable for real live >>> systems but is not conform the other spin concepts where an >>> additional, normal user is created and the root password is removed. >>> If there is a motivation for setting a root password and not creating >>> a (regular) user in this spin concept, please let us know. >> >> This spin is really seen as a base upon which someone would "build" an >> appliance. As appliances tend to be locked down in most cases, the >> root user is probably the only user who would log into the machine. >> Anyone building upon this would probably want to remove the user. >> > > True as far as the custom user is concerned, however a default password > for the root user is worse then no password, given that remote access is > prevented when not having a password, while allowed when knowing the > default password. Although this spin does not contain nor start sshd, I > can only assume that is the first thing some people will want to add. > Additionally, it has been proven a pain in the *ss to communicate a > default password alongside a spin. I am fine with take off the rootpw. I think the only reason we set it is b.c we had issues with building an image without one. However form your above statements it looks like the appropriate work around is to remove the root pw in the post section as well as creating a normal user. > >>> >>> 3) the partitioning configuration has --ondisk sda as well as >>> --fstype ext3 which is not taken into account with creating a live spin. >> >> The appliance-tools do take these into acocunt, and utilize them to >> set up the partitioning on disk. >> > > Noted, and maybe worth a little comment entry in the kickstart - it > doesn't really apply to this particular spin that we would be releasing > via the Fedora Project, but it does apply for people wanting to continue > and build upon this spin (and use this kickstart). sounds good > >>> 5) the kickstart removes fedora-logos, but does not add another logos >>> package, resulting in that fedora-logos still ends up on the image. A >>> minor problem for when the spin is approved by the Board for >>> trademark usage, but you may want to add "generic-logos" to the >>> manifest for now. >> >> I have added in generic logos. Once the new tradmark policy is put >> into place, I would like to add the secondary marks to this kickstart >> file. >> > > Yes, after trademark approval by the board, you are allowed to kick back > in the fedora-logos package as well. agreed > >> Thanks again. Updated kickstart file is attached. >> > > Thanks for the quick response. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkikRrwACgkQccHK32ogu/fdOwCfe+hIp+Hk3c/j366ObxVALPhC ZvkAnRSYm2wD/W2H+nBkOP3Jnks8aS/p =/2Fw -----END PGP SIGNATURE-----

1 0

Re: [Fedora-spins] BrOffice.org Spin
by Jeroen van Meeuwen 13 Aug '08

13 Aug '08

Igor Pires Soares wrote: > Hi Jeroen! > > Is there a way to get my spin kickstart included into Kickstart Pool? > > The file is the following: > http://igor.fedorapeople.org/BrOffice.orgSpin/fedora-livecd-broffice.org.ks > > BrOffice.org Spin Feature Page: > https://fedoraproject.org/wiki/Features/BrOffice.orgSpin > Hi Igor, submit your spin (the kickstart) to the Fedora-spins(a)lists.fedoraproject.org list (in CC:), and one of the Spin SIG members will review the technical aspects, and get back to you. Meanwhile, we'll probably discuss the spin on the fedora-spins m-l, so if you watch it, you can chime in ;-) Kind regards, Jeroen van Meeuwen -kanarip

2 3

Developer and Electronic-Lab Spins
by Jeroen van Meeuwen 13 Aug '08

13 Aug '08

Guys, you are lacking Feature Pages, and are therefore not yet approved by Release Engineering to be composed for the Beta. Create your feature pages and drop a note on both the fedora-spins mailing list, as well as the fedora-advisory-board for trademark approval, after which you can continue to move to the rel-eng mailing list at lists.fedoraproject.org to get your final approval. Most appropriate would be to do so in advance of the Beta Feature Freeze, coming up August 19th. Kind regards, Jeroen van Meeuwen -kanarip

3 4

Approved Spins for F10 Beta and branching off the spin-kickstarts repo
by Jeroen van Meeuwen 12 Aug '08

12 Aug '08

Although also the feature freeze, these are the spins approved for F10-Beta, and are thus going to be composed. Given a certain set of conditions to be met in advance, of which all the spin maintainers have been notified, these are the spins that are going to be composed: fedora-livecd-desktop-default.ks fedora-livecd-education-math.ks fedora-livecd-kde.ks fedora-livecd-xfce.ks fedora-livedvd-games.ks Spins in the spin-kickstarts GIT repository which will not be composed as of yet, awaiting certain conditions to be met, are: fedora-livecd-broffice.org.ks * Note: awaiting review by the Spin SIG which will happen tomorrow, by me fedora-livedvd-developer.ks * Feature Page lacking fedora-livedvd-electronic-lab.ks * Feature page lacking August 19th, during whatever is daytime for me, I'll be branching off the spin-kickstarts GIT repository into F-10-Beta, from which the F-10-Beta images will be composed. Development can continue in the master branch, which is the branch that moves with rawhide. Note that _any_ questions can be asked on this list and will be answered promptly as I'm watching this list like a hawk, so if you have any questions regarding the process, the required Feature pages, and whatnot, please _do_ ask. Kind regards, Jeroen van Meeuwen -kanarip

3 6

!!! [Fwd: Fedora 10 Beta Freeze coming soon]
by Jeroen van Meeuwen 11 Aug '08

11 Aug '08

For anyone who has not (yet) read this on the -devel or -devel-announce mailing list, here's how this is going to end: Features (in our case, spins) which are not approved by FESCo Aug 19th, will -no matter how regrettable- not make it into the release. Even if in your perception is your spin is approved by the Spin SIG, approved by the Board to carry the Fedora trademark, and approved by FESCo, now is the time to poke around and shake up some people to verify if that's really the case, or you're in for a big disappointment. The following spins carry the Spin SIG approved flag: fedora-livecd-desktop-default.ks fedora-livecd-education-math.ks fedora-livecd-kde.ks fedora-livecd-xfce.ks fedora-livedvd-developer.ks fedora-livedvd-electronic-lab.ks fedora-livedvd-games.ks Awaiting approval is: fedora-livecd-broffice.org.ks And they will be put through compose tests over the next week. You will need to ensure your kickstart composes nice and easy, using the latest livecd-tools in rawhide, against the rawhide trees, note bug numbers related to your spin in the kickstart, and sign-off on them becoming a feature to be released by the Fedora Project, with help of the Fedora Project, before the Big Evil Beta Freeze, so that FESCo can verify and Release Engineering can compose. Note that this endeavor also requires your Feature page on the wiki to be in the appropriate category (CategoryProposedFeaturesF10 IIRC, please check for yourselves), so that FESCo has a tracker. Kind regards, Jeroen van Meeuwen -kanarip -------- Original Message -------- Subject: Fedora 10 Beta Freeze coming soon Date: Mon, 11 Aug 2008 13:02:55 -0400 From: Jesse Keating <jkeating(a)redhat.com> Reply-To: fedora-devel-list(a)redhat.com Organization: Red Hat To: fedora-devel-announce(a)redhat.com The Fedora 10 Beta freeze is scheduled for the 19th of Aug, one week and one day away. I know it hasn't been very long since the Alpha release, but that's how we roll here in the land of 6 month release cycles. Beta freeze also marks the Feature freeze, so it is very important that you get your features into working, testable shape by then, or be prepared to try your feature again for Fedora 11. We'd like to treat rawhide as a slushy freeze at this point, we'll be doing full composes against rawhide to test for various things and be ahead of the curve come actual freeze time, so we'd like you to not land any really dangerous changes without extensive testing first, and notification to the Fedora lists about your scary change. If we all work together we can get through the beta freeze period quickly and be on to the bugfixing mode after beta releases. http://fedoraproject.org/wiki/Releases/10/Schedule is the current schedule, although releng/Fesco/Board has the ability to change the schedule as needed. This week's meetings of the various boards, sigs, groups, etc.. should focus on Beta readiness. It would be good to take a moment to see what state your area of interest is in, and how likely it would be that said area of interest will be in a "testable" shape by the Beta freeze. If more (reasonable) time is needed, now is the time to let the project know so that we can effectively manage the remainder of our release schedule. Thanks for all your hard work in making Fedora 10 great! -- Jesse Keating Fedora -- FreedomÂ² is a feature! identi.ca: http://identi.ca/jkeating _______________________________________________ Fedora-devel-announce mailing list Fedora-devel-announce(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce

1 0

revisor vs livecd-creator
by Don Raikes 05 Aug '08

05 Aug '08

Hi all, I have been readig a lot of posts on this list lately, and wonder if someone can give me some clarification on the difference between revisor and livecd-creator. As a blind user, unfortunately, I cannot run revisor in gui mode since it is not accessible using orca on the gnome desktop, so I am not sure what benefits I would gain from using revisor. I have created a couple of livecd's using livecd-creator, and while the process is a bit time-consuming, it seems to be pretty successful. Any info would be appreciated. Donald Raikes | Accessibility Specialist Phone: +16028246213 | Fax: +15207440826 | Mobile: +15202717608 Oracle JDeveloper QA ORACLE United States | | Tucson, Arizona "Please consider your environmental responsibility before printing this e-mail"

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

spins August 2008