FWN/Issue177

From FedoraProject

< FWN(Difference between revisions)
Jump to: navigation, search
(add Ambassadors, Translation, SecurityAdvisories, Virtualization)
(add welcome)
Line 1: Line 1:
 +
= Fedora Weekly News Issue 177 =
 +
 +
Welcome to Fedora Weekly News Issue 177<ref>http://fedoraproject.org/wiki/FWN/Issue177</ref> for the week ending May 24th, 2009.
 +
 +
This week we offer a special collector's edition with the last ever Fedora Webcomic. PlanetFedora links Jeff Shelten's thoughts on "Why Students Should Get Involved in Open Source", Ambassadors reports on "Fedora en Mexico", Developments is getting "In a Flap Over Flags", QualityAssurance takes a look at a "Beagle/Tracker Blocker Bug Proposal", Artwork says goodbye to itself but welcomes Design. SecurityWeek examines the problems of "Cloudy Trust". Translations notes that "Sections of the Fedora User Guide Cannot be Translated". SecurityAdvisories includes an <code>ipsec-tools</code> update. Virtualization shares details on the "Rawhide Virtualization Repository".
 +
 +
 +
If you are interested in contributing to Fedora Weekly News, please see our 'join' page<ref>http://fedoraproject.org/wiki/NewsProject/Join</ref>. We welcome reader feedback: fedora-news-list@redhat.com
 +
 +
FWN Editorial Team: [[User:Pcalarco|Pascal Calarco]], [[User:Ush|Oisin Feeley]], [[HuzaifaSidhpurwala|Huzaifa Sidhpurwala]]
 +
 +
<references/>
 +
 
{{Anchor|PlanetFedora}}
 
{{Anchor|PlanetFedora}}
 
== Planet Fedora ==
 
== Planet Fedora ==

Revision as of 12:00, 25 May 2009

Contents

Fedora Weekly News Issue 177

Welcome to Fedora Weekly News Issue 177[1] for the week ending May 24th, 2009.

This week we offer a special collector's edition with the last ever Fedora Webcomic. PlanetFedora links Jeff Shelten's thoughts on "Why Students Should Get Involved in Open Source", Ambassadors reports on "Fedora en Mexico", Developments is getting "In a Flap Over Flags", QualityAssurance takes a look at a "Beagle/Tracker Blocker Bug Proposal", Artwork says goodbye to itself but welcomes Design. SecurityWeek examines the problems of "Cloudy Trust". Translations notes that "Sections of the Fedora User Guide Cannot be Translated". SecurityAdvisories includes an ipsec-tools update. Virtualization shares details on the "Rawhide Virtualization Repository".


If you are interested in contributing to Fedora Weekly News, please see our 'join' page[2]. We welcome reader feedback: fedora-news-list@redhat.com

FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala

  1. http://fedoraproject.org/wiki/FWN/Issue177
  2. http://fedoraproject.org/wiki/NewsProject/Join

Planet Fedora

In this section, we cover the highlights of Planet Fedora[1] - an aggregation of blogs from Fedora contributors worldwide.

Contributing Writer: Adam Batkin

  1. http://planet.fedoraproject.org

General

Michael DeHaan wrote[1] an essay "Recognizing and Avoiding Common Open Source Community Pitfalls" such as that "contributors appear overnight out of the woodwork, that users grow on trees, and that it’s possible to direct community members as if they were employees."

Thorsten Leemhuis asked[2]: "What questions would you like to ask the Fedora Board or FESCo Candidates?" for the upcoming Fedora Board and FESCo elections. "Hence we need to prepare a few good questions that we can send to the candidates once the nomination period ends. And that's where I need *your help*"

Richard W.M. Jones announced[3] the first proper version of virt-inspector, "a command line tool that tells you what’s in a virtual machine. You just point it at a disk image or a libvirt domain" and it can discover a number of pieces of information about the installed VM.

Thomas Canniot posted[4] a How-To about running a successful release event. "Fedora 11 is going to be released at the end of the month and very soon, our massive army of ambassadors will want to spread how proud they are of their Fedora 11 release to the masses."

Jef Spaleta calculated[5] new Fedora usage statistics that combined the Smolt and MirrorManager logs to come up with some very interesting new numbers.

Paul W. Frields responded[6] to the recent discussions about the new fedora-devel moderation policy. "There’s simply no place in free software, and certainly not in Fedora, for that kind of abuse. Of course harsh words aren’t the end of the world. When we let them become the noise that drowns out the signal, though, we’re putting the project at risk. If contributors feel their time in community discussions are wasted, they will either hold them elsewhere, or simply go away."

Jack Aboutboul interviewed[7] Lennart Poettering ("Red Hat Desktop Team Engineer and resident audio guru") about Pulse Audio and audio in Fedora.

Susan Lauber wrote[8] about "how can you - a Fedora contributor - assist in making the wiki more useful for everyone?" For anyone wondering how they can start contributing to Fedora, this is a great way to start, without any long-term commitments.

Nicu Buceli reported[9] from eLiberatica 2009[10] in Bucharest, Romania.

Jeff Sheltren discussed[11] "Why Students should get Involved in Open Source". Jeff says that "from my experience, open source experience has given our student employees an enormous boost when looking for their first jobs out of college."

Adam Williamson mentioned[12] the Common F11 bugs wiki page, and how you can help: "It’s really easy - everything you need to know to add an issue to the Common Bugs page is right there in the page source, as a comment. If you edit the page you’ll see a few chunks of comments which explain how to add an issue (including a template entry), and what else to do when adding one..." James Laska also suggested[13] that there are still some high priority defects that could use some extra testing in preparation for the imminent Fedora 11 release.

Thorsten Leemhuis explained[14] that "There is one small change in Fedora 11 that I guess will confuse Fedora and RPM Fusion users with x86-32 (aka i386/ix86) systems quite a lot, but afaics did not get enough attention yet: By default, the PAE kernel will be used on 32-bit hardware, where appropriate."

  1. http://michaeldehaan.net/2009/05/17/oss-pitfalls/
  2. http://thorstenl.blogspot.com/2009/05/what-questions-would-you-like-to-ask.html
  3. http://rwmj.wordpress.com/2009/05/19/virt-inspector/
  4. http://blog.mrtomlinux.org/index.php?post/HowTo-run-a-successful-IP
  5. http://jspaleta.livejournal.com/42464.html
  6. http://marilyn.frields.org:8080/~paul/wordpress/?p=1653
  7. http://jaboutboul.blogspot.com/2009/05/sound-of-fedora-11.html
  8. http://travelingtrainer.laubersolutions.com/2009/05/revisiting-wiki-search-and-cleanup-part.html
  9. http://nicubunu.blogspot.com/2009/05/preamble-to-eliberatica.html
  10. http://www.eliberatica.ro/2009/
  11. http://sheltren.com/students_in_oss
  12. http://www.happyassassin.net/2009/05/22/fedora-11-common-bugs-page/
  13. http://jlaska.livejournal.com/5561.html
  14. http://thorstenl.blogspot.com/2009/05/fedora-11-kernel-pae-and-what-it-means.html

Ambassadors

In this section, we cover Fedora Ambassadors Project[1].

Contributing Writer: Larry Cafiero

  1. http://fedoraproject.org/wiki/Ambassadors

Fedora en Mexico

Alejandro Acosta recently presented the remixes workshop at the May session of the local Linux User Group know as Gluch in Chihuahua, Mexico. The reason is that many of the members of the Gluch could not attend the workshop at Flisol since they where helping out in other tasks.

Alejandro created a customized distro based on Fedora AKA Remix and then tested it on a LiveUSB.

A report on the activities can be found here [1] and at the Fedora Mexico Facebook page here [2].

In addition, Alejandro also gave a talk about Fedora to COPI (an organization of college IT professionals) at their May 2009 meeting. A report on the talk at COPI can be found here [3].

  1. http://alexacosta.wordpress.com/eventos/fedora-workshop-gluch-may-09/
  2. http://www.facebook.com/pages/Fedora-Mexico/71816678729?ref=ts
  3. http://alexacosta.wordpress.com/eventos/fedora-talk-copi-may-09/

Tips on Fedora 11 release events

Thomas Canniot posted a very helpful guide in his blog for those who are holding events around the upcoming Fedora 11 release.

Thomas' blog can be found here [1].

  1. http://blog.mrtomlinux.org/index.php?post/HowTo-run-a-successful-IP

Announce your Fedora 11 events

With the upcoming release of Fedora 11, posting your event on Fedora Weekly News can help get the word out. Contact FWN Ambassador correspondent Larry Cafiero at lcafiero-AT-fedoraproject-DOT-org with announcements of upcoming events (and don't forget to e-mail reports after the events as well).


QualityAssurance

In this section, we cover the activities of the QA team[1].

Contributing Writer: Adam Williamson

  1. http://fedoraproject.org/wiki/QA

Test Days

There was no Test Day last week, as we are deep in the Fedora 11 final release run-up.

Currently, no Test Day is scheduled for next week - it is too close to the scheduled release of Fedora 11 for any testing to produce results directly in Fedora 11 final release, but if you would like to propose a test day which could result in changes for post-release updates, or an early test day for Fedora 12, please contact the QA team via email or IRC.


Weekly meetings

The QA group weekly meeting[1] was held on 2009-05-20. The full log is available[2]. Adam Williamson reported that he had filed a ticket to have Bodhi use the appropriate resolution for bugs fixed with stable release updates. Luke Macken said he would take care of the ticket. Adam also reported that he had not yet remembered to ask the Bugzilla team to add a link to the Fedora bug workflow page.

James Laska reported that he had not yet sent out a Test Day feedback survey to previous participants, but had a draft ready and would continue to work on it.

John Poelstra said that he had not yet finalized a schedule for blocker bug reviews during the Fedora 12 cycle, as the overall Fedora 12 cycle was still not finalized. He will revisit the issue next week.

Will Woods reported there had been little work on the autoqa project or adding upgrade test cases to the Wiki during the week, as testing for Fedora 11 release had taken priority.

The group discussed the Fedora 11 release situation, and noted that the release had been pushed back one week. They examined the blocker bug list, and found it was generally manageable. Francois Cami noted that major fixes to X.org's core or the ATI driver were unlikely as Dave Airlie is on vacation. The group noted that most remaining X.org blockers were in the Intel driver, and assigned to

The group then discussed the Fedora 11 Common Bugs page[3]. Adam Williamson volunteered to revise the existing page to match the format used for previous releases, initiate a few other changes based on his previous work on Mandriva Linux Errata pages, and talk to other groups about the use of the page, including the Documentation group, and the IRC, mailing list and forum support teams. Francois Cami volunteered to help ensure all appropriate X.org issues are tracked on the page.

In open discussion, Francois Cami noted that for Fedora 11, users of several generations of ATI Radeon cards would now only have the free drivers as a viable choice, whereas previously they would be able to use the ATI proprietary driver from third-party repositories. It was also noted that, at release time, the commonly-used RPMFusion repository would have no packages available for the proprietary driver even for cards for which it is still available, due to the lack of a reliable patch for kernel 2.6.29. The group discussed whether this could be explained in the release notes (with no definite resolution, but advice to check with the Documentation team), and how to note the requirements for a full and useful bug report for problems with the free driver from such users. Adam Williamson noted that the appropriate venue for such information would be the Bugs and Feature Requests Wiki page[4].

The Bugzappers group weekly meeting[5] was held on 2009-05-19. The full log is available[6]. John Poelstra reported on progress of the housekeeping changes for Fedora 11's release, and the group agreed that he was doing a fine job and should keep it up.

Adam Williamson reported on the progress of the triage metric system. Brennan Ashton has again been busy (and without access to a regular internet connection), so progress has been slow. Adam clarified that the main choke point now was the lack of a set of test data for the scripts, to ensure that they were working correctly, and explained he was doing his best to get this data made available. Once it is available, work on the system is no longer solely dependent on Brennan being available.

Adam Williamson also reported on the progress of the proposal to include setting the priority / severity fields as part of triage. He had sent out the mail asking for feedback on how to proceed, but had received none yet. The group agreed that he should send out another mail as a new thread, and set a deadline of the end of the week; if no significant feedback to the contrary was received by that point, the group agreed they should proceed using the method proposed by Matej Cepl.

The next QA weekly meeting will be held on 2009-05-27 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-05-26 at 1500 UTC in #fedora-meeting.

  1. http://fedoraproject.org/wiki/QA/Meetings
  2. http://fedoraproject.org/wiki/QA/Meetings/20090520
  3. http://fedoraproject.org/wiki/Common_F11_bugs
  4. http://fedoraproject.org/wiki/BugsAndFeatureRequests
  5. http://fedoraproject.org/wiki/BugZappers/Meetings
  6. http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-May-19

Blocker bug review meeting

John Poelstra announced[1] a joint QA / Release Engineering Fedora 11 blocker bug review meeting on Friday 2009-05-22. The meeting was not logged, but all outstanding release blockers were reviewed, some were closed or downgraded, and action plans were decided for several.

  1. http://www.redhat.com/archives/fedora-test-list/2009-May/msg00946.html

Adobe Flash installation instructions

Christopher Beland explained[1] that he had updated the Wiki page on Flash[2] with the latest instructions on installing it on x86-64 systems. Adam Williamson noted[3] that the page should emphasize free software alternatives as well as the proprietary Adobe Flash system. Paul Frields announced[4] that he had made such a change.

  1. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01004.html
  2. http://fedoraproject.org/wiki/Flash
  3. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01006.html
  4. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01027.html

Fedora 11 Common Bugs page

Adam Williamson announced[1] his revisions to the Fedora 11 Common Bugs page, and asked the group to contribute to expanding and maintaining the page and consistently refer to it when explaining problems. He also explained some of the planned improvements to the content of the page and its interaction with Bugzilla.

  1. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01026.html

Mozilla / Beagle blocker bug proposal

Jonathan Kamens asked[1] whether a bug preventing Beagle from searching Mozilla Firefox and Thunderbird data should be a release blocker, on the basis that desktop search is a key function for some users and web browser and email data are important sets which someone may wish to search. Brian Pepple pointed out[2] that it did not meet the official release blocker criteria[3], but Jonathan responded that the page admits this is a subjective judgment, and many bugs that do not strictly meet those criteria are in fact considered blockers. In the end, it was mostly agreed that, because Beagle is not installed by default and so is not considered core functionality, the issue should not be considered a blocker.

  1. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01041.html
  2. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01042.html
  3. http://fedoraproject.org/wiki/QA/ReleaseCriteria

New Bugzappers

Two new Bugzappers volunteers introduced themselves this week: Xia Shing Zee[1] and Alex Turner[2].

  1. http://www.redhat.com/archives/fedora-test-list/2009-May/msg00734.html
  2. http://www.redhat.com/archives/fedora-test-list/2009-May/msg01028.html

Developments

In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.

Contributing Writer: Oisin Feeley

In a Flap Over Flags

This week's "frank and open exchange of views" took the (non)inclusion of country flags as its subject. A reminder was posted[1] by Kevin Fenzi of a previous FESCo decision to split flags representing geopolitical or ethnocultural concepts into separate subpackages. Tom Callaway posted[2] the history of how he had come to draft the proposal and noted that the inclusion of the Taiwan/Republic of China flag and possible consequences to the distributability of Fedora in the P.R.C. were the initial impetus. Upon request Josh Boyer provided[3] the relevant IRC log of the 2009-03-27 FESCo meeting.

Lots of discussion was had in several separate threads. FESCo was criticized repeatedly for taking the decision.

When Project Leader Paul W. Frields was pressed to comment he replied[4] that it was not his job to interfere with FESCo decisions of this sort and that he agreed with David Woodhouse's take: namely, that while disapproving of censorship, there was precedent for removing material deemed likely to offend the sensibilities of some users.

Although Bill Nottingham thought that it was absurd Toshio Kuratomi and Seth Vidal explored[5] some ideas about how YUM plugins and a new entry in the Provides namespace might enable a technical solution.

Jesse Keating outlined[6] the advantages of a "no flags" policy in gaining possible contributors from the PRC and also getting wider exposure for software in RHEL.

[[User:|Denis Leroy]] was a persistent critic of the decision and called[7] for most of FESCo to resign.

Patrice Dumas kicked off[8] a fresh instance of the thread which recast the discussion in terms of two separate issues: legality and giving offense.

Christoph Wickert started[9] a fresh instance of the thread because: "[t]he `Package Maintainers Flags policy" thread already counts more than 225 mails, but nobody bothered to answer 7 simple (?) questions I asked in my mail, although it was one of the very first three mails on the topic. So what did I do wrong? Was it that I mentioned the missing FESCo meeting minutes? If 8 out of 21 summaries are missing, IMHO this is a fact worth mentioning. I'm one of the few maintainers who directly is affected by the policy. Would somebody - preferably a FESCo member, who voted for the flags proposal - please be so kind to answer my questions. TIA!" Josh Boyer answered[10] pretty thoroughly. He included the information that the policy would be revisited in the next meeting and an explanation that the FESCo meeting summaries were incomplete due to the failure of an attempt to rotate the onerous minute taking duties. Bill Nottingham added[11] that the missing items should now be available.

Yet a further thread was started[12] by Martin Sourada as a proposal to create icon-themes as a long-term support solution.

The policy, as currently formulated is[13] posted on the wiki.

The 2009-05-22 FESCo meeting voted[14] to overturn the flag policy and to start gathering information on the actual scope of the problem. Kevin Kofler started[15] a thread to this end.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01403.html
  2. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01427.html
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01670.html
  4. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01480.html
  5. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01550.html
  6. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01582.html
  7. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01661.html
  8. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01557.html
  9. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01740.html
  10. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01743.html
  11. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01892.html
  12. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01910.html
  13. https://fedoraproject.org/wiki/Package_Maintainers_Flags_Policy
  14. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01869.html
  15. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01895.html

FESCo Election Questions

John Stanley reminded[1] everyone that nominations for five FESCo seats are open until 2009-05-29 for "[a]ny interested Fedora packager [...] the only requirement is membership in the 'packager' group in FAS."

Given the rumblings over the geopolitical flags issue (and other signs of discontent) it may be that this will be an interesting election.

The requirement to be a packager was a new one and raised[2] questions from John Poelstra and Rahul Sundaram. Jesse Keating argued[3] that FESCo was "[...] primarily concerned with the packages and distribution release side of the house." This was disputed by several commenters who referenced decisions made by FESCo which affected documentation, artwork and internationalization.

John Rose wanted to know why the voting-pool was not the same as the candidate-pool and Josh Boyer responded[4] that the issue should be raised by filing a ticket with FESCo. Andreas Thiemann and John Rose agreed[5] that there was a culture of meritocracy in the Fedora Project and John Rose observed that: "The Fedora Board and FESCo and others think of themselves as being part of a meritocracy (at least that is my perception of what they think) but at the same time are trying to encourage more widespread democratic participation which naturally runs counter to perpetuating the meritocracy."

A subsequent 2009-05-22 FESCo meeting addressed the issue of restricting its membership to packagers and ratified the current practice while leaving open the door for further discussion if need be. The meeting summary (posted[6] by Bill Nottingham) noted that no one who lacked packager status had actually expressed interest in running.

Thorsten Leemhuis asked[7] for participation in preparing questions to pose to the candidates once the nominations are closed.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01735.html
  2. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01756.html
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01768.html
  4. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01796.html
  5. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01879.html
  6. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01869.html
  7. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01507.html

Anaconda vs YUM Upgrades

A brief thread initiated by David Timms explored[1] why it has been easier to upgrade a system with anaconda rather than YUM. David referenced a suggestion that: "anaconda is cheating (ie running --nodeps installs). This would allow it to complete an upgrade where dependencies lead to unavailable packages that are not on the dvd, but are in the complete Fedora, and or non- fedora repositories, that are not available at upgrade time."

Seth Vidal replied[2] that as anaconda was running outside of the system experiencing the update it was free to use "--nodeps [without] a concern for not being able to complete the transaction." Anaconda's ability to use blacklists to exclude particular items from such transactions is now available to preupgrade as a YUM plugin.

Jeremy Katz added[3] that: "It also means that we can do things like use a newer version of rpm or a new kernel with ext4 support to (eventually) allow for migrating from ext3->ext4[.]"


  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01353.html
  2. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01360.html
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01386.html

Broken Dependencies in Fedora 12 Development

Michael Schwendt posted three lists of broken dependencies in Fedora 12 development[1][2][3].

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01866.html
  2. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01867.html
  3. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01868.html

Too Many Conflicts

Michael Schwendt reminded[1] the list that packagers were ignoring conflicts too readily.

  1. https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01917.html

Artwork

In this section, we cover the Fedora Artwork Project[1].

Contributing Writer: Nicu Buculei

  1. http://fedoraproject.org/wiki/Artwork

Goodbye Fedora-art, Welcome Fedora-design

Máirín Duffy announced[1] a major rebranding: "we are going to rebrand ourselves as the Fedora Design team rather than the Fedora Art team, both in hopes of attracting more UX designers, and also since it's a more accurate representation of the team so folks needing help with UI design will know where to go." The change involves modification in the mailing list, IRC channel, the Fedora Account System and awesome new functionality, shared file storage "This means rather than painfully uploading your work file-by-file to the wiki, you can just drag and drop files in batches to the shared directory and link to the top level or individual files from the wiki [...] This way, other folks on the design team can collaborate and upload their improvements and remixes to the same place so we don't have files for the same project all over the place."

  1. http://www.redhat.com/archives/fedora-art-list/2009-May/msg00171.html

Statistics Poster

Steven Moix asked[1] of @fedora-design about an updated statistic poster[2] "Could someone have a look at the Statistics Poster to update it to 4F standards and update it with recent statistics?", request quickly accomplished[3]Paul Frields "It was very easy to do, thanks to the way it was created -- whoever you are, thank you very much!" (as discovered later[4], it was developed by Dimitris Glezos and Máirín Duffy)

  1. http://lists.fedoraproject.org/pipermail/design-team/2009-May/000044.html
  2. http://fedoraproject.org/wiki/Marketing_statistics_poster
  3. http://lists.fedoraproject.org/pipermail/design-team/2009-May/000048.html
  4. http://lists.fedoraproject.org/pipermail/design-team/2009-May/000049.html

Fedora Weekly Webcomic

FWN-2009-05-24-the-end.png

Nicu's latest and last webcomic[1]

  1. http://nicubunu.blogspot.com/search/label/webcomic

Security Week

In this section, we highlight the security stories from the week in Fedora.

Contributing Writer: JoshBressers

Cloudy Trust?

CIO.com has a nice article that points out some of the probably flaws in cloud computing: Cloud Security: Danger (and Opportunity) Ahead. [1] In theory, cloud computing is a fine idea that has the potential to lower the cost of a CPU cycle dramatically. The thing nobody is really talking about yet is keeping your data secure. Right now, it would be rather unwise to presume that anything you send to the cloud won't be compromised in some way. Securing a highly multi-user environment such as this is going to pose a huge challenge. Problems nobody has even though of are going to emerge, and will take a great deal of cooperation and understanding to solve them. This is one of the places that Open Source style collaboration will prove to be highly useful.

  1. http://www.cio.com/article/492999/Cloud_Security_Danger_and_Opportunity_Ahead

Translation

This section covers the news surrounding the Fedora Translation (L10n) Project[1].

Contributing Writer: Runa Bhattacharjee

  1. http://fedoraproject.org/wiki/L10N

New Translations for Fedora Websites

Translations in Korean, Traditional Chinese, French, Japanese, and Russian were added for the various Fedora-website pages for the first time in Fedora 11[1].

  1. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00104.html

Zero-day Changes Made to the Release Notes

Ruediger Landmann announced[1] the zero day updates to the F11 Release Notes which in include all the issues reported by the Translation and Documentation team.

Earlier, DomingoBecker reported[2] the lack of references about the '5.2.1. Fingerprint Readers' section in the Fedora 11 Release Notes. PaulFrields suggested[3] the addition of a link to a wiki page as the reference with a mention of note for 'further information' and the note could be easily translated by reusing translations from existing sections.

  1. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00121.html
  2. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00112.html
  3. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00114.html

system-config-kdump Not Enabled for Submission

Kris Thomsen brought forward a problem[1] with the submission of the system-config-kdump package via translate.fedoraproject.org. It was later found[2] that the user account 'transif' used to submit translations via translate.fedoraproject.org had not been granted submission privileges for this module. This problem is currently in process of being resolved.

  1. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00118.html
  2. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00133.html

Sections of the Fedora Users-Guide Cannot be Translated

Daniel Cabrera reported[1] that some lines from the Fedora User Guide are missing from the .pot file and as a result these lines remain untranslated in the final document. This was caused while merging the many disparate files generated by publican[2].

  1. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00125.html
  2. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00130.html

SELinux User Guide Now Available for Translation

Scott Radvan, writer of the Fedora SELinux User Guide, announced[1] the availability of the document for translation. The disparate files have been merged together into a single .pot file, which can be downloaded. The translations for this document can be submitted via translate.fedoraproject.org[2].

  1. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00142.html
  2. https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00148.html

Security Advisories

In this section, we cover Security Advisories from fedora-package-announce.

https://www.redhat.com/mailman/listinfo/fedora-package-announce

Contributing Writer: David Nalley

Fedora 10 Security Advisories

Fedora 9 Security Advisories

Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @et-mgmnt-tools-list, @fedora-xen-list, and @libvirt-list and lists.

Contributing Writer: Dale Bewley

Fedora Virtualization List

This section contains the discussion happening on the fedora-virt list.

Rawhide Virtualization Repository

Mark McLoughlin announced[1] the launce of the virt preview repo(FWN#171[2]). "We've set up a repository for people running Fedora 11 who would like to test the rawhide/F12 virt packages. To use it, do e.g."

  $> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
  [rawvirt]
  name=Virtualization Rawhide for Fedora 11
  baseurl=http://markmc.fedorapeople.org/virt-preview/f11/$basearch/
  enabled=1
  gpgcheck=0
  EOF
  $> yum update

Adding "this is very much a work-in-progress."

Mark McLoughlin decribed[3] the different types of users consuming these packages:

  • 1) Users who want things to stay stable and who aren't necessarily expecting new features until they update to F-12 - these are people with just the updates repo enabled
  • 2) Same as (1) but who are willing to help out testing updates for the whole distro in order to catch things before they hit the people in category (1) - these people have the updates and updates-testing repos enabled
  • 3) Mostly the same as (1) or (2), but have a specific interest in testing new virt features and are willing to deal with virt regressions - these people enable the updates, updates-testing and preview repos
  • 4) People who are interested in helping with helping with F-12 development in general, not just virt - these people run rawhide

Daniel Berrange added[4] "The virt-preview repo is intended primarily as an aid to testing / early experimentation. It is not intended for 'production' deployment."

  1. http://www.redhat.com/archives/fedora-virt/2009-May/msg00074.html
  2. http://fedoraproject.org/wiki/FWN/Issue171#Virtualization_Technology_Preview_Repo
  3. http://www.redhat.com/archives/fedora-virt/2009-May/msg00086.html
  4. http://www.redhat.com/archives/fedora-virt/2009-May/msg00081.html

No libguestfs on Fedora 10

Ján ONDREJ referenced[1] FWN[2] when asking if Richard Jones would consider including Package-x-generic-16.pngqemu-0.10 into Package-x-generic-16.pnglibguestfs package to satisfy dependencies for Fedora 10.

Richard "had a go at backporting the changes to qemu that we ship in F-10. qemu in F-10 is based on qemu 0.9, and doesn't include the vmchannel patch." But "ended up with a qemu which compiled, but kept segfaulting, and it was tricky to diagnose exactly why."

"Is it really a problem to use the libguestfs[3] and/or qemu[4] packages from Fedora 11 builds? You can grab the latest builds out of Koji." "This worked OK for me, although I have now moved to using Fedora 11-Preview, and have mostly abandoned Fedora 10."

Daniel B and Mark Mc concurred, Fedora 11 is the place to get libguestfs .

  1. http://www.redhat.com/archives/fedora-virt/2009-May/msg00064.html
  2. http://fedoraproject.org/wiki/FWN/Issue175#libguestfs_on_non-Fedora_Platforms
  3. http://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=libguestfs
  4. http://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=qemu

New Release virt-inspector

Richard Jones announced[1] "the first 'really working' version of virt-inspector[2]."

"This is a tool based around libguestfs which can inspect a virtual machine disk image and tell you some interesting things about what's inside it."

Some of the things virt-inspector can tell you:

  • What operating system(s) are installed, and what distros and versions. It currently covers RHEL releases, Fedora releases, Debian releases, and has limited support for Windows.
  • How disk partitions are expected to be mounted (eg. /dev/sda1 -> /boot)
  • What applications are installed.
  • What kernel(s) are installed.
  • What kernel modules are installed.
  1. http://www.redhat.com/archives/fedora-virt/2009-May/msg00073.html
  2. http://git.et.redhat.com/?p=libguestfs.git;a=summary

Fedora Xen List

This section contains the discussion happening on the fedora-xen list.

Xen 3.4.0 Released

Pasi Kärkkäinen forwarded[1] an announcement from the Xen list.

"This release contains a number of important new features and updates including:

  • Device passthrough improvements, with particular emphasis on support for client devices (further support is available as part of the XCI project[2])
  • RAS[3] features: cpu and memory offlining
  • Power management - improved frequency/voltage controls and deep-sleep support. Scheduler and timers optimised for peak power savings.
  • Support for the Viridian (Hyper-V) enlightenment interface
  • Many other x86 and ia64 enhancements and fixes

Fedora 11 includes Package-x-generic-16.pngXen version 3.3.1.

  1. http://www.redhat.com/archives/fedora-xen/2009-May/msg00014.html
  2. http://xenbits.xensource.com/xenclient/
  3. http://en.wikipedia.org/wiki/Reliability,_Availability_and_Serviceability

Libvirt List

This section contains the discussion happening on the libvir-list.

Libvirt VMWare ESX Driver In Development

Matthias Bolte announced[1] "a project of the Paderborn Center for Parallel Computing"[2] having "a subgoal is to extend the driver base of Package-x-generic-16.pnglibvirt. We've started an VMware ESX driver and are investigating Hyper-V support."

"The ESX driver isn't complete yet, currently it supports:"

  • domain lookup by ID, UUID and name
  • domain listing
  • domain suspend and resume
  • domain reboot, if the VMware tools are installed inside the domain
  • domain start and shutdown
  • domain migration

"We think this code might be useful for others and would be glad if the driver could be merged into libvirt in medium term." Matthias was met with enthusiasm from the core libvirt developers.

  1. http://www.redhat.com/archives/libvir-list/2009-May/msg00431.html
  2. http://pc2.uni-paderborn.de