January 2009 - announce - Fedora Mailing-Lists

Unofficial Fedora FAQ Update: 2009-01-30

by Max Kanat-Alexander

Hi Fedora Users! I've updated the Unofficial Fedora FAQ today. As always, you can find the FAQ at: http://www.fedorafaq.org/ Here's what's changed since the last time I sent out an update: * The ATI question has been updated to reflect that there are now working 3D drivers for Fedora 10. * Some people experience sound cracking or popping on their machines. I've added instructions on what to do about it. * Fixed the Flash instructions. * Fixed the instructions for installing Windows fonts. * Two new translations: German and Portuguese. * The site's layout and style has changed--let me know what you think. Let me know if you have any thoughts or feedback! I'm also always interested if there are other frequently-asked questions that the FAQ should be dealing with, so let me know! To see how to contribute to the FAQ, look at: http://www.fedorafaq.org/contribute/ I'd particularly like some new translations, also! If you'd be interested in translating the FAQ to your language, just let me know by sending me an email! (Remove the "_list" in the address I'm sending this message from.) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

14 years, 4 months

1
0
0 / 0

Re: Reminder: Fedora Board IRC meeting 1900 UTC 2009-02-03

by Paul W. Frields

** Changed subject line to reflect proper date. ** On Thu, Jan 29, 2009 at 2:46 PM, Paul W. Frields <stickster(a)gmail.com> wrote: > The Board is holding its monthly public meeting on Tuesday, 3 February > 2009, at 1900 UTC on IRC Freenode. The Board has settled on a > schedule that puts these public IRC meetings on the first Tuesday of > each month. Therefore, the next following public meeting will be on 3 > March 2009. For these meetings, the public is invited to do the > following: > > * Join #fedora-board-meeting to see the Board's conversation. This > channel is read-only for non-Board members. > > * Join #fedora-board-public to discuss topics and post questions. This > channel is read/write for everyone. > > The moderator will direct questions from the #fedora-board-public > channel to the Board members at #fedora-board-meeting. This should > limit confusion and ensure our logs are useful to everyone. > > We look forward to seeing you at the meeting. > > -- > 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 >

14 years, 4 months

1
0
0 / 0

Reminder: Fedora Board IRC meeting 1900 UTC 2009-01-06

by Paul W. Frields

The Board is holding its monthly public meeting on Tuesday, 3 February 2009, at 1900 UTC on IRC Freenode. The Board has settled on a schedule that puts these public IRC meetings on the first Tuesday of each month. Therefore, the next following public meeting will be on 3 March 2009. For these meetings, the public is invited to do the following: * Join #fedora-board-meeting to see the Board's conversation. This channel is read-only for non-Board members. * Join #fedora-board-public to discuss topics and post questions. This channel is read/write for everyone. The moderator will direct questions from the #fedora-board-public channel to the Board members at #fedora-board-meeting. This should limit confusion and ensure our logs are useful to everyone. We look forward to seeing you at the meeting. -- 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

14 years, 4 months

1
0
0 / 0

Fedora Weekly News #160

by Oisin Feeley

Fedora Weekly News Issue 160 Welcome to Fedora Weekly News Issue 160 for the week ending January 25th, 2009. http://fedoraproject.org/wiki/FWN/Issue160 Announcements notes upcoming events and deadlines for Fedora 11. PlanetFedora picks up on some communication problems in "General" and shares "How To" information on disabling the system bell. Developments rounds up some "Fedora 11 Release Activity" and synopsizes the debate around a "Minimalist Root Login to X?". Infrastructure is back with some essential information on "Fedora Security Policy". Artwork shares the "Fedora 11 Release Banner". SecurityAdvisories provides a handy list of essential updates. Virtualization explains "QEMU VM Channel Support". We are pleased to have an AskFedora Q&A covering the advisability of using the "Ext4 Filesystem on Solid State Disks". Keep sending your questions! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. We welcome reader feedback: fedora-news-list(a)redhat.com FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [1] http://fedoraproject.org/wiki/NewsProject/Join == Table of Contents == 1.1 Announcements 1.1.1 Technical Announcements 1.1.2 Fedora 11 1.1.3 Upcoming Events 1.2 Planet Fedora 1.2.1 General 1.2.2 How-To 1.2.3 Events 1.3 Developments 1.3.1 NFS Mounts and Caching DNS Nameserver Problem 1.3.2 Fedora 11 Alpha Release Activities 1.3.3 Minimalist Root Login to X ? 1.3.4 Fedora Geo Spin for USB Key and LiveCD 1.3.5 Draft Guidelines for Approving provenpackagers 1.3.6 Cloning of Bug Reports ? 1.4 Infrastructure 1.4.1 Why Puppet uses config instead of configs 1.4.2 Fedora Security Policy 1.4.3 Alpha Release Readiness 1.5 Artwork 1.5.1 Fedora 11 Release Banner 1.5.2 Artwork for the Education SIG 1.5.3 Wallpaper Survey 1.6 Security Advisories 1.6.1 Fedora 10 Security Advisories 1.6.2 Fedora 9 Security Advisories 1.7 Virtualization 1.7.1 Enterprise Management Tools List 1.7.1.1 Improved Device Configuration Support in virt-manager 1.7.2 Fedora Virtualization List 1.7.2.1 Fedora 11 Virtualization Features 1.7.2.2 Weekly Status Report 1.7.2.3 New Virtualization Wiki Pages 1.7.3 Libvirt List 1.7.3.1 QEMU VM Channel Support 1.8 Ask Fedora 1.8.1 Ext4 Filesystem on Solid State Disks == Announcements == In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack === Technical Announcements === John Palmieri (on behalf of Luke Macken and Mairin Duffy) announced[1] the Moksha Project and the Fedora Community Project[2]. They have been consolidating "the Fedora Infrastructure bits under one unified user interface", and have "decided to split the efforts into two projects." "Moksha is a platform for creating real-time collaborative web applications. It provides a set of Python and JavaScript API's that make it simple to create rich applications that can acquire, manipulate, and visualize data from external services." "Fedora Community aims at being a portal interface for Fedora Project members to collaborate within and find information about the diverse Fedora universe. It is created from applications built on top of the Moksha platform. Fedora Community is assembled from a wide-ranging set of modules that integrates existing Fedora Infrastructure components such as koji, bodhi, FAS, and PkgDB." [1] http://www.redhat.com/archives/fedora-announce-list/2009-January/msg00015... [2] http://johnp.fedorapeople.org/fedora-community/ Tom "Spot" Callaway announced[1] that the Fedora Packaging Committee has made some changes to the packaging guidelines. For details, read the full announcement linked below. [1] http://www.redhat.com/archives/fedora-devel-announce/2009-January/msg0000... === Fedora 11 === The Fedora 11 Alpha freeze has passed[1], and "we still have a few feature pages in need of an update. Several have not been updated for a month or more," according to John Poelstra. If these pages are not updated by January 28th, FESCo will be asked to drop the features from Fedora 11. [1] http://www.redhat.com/archives/fedora-devel-announce/2009-January/msg0000... === Upcoming Events === Fedora will have a presence at several events in the next few weeks. Feel free to join us, February 6 - 8: Free and Open Source Developers European Meeting (FOSDEM) February 20 - 22: Southern California Linux Expo (SCALE) Also, people are encouraged to register for Fedora or JBoss.org related speaking slots at LinuxTag 2009. [1] https://fedoraproject.org/wiki/FedoraEvents/FOSDEM/FOSDEM2009 [2] https://fedoraproject.org/wiki/SCALE7X_Event [3] https://fedoraproject.org/wiki/Fedora_Activity_Day_at_SCaLE_7x [4] https://fedoraproject.org/wiki/LinuxTag_2009_talks == Planet Fedora == In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin === General === Thorsten Leemhuis expressed[1] some concern over important communication and decisions taking place over synchronous/real-time mediums (like IRC or conferences like FUDcon) without the ability for people unable to attend to participate. Michael DeHaan agreed[2] and used a personal example of trying to maintain software that runs on EL-4 through Fedora 11 to explain the importance. "I have to use the old libraries and mostly only get to see new releases as things that break API compatibility or bring new bugs...I care about the environment more than the technology." Michael continued, "While many developers see Fedora is about technology, as a mostly "upstream" guy, the joy I find in it is really just about collaboration and working with people all over the globe." Jef Spaleta continued[3] a disagreement with Mark Shuttleworth over the fact that Canonical has yet to open source some of the community-related components of Launchpad. Dave Jones mentioned[4] an upcoming change to the p4-clockmod driver. "It no longer exports a cpufreq interface to sysfs. This will no doubt have some people complaining that they can no longer change their CPU frequency. The thing is, they never could." He then explains why such a feature ever existed. Harish Pillay compared[5] the new White House[6] website copyright policy with that of a number of nations. Sebastian Dziallas and the Fedora Education SIG[7] announced[8] the preview of an unbranded Education Remix. "As this is still based on F10, the main purpose is to gather feedback concerning the spin for F11." Michael DeHaan wrote[9] about some of the advancements being made in order to support the provisioning of large datacenters and large-scale virtualization setups under Fedora. Máirín Duffy showed off[10] some new mockups of screens for the Fedora Community Project[11]. [1] http://thorstenl.blogspot.com/2009/01/communication-is-important.html [2] http://www.michaeldehaan.net/?p=825 [3] http://jspaleta.livejournal.com/33352.html [4] http://www.codemonkey.org.uk/2009/01/18/forthcoming-p4clockmod/ [5] http://harishpillay.livejournal.com/135485.html [6] http://www.whitehouse.gov/ [7] https://fedoraproject.org/wiki/SIGs/Education [8] http://sdziallas.joyeurs.com/blog/2009/01/fedora-edu-a-remix-and-more-to.... [9] http://www.michaeldehaan.net/?p=830 [10] http://mihmo.livejournal.com/68603.html [11] http://johnp.fedorapeople.org/fedora-community/ === How-To === James Morris explained[1] how to work around an issue where MacBooks have trouble talking to projectors over the VGA output. John Poelstra started[2] an interesting thread[3,4,5,6,7,8] (only some of which was serious) about disabling the system bell. Who knew that such an ancient component (a relic of computers from decades ago when soundcards had yet to be invented) could be so interesting? Tom Waugh described[9] how to transfer e-mail and addresses from Evolution to Thunderbird [1] http://james-morris.livejournal.com/38392.html [2] http://poelcat.wordpress.com/2009/01/22/disabling-the-fedora-10-system-bell/ [3] http://marilyn.frields.org:8080/~paul/wordpress/?p=1429 [4] http://kanarip.livejournal.com/8662.html [5] http://thecodergeek.com/post/84 [6] http://www.chruz.com/2009/01/25/pcspkr-be-gone/ [7] http://skvidal.wordpress.com/2009/01/25/speaker/ [8] http://jwboyer.livejournal.com/29470.html [9] http://cyberelk.net/tim/2009/01/24/switching-mail-clients/ === Events === Fedora Infinity Day 2009, at Presidency University, Dhaka[1] Lots of videos[2,3] of various Fedora and Red Hat events [1] http://angel.linux.org.bd/?p=8 [2] http://domsch.com/blog/?p=27 [3] http://marilyn.frields.org:8080/~paul/wordpress/?p=1421 == Developments == In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley === NFS Mounts and Caching DNS Nameserver Problem === An update on problems with NFS mounts was posted[1] by Warren Togami. It was decided that nfs-utils will revert to its pre 2009-01-14 behavior. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01242.html === Fedora 11 Alpha Release Activities === There was a flurry of activity related to the Fedora 11 Alpha release (scheduled[1] for 2009-02-03). Denis Leroy inquired[2] on 2009-01-21 what had happened to the freeze, originally scheduled for the previous day, and whether all builds in rawhide were queued until after the freeze. Mamoru Tasaka responded[3] with a link to Jesse Keating's explanation[4] that the freeze is a non-blocking freeze which allows targeted fixes to be made. Tom Lane wanted[5] an "all-clear signal that the alpha tag has been made and we can go back to breaking rawhide ;-)" Jesse created [6] the alpha tag and apologized for slacking on it. He suggested that if many dependencies were going to be broken by Tom's mysql-5.1 push that Tom should ask for a koji tag specifically to land it and build all the deps for it before moving it into rawhide itself.Josh Boyer demonstrated[7] how the Koji command-line can be used to answer queries about what tags are present: $koji list-tags | grep f11-alpha $koji list-tag-inheritance f11-alpha Rahul Sundaram requested[8] that knowledgeable folks would help build the Release Notes[9] for Fedora 11 by adding relevant information to the wiki. After Rahul got the ball rolling, with some information on the use of ext4 as the default filesystem, the experimental provision of the btrfs filesystem and more, Richard W.M. Jones added information on the MinGW windows cross-compiler and Todd Zullinger added information about git-1.6. The 2009-01-23 Rawhide Report[10] contained some large lists of broken dependencies which were pounced on by the respective developers. As the majority were due to the new MySQL mentioned above Jesse Keating asked[11] why his advice to use a special tag had been ignored. Tom Lane replied that there had been no objections when he mooted the idea a week ago and that a non-standard tag would cause more work for affected developers than the current rebuilds. Jesse re-iterated[12] his request to "[p]lease consider using it in the future if you're going to break such a wide array of packages." Richard W.M. Jones reported[13] problems using yum on Rawhide. Tom London suggested and Richard W.M. Jones confirmed[14] that reverting to sqlite-3.6.7-1.fc11.x86.64 fixed the problems. It transpired[15] that there was indeed an SQLite bug which was quickly fixed by Panu Matilainen. [1] https://fedoraproject.org/wiki/Releases/11/Schedule [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01275.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01276.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00664.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01298.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01348.html [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01299.html [8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01511.html [9] https://fedoraproject.org/wiki/Fedora_11_Alpha_release_notes [10] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01510.html [11] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01510.html [12] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01533.html [13] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01464.html [14] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01485.html [15] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01483.html === Minimalist Root Login to X ? === Warren Togami suggested[1] "mak[ing] root logins from GDM a stripped down desktop with only a terminal and a menu with only configuration tools [and making the desktop] ugly and with a very obvious note explaining why [users] shouldn't be logged in as root." "Nodata" was among those who wondered[2] if Warren's use cases "[...] where /home filesystem is full and logins fail, or /home is remote and inaccessible[...]" were anything other than odd edge cases. Jeff Spaleta and Chris Adams expanded[3] upon this line of thought: "[...] if /home is full, can users really not log in? If that is the case, that's broke and should be fixed. The user should be able to log in and remove files." The impetus for this discussion may have been another thread which asserted that the denial of root login via GDM on Fedora 10 systems made it too difficult to maintain said systems. The thread yielded[4] good examples by Jud Craft and Dave Airlie[5] of arguments that such modifications merely penalized experienced users and failed to enhance security as the users could just login as root on the console anyway. As an aside Benjamin LaHaise brought up the issue that Ctrl+Alt+F2 no longer worked. DanHorák explained[6] that "F2-6 are blocked when you have getty running on vt1 (/etc/event.d/tty1 is the same tty[2-6]) and Xorg server runs on vt1 too (gdm runs with --force-active-vt) Then there are messages like `unable to switch vt' in /var/log/Xorg.log. [Such behavior] requires manual editing of at least /etc/event.d/tty1, it should not happen in default setups." Nicolas Mailhot suggested[7] an imperfect upgrade as another possible cause. A further nugget of information revealed in the thread was as Fedora 10 had implemented hiddenmenu as a default in grub it was best to hold down any key once the BIOS had finished the POST routine. Jesse Keating suggested[8] the shift key as it typically had no bindings either in BIOS or grub. Andrew Haley pointed out[9] that many of the recent changes were breaking established use patterns. Kevin Kofler and Christopher Wickert suggested[10][11] that anyone who wished to revert to the previous status should just edit /etc/pam.d/gdm to comment out auth required pam_succeed_if.so user != root quiet Back in the later thread which sought to deal with some of the difficulties raised above Tom `spot' Callaway suggested: "A `Rescue Mode' in GDM which goes to a root session with minimal apps, marked as "Rescue Mode", rather than a root X login (even though it does need root credentials)." Lyos Gemini Norezel preferred[12] that "[...] the root login should use the user selected interface (gnome, kde, xfce, etc)" but Matthew Woehlke emphasized[13] the maintenance benefits of choosing a single Desktop Environment and forcing that as the safe root login. Variations on this topic have been covered previously in FWN#133[14] and FWN#103[15] [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01387.html [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01542.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01547.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01300.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01335.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01399.html [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01398.html [8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01455.html [9] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01408.html [10] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01278.html [11] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01291.html [12] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01493.html [13] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01495.html [14] http://fedoraproject.org/wiki/FWN/Issue133#Running_As_Root [15] http://fedoraproject.org/wiki/FWN/Issue103#Root_Login_And_Display_Manager... === Fedora Geo Spin for USB Key and LiveCD === Yaakov Nemoy announced[1] a "[...] respin of Fedora with packages for doing OSM[0] 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 cono/guring user computers to do mapping. The USB stick can then be brought home, and the user can continue doing mapping there." [0] Open Street Mapping http://en.wikipedia.org/wiki/OpenStreetMap [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01155.html === Draft Guidelines for Approving provenpackagers === Jesse Keating drafted[1] a definition of `provenpackager' (see FWN#151[2)]. Alex Lancaster was worried[3] that too many hoops would mean that maintainers such as himself would lose motivation to continue their work. As a subsidiary concern Alex was worried that there were still some packages not being opened up. KevinKofler assured Alex that he would become a `provenpackager' based up his sterling work and Jesse confirmed[4][5] that this redefinition and re-seeding of the `provenpackager' group was in part to address such concerns. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01573.html [2] http://fedoraproject.org/wiki/FWN/Issue151#Security_Exceptions_to_the_Mas... [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01620.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01629.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01628.html === Cloning of Bug Reports ? === Jóhann B. Guðmundsson asked[1] for input, in the form of suggestions and votes, as to whether Bug Hunters (which later seemed to mean testers, but not triagers) should file a separate bug entry for each of: past supported release, current release and rawhide or just annotate a bug for one of the former with a note that it was present in the others. There was general agreement that mailing list votes were ineffective and unwanted. Kevin Kofler objected[2] to the tack taken by Jóhann which seemed to assume an authority over a decision which would affect not just QA, testing and triage teams but also packagers and maintainers. It appeared[3] that the matter would be elevated to FESCo for a decision but as of going to press this had not happened. Mark McLoughlin suggested[4] a more flexible policy and warned that "[...] you can be sure you'll have maintainers who haven't read or replied to this thread waking up and getting annoyed that they've 3x bug reports to deal with :-)" Jesse Keating argued[5] that the multiple bug-entry option was preferable on four heads: 1) that bugs may have different causes in their releases; 2) users of past releases will not be helped by closing bugs on rawhide; 3) bodhi updates are not pushed at the same time; 4) maintainers are the only people with the knowledge to make such a call. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/thread.htm... [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01423.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01490.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01442.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01342.html == Infrastructure == This section contains the discussion happening on the fedora-infrastructure-list http://fedoraproject.org/wiki/Infrastructure Contributing Writer: Huzaifa Sidhpurwala === Why Puppet Uses config Instead of configs === susmit shannigrahi asked[1] on the @fedora-infrastructure-list asked why, in the fedora-infrastructure implementation of puppet when we add a new file, in the .pp file the path is written as puppet:///config where as the actual path of the file is in the configs directory. To this Jeroen van Meeuwen answered [2] by saying that the [config] fileserver mount may point to /path/to/configs which may allow this discrepancy to exist. [1] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... [2] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... === Fedora Security Policy === Mike McGrath wrote[3] on the @fedora-infrastructure-list about the proposed Fedora Security Policy. Mike asked that he would like everyone in the sysadmin-* group to be compliant with this policy. On this thread several people commented about changes they would propose in iptables[4] & [5] [3] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... [4] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... [5] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... === Alpha Release Readiness === John Poelstra wrote [6] on the @fedora-infrastructure-list about the Alpha Release Readiness meeting on the 3rd Feb 2009. Mike McGrath replied[7] that he will be attending the meeting on the behalf of the Infrastructure team. [6] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... [7] https://www.redhat.com/archives/fedora-infrastructure-list/2009-January/m... == Artwork == In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei === Fedora 11 Release Banner === With the Alpha release of the upcoming Fedora 11 approaching fast, Paolo Leoni created[1] a banner[2] to be used on various websites for the announcement "Since we are still in a initial session for the official F11 theme, I've used a simple image to point the birth of a new fedora version". [1] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00061.html [2] http://pleoni.altervista.org/fedora11-banner-alpha5c.png === Artwork for the Education SIG === Following a request[1] from Sebastian Dziallas for updated graphics for the Education SIG, Maria Leandro posted[2] a couple of very cute graphics, with one of them[3] being the favorite of the team. She still to add some improvements, incorporating the feedback received. [1] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00070.html [2] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00080.html [3] http://tatica.fedorapeople.org/EduSig/thumb_wallpaper3.jpg === Wallpaper Survey === Máirín Duffy reported[1] on @fedora-art about the results of an informal survey she ran on her blog[2] about the wallpapers used by various people "So far as I've been able to read through them, they seem to fit into 3 categories: #1 stick with the default (distro default or desktop env default) or flat solid color #2 personalized no matter what (photos they took themselves or photos of family members) or a photo of an interest hobby (racecars, bikes, hometown, etc) #3 beautiful pictures of nature, usually with some depth". Máirín is trying to use this data so the Art Team can come with more useful wallpapers "we should think about these wallpapers that folks are actually using and try to create something that they will like having as their desktop background as much as possible". [1] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00088.html [2] http://mihmo.livejournal.com/68292.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 === * mumbles-0.4-9.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * moodle-1.9.3-5.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * uw-imap-2007e-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * DevIL-1.7.5-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * ntp-4.2.4p6-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * nessus-libraries-2.2.11-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * libnasl-2.2.11-3.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * nessus-core-2.2.11-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * tor-0.2.0.33-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... === Fedora 9 Security Advisories === * amarok-1.4.10-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * moodle-1.9.3-5.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * DevIL-1.7.5-2.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * uw-imap-2007e-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * ntp-4.2.4p6-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * tor-0.2.0.33-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * libnasl-2.2.11-3.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * nessus-core-2.2.11-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * nessus-libraries-2.2.11-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... == Virtualization == In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley === Enterprise Management Tools List === This section contains the discussion happening on the et-mgmt-tools list ==== Improved Device Configuration Support in virt-manager ==== Cole Robinson posted several device related enhancements to image:Echo-package-16px.pngvirt-manager including: * Support[1] for listing, viewing details of, and removing VM hostdev[2] devices * Add hardware wizard[3] for sound devices * Support[4] for specifing the model[5] when adding a network device [1] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00039.html [2] http://www.libvirt.org/formatdomain.html#elementsUSB [3] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00033.html [4] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00032.html [5] http://www.libvirt.org/formatdomain.html#elementsNICSModel === Fedora Virtualization List === This section contains the discussion happening on the fedora-virt list. ==== Fedora 11 Virtualization Features ==== Mark McLoughlin announced[1] the virtualization features in development for Fedora 11. * VirtVNCAuth Define a mapping of SASL authentication into the VNC protocol, and implement it for QEMU and GTK-VNC, providing strongly authenticated, securely encrypted remote access of virtual guest consoles. * KVM PCI Device Assignment Assign PCI devices from your KVM host machine to guest virtual machines. A common example is assigning a network card to a guest. * KVM and QEMU Merge Combine the image:Echo-package-16px.pngkvm and image:Echo-package-16px.pngqemu packages into a single package. [1] http://www.redhat.com/archives/fedora-virt/2009-January/msg00024.html ==== Weekly Status Report ==== Mark McLoughlin "started sending out a 'Fedora Virtualization status report' to folks at Red Hat to keep people informed about what's going on." Mark also forwarded[1] the report to @fedora-virt. The report identified 186 open bugs, and included information for effectively monitoring the package commits on the @fedora-virt-main[2] list. [1] http://www.redhat.com/archives/fedora-virt/2009-January/msg00037.html [2] http://www.redhat.com/mailman/listinfo/fedora-virt-maint/ ==== New Virtualization Wiki Pages ==== Mark McLoughlin has been busy revising[1] existing, creating new, and archiving[2] old Fedora Virtualization wiki pages. You can help[3]. [1] http://fedoraproject.org/wiki/Category:Virtualization [2] http://fedoraproject.org/wiki/Category:Virtualization_archive [3] http://fedoraproject.org/wiki/Help:Editing#Gaining_Edit_Access === Libvirt List === This section contains the discussion happening on the libvir-list. ==== QEMU VM Channel Support ==== Richard W.M. Jones proposed[1] adding support for image:Echo-package-16px.pngqemu vmchannels to image:Echo-package-16px.pnglibvirt. A vmchannel is a "communication channel between [a VM] host and various agents that are running inside a VM guest."[2] Richard did note that "One problem is that it is qemu/kvm-only." As far as Daniel P. Berrange knew[3] "this support is not yet merged in upstream QEMU and the syntax is still being debated." This made Daniel "wary of committing to support it in libvirt" at this time. The fact that it is a feature only for QEMU did not concern Daniel, saying "I've no problem adding vmchannel support to libvirt even if its only [implemented] for QEMU/KVM. If applications/users of it find that they really badly need it for image:Echo-package-16px.pngxen too, then someone will step up to [implement] it." [1] http://www.redhat.com/archives/libvir-list/2009-January/msg00446.html [2] http://kerneltrap.org/mailarchive/linux-kvm/2008/12/14/4413984 [3] http://www.redhat.com/archives/libvir-list/2009-January/msg00448.html == Ask Fedora == In this section, we answer general questions from Fedora community. Send your questions to askfedora AT fedoraproject.org and Fedora News Team will bring you answers from the Fedora Developers and Contributors to selected number of questions every week as part of our weekly news report. Please indicate if you do not wish your name and/or email address to be published. http://fedoraproject.org/wiki/AskFedora === Ext4 Filesystem on Solid State Disks === A question on Ext4, that has already been made the default in the development tree headed for Fedora 11 was answered by Eric Sandeen, Red Hat ext4 and XFS filesytems developer. Contributing Writer: Eric Sandeen Francesco Frassinelli wrote: "I've read that in F11 ext4 will be the default filesystem. What about ext4 on solid state disk? Many websites and bloggers say that it's better to use ext2 because of the journaling, but in some kind of operation (like applying upgrades) it's sooo slow. Could we'll use ext4 on our ssd without compromising their life? TBH I haven't tested ext4 on ssd yet, though we do have some in the lab, I just haven't done it." Eric Sandeen replied: "By default ext4 still journals pretty much the same as ext3 does, so if you want to minimize writes to your flash, it should not be significantly better than ext3 in that respect. However, there is a patch to ext4 (merged soon if not already) to allow it to run in a no-journal mode, so that may be a good option." Thorsten Leemhuis added: "FYI, it was merged[1] for 2.6.29" [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit... -- Oisin Feeley http://fedoraproject.org/wiki/OisinFeeley

14 years, 4 months

1
0
0 / 0

Announcing the Moksha Project and Fedora Community Project!

by John (J5) Palmieri

We are pleased to announce the Moksha Project and Fedora Community Project. For a while now, Luke Macken, Máirín Duffy, myself and others have been working on consolidating the the Fedora Infrastructure bits under one unified user interface. We have decided to split the efforts into two projects. * Moksha - a generic platform for creating live collaborative web applications * Fedora Community - a website portal built on top of the Moksha platform What is Moksha? Moksha is a platform for creating real-time collaborative web applications. It provides a set of Python and JavaScript API's that make it simple to create rich applications that can acquire, manipulate, and visualize data from external services. It is a unified framework build using the best available open source technologies such as TurboGears2, jQuery, AMQP, and Orbited. More information can be found on the Moksha Project Page at http://moksha.fedorahosted.org What is Fedora Community? Fedora Community aims at being a portal interface for Fedora Project members to collaborate within and find information about the diverse Fedora universe. It is created from applications built on top of the Moksha platform. Fedora Community is assembled from a wide-ranging set of modules that integrates existing Fedora Infrastructure components such as koji, bodhi, FAS, and PkgDB. More information and an example of the interface can be found at the Fedora Community project page http://johnp.fedorapeople.org/fedora-community/ . Timeline Moksha's base functionality is scheduled for completion by the beginning of February. Our focus will then shift toward integration and polish to deliver the Fedora Community website in March. Getting Involved Weekly Meetings - We will be having public meetings every Monday morning at 10am EST (1500 UTC) where we go over the last week's progress and the current week's goals. Anyone is welcome to join and take on action items. The meetings will be broadcast over Fedora Talk. If you are a Fedora Talk user with a soft/voip phone, you can join the conference via 2001(a)fedoraproject.org or infrastructure(a)fedoraproject.org. If you wish to dial in via a normal telephone, choose one of these local numbers: * 919-424-0063 - Raleigh, NC * 312-577-0052 - Chicago, IL * 978-303-8021 - Westford, MA * 650-930-9514 - Sunnyvale, CA * 442030518327 - UK The conference call extension is 2001. irc - #moksha on irc.freenode.net mailing list - https://fedorahosted.org/mailman/listinfo/moksha Since at this point Moksha and Fedora Community development are pretty much intertwined, Fedora Community will be using the Moksha irc channel and mailing list. At some point in the future we may wish to create a new irc channel and mailing list for Fedora Community efforts. Resources Moksha Project Page - http://lmacken.fedorapeople.org/moksha/ Moksha Trac - https://fedorahosted.org/moksha/ Fedora Community Project Page - http://johnp.fedorapeople.org/fedora-community/ MyFedora Trac - https://fedorahosted.org/myfedora/ MyFedora Wiki - https://fedoraproject.org/wiki/MyFedora TurboGears 2 - http://turbogears.org/2.0/docs/index.html jQuery - http://jquery.org/ AMQP - http://amqp.org Orbited - http://orbited.org -- John (J5) Palmieri

14 years, 4 months

1
0
0 / 0

Fedora Weekly News #159

by Pascal Calarco

Welcome to Fedora Weekly News Issue 159 for the week ending January 19th, 2009. http://fedoraproject.org/wiki/FWN/Issue159 This week's issue reveals the code name for Fedora 11 and provides coverage from the latest FUDCon in announcements. News abounds from around Fedora Planet, including musings on the reduction of the OLPC dev team, thoughts on what it means to contribute to Fedora from several contributors, and much more. Development reports on several discussions from the recent FUDCon on the possible future of comps.xml, new packages to Rawhide coming, and more. More depth of discussion on the need for a Fedora Project CMS is offered in the Docs beat, and Translations has lots more to report on new members of various internationalization teams. The Art beat has a wonderful in-depth look at approaches for themes for Fedora 11, and security advisories brings us up to date with recent updates there. We complete the issue with news from virtualization developments, including two items regarding sVirt, a project to add security labeling support to Linux-based virtualization, and other focused discussions with libvirt. Enjoy! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. We welcome reader feedback: fedora-news-list(a)redhat.com FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [1] http://fedoraproject.org/wiki/NewsProject/Join -- Announcements -- In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack --- Fedora 11 Release Name --- At FUDCon Boston, Paul Frields announced that "Leonidas" had won the vote, and will be the code name of Fedora 11. There was much screaming and yelling, and reciting of lines from "The 300"[0]. [0] http://www.redhat.com/archives/fedora-devel-announce/2009-January/msg0000... --- FUDCon Boston --- FUDCon Boston was a great success[1]. Not only are many videos from the sessions available on the Fedora Wiki, but there is also a collection of blog posts from various attendees[2]. [1] http://www.redhat.com/archives/fedora-announce-list/2009-January/msg00013... [2] https://fedoraproject.org/wiki/FUDCon:FUDConF11_blogs --- Technical Announcements --- Jon Stanley announced[3] that he and Dennis Gilmore "are beginning an effort to migrate fedora-* redhat com to lists.fedoraproject.org." There are several benefits to this move, including greater control of the Fedora lists, a stronger Fedora identity (@lists.fedoraproject.org as opposed to @redhat.com), and the ability to be more responsive to community requests. [3] http://www.redhat.com/archives/fedora-announce-list/2009-January/msg00012... Jesse Keating announced[4] that on January 20th, "we will be doing a non-blocking freeze of Rawhide to be the basis of Fedora 11 Alpha. Only targeted fixes will be pulled into the Alpha tag after the freeze. Rawhide itself will continue on as to not disrupt development." [4] http://www.redhat.com/archives/fedora-devel-announce/2009-January/msg0000... --- Upcoming Events --- Fedora will have a presence at several events in the next few weeks. Feel free to join us, February 6 - 8: Free and Open Source Developers European Meeting (FOSDEM)[5] February 20 - 22: Southern California Linux Expo (SCALE)[6] Also, people are encouraged to register for Fedora or JBoss.org related speaking slots at LinuxTag 2009[7]. [5] https://fedoraproject.org/wiki/FedoraEvents/FOSDEM/FOSDEM2009 [6] https://fedoraproject.org/wiki/SCALE7X_Event [7] https://fedoraproject.org/wiki/LinuxTag_2009_talks -- Planet Fedora -- In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin --- General --- Marc F Ferguson expounded[0] upon the wonders of "Being a Part of Something Bigger" by joining the Fedora Project and switching to Linux! While there are lots of positive posts out there, this one captures the positive feeling that a lot of folks have by joining a project like Fedora. Andrew Overholt appealed[1] for anyone interested in helping get JBoss AS 5.0 into Fedora. Karsten Wade wrote[2] about some of the issues and concerns involved with picking a CMS for Fedora. Abhishek Rane posted[3] some nice screenshots of Amarok 2.0.1.1 (as well as a download link for Fedora 10). Jef Spaleta continued[4] his across-the-intertubes discussion with Mark Shuttleworth about Canonical's Launchpad being closed source, and talked about his motivations behind contributing to Fedora: "I have never received a paycheck from Red Hat in any capacity...Making sure companies which proclaim to be open source advocates are actually ‘walking the walk’ is on my personal agenda." In another post, Jef added[5] the statistic "2 out of the top 3 'ideas' on Ubuntu's brainstorm this week are requests to take features from the Fedora Feature process for Fedora 10 and port them to Ubuntu". He continued[6] by showing that Soyuz (a component of Launchpad that Canonical has not open sourced) has a much higher number of open bugs than other components. Along a similar line of thought, he discussed[7] in more general terms, "How important is opening sourcing in the cloud?" Greg DeKoenigsberg mused[8] about the loss of most of the OLPC software development team and what that means for OLPC, Sugar and Fedora. Jesus Rodriguez announced[9] that Spacewalk 0.4 ("an open source Linux and Solaris systems management solution") has been released, including a list of features and enhancements and some known issues. Scott Williams proposed[10] offering support for end-of-life versions of Fedora in a new Freenode IRC channel (#Fedora-EOL), complete with some discussion in the comments about whether or not this was a good idea. Dave Jones generated[11] a neat graph of the performance of an SSD Jef Spaleta provided[12] some interesting statistics about VCS usage from Debian as well as fedorahosted.org, and discussed some of the implications. [0] http://www.fergytech.com/2009/01/17/being-apart-of-something-bigger/ [1] http://overholt.ca/wp/?p=114 [2] http://iquaid.org/2009/01/11/moving-toward-a-content-management-decision/ [3] http://www.abhishekrane.com/2009/01/12/magellanamarok-2011-released-scree... [4] http://jspaleta.livejournal.com/32178.html [5] http://jspaleta.livejournal.com/32733.html [6] http://jspaleta.livejournal.com/33152.html [7] http://jspaleta.livejournal.com/32488.html [8] http://gregdek.livejournal.com/43698.html [9] http://zeusville.wordpress.com/2009/01/15/spacewalk-04-released/ [10] http://vwbusguy.wordpress.com/2009/01/16/help-needed-fedora-eol/ [11] http://www.codemonkey.org.uk/2009/01/16/gskill-ssd-performance/ [12] http://jspaleta.livejournal.com/32888.html --- FUDcon Boston --- Máirín Duffy took[1] some photos of the latest FUDcon Boston shirts. Chris Tyler announced[2] that "Video from eight of the FUDCon F11 sessions plus Paul Frield's closing remarks/State of Fedora are now available". Karsten Wade asked[3] "Where are your FUDCon session notes?" (so if you have any session notes from FUDcon, feel free to follow these tips to share them with others who may not have been so fortunate to attend in-person). [1] http://mihmo.livejournal.com/67737.html [2] http://blog.chris.tylers.info/index.php?/archives/170-FUDCon-F11-Video.html [3] http://iquaid.org/2009/01/16/where-are-your-fudcon-session-notes/ --- How-Tos --- John Poelstra wrote[1] about how to perform "Fast Spaceless Backups". Bogomil Shopov shared[2] a quick tutorial on "Installing LXDE on Fedora". LXDE is the Lightweight X11 Desktop Environment ("a desktop environment which is lightweight and very very fast"). [1] http://poelcat.wordpress.com/2009/01/14/fast-spaceless-backups/ [2] http://www.bogomil.info/int/installing-lxde-on-fedora -- Developments -- In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley --- The Possible Future of Comps ? --- Seth Vidal reported[1] that one outcome of the recent FUDCon[2] had been an initiative to overhaul the comps.xml file. This file is part of the metadata used to define group membership of related packages in order to allow[3] yum or anaconda to aid in installation. Seth described the intent to replace the fixed group definitions with metapackages created on-the-fly, based on examining and dependency-solving repository metadata, as "a fairly radical departure". Related changes will be the ability to define groups within groups and the addition of new metadata to allow tag cloud classification. Some of the anticipated benefits are the ability to find desired software more easily, the creation of more fine-grained groups and a more intuitive persistence of groups. One apparent sticking point raised by Bill Nottingham was that the flattening of the package levels included the removal of "conditional" packages and "[...] a large portion of the language support is built around conditional packages." Seth argued[4] that removing conditional packages was something which was desirable whether or not this particular initiative took hold. This seemed like a problem especially for KDE but Bill prototyped[5] a yum plugin to solve the problem. Some examples in which removing a metapackage would not remove dependencies installed to satisfy the metapackage were teased out[6][7] in conversations between Josh Boyer and Seth and Jesse Keating. Florian Festi thought[8] that the list of problems to be solved should be expanded to include how multilib is handled, the proliferation of noarch subpackages and poor implementations of parts of the tool-chain. He also emphasized that with the "increasing number of languages supported and packages being properly translated we ship more and more language dependent content the users are not interested in. We are currently missing both a way to package these contents properly and a mechanism the control which should be actually installed." [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00733.html [2] http://fedoraproject.org/wiki/FUDCon [3] http://fedoraproject.org/wiki/PackageMaintainers/CompsXml#How_comps_is_used [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00748.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00882.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00751.html [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00777.html [8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00841.html --- New GPG Signing Keys for Each Release --- Jesse Keating asked[1] what value Fedora users perceived in the presence of the "[...] two gpg keys per release, one for rawhide/updates-testing and one for the final release and stable updates." Todd Zullinger suggested[2] that eschewing the importation of the "updates-testing" key would ensure that "[...] no packages from updates-testing are installed on a box [.]" Casey Dahlin disliked[3] such a use of keys to categorize things. Todd asked if each new release would come with a new key, similar to the way this was handled after the infrastructure intrusion. He balanced the sense of confidence given by keeping a key around for a "reasonably long time" versus the mitigation of "the lack of any way to revoke a key in the rpm db [.]" Jesse confirmed[4] "[...] yes, we plan to use new keys each release. We can use gpg web-"-trust thing and sign the new keys with the old keys and whatnot, does that actually help people?j Douglas E. Warner and Steve Grubb worried[5] that the inability to revoke keys exposed machines to repository metadata attacks and Steve revealed[6] that the import of keys is "[...] one of the few security sensitive actions that is not put into the audit system." [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00999.html [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01001.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01020.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01003.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01036.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01050.html --- libssl.so.7 Going Through a Bumpy Patch --- Tomas Mraz advised[1] that he was going to build a new OpenSSL in rawhide which would require a soname bump due to minor breakage of the ABI. As a transitional measure he intended to temporarily provide symlinks to the old soname so that most of the 288 affected packages should continue working until they were rebuilt. Jesse Keating expressed[2] disquiet with the timing as the large number of rebuilds would be "[...] likely to break buildroots, break anaconda composes, break installs, break users. This isn't the kind of crap we want to land in rawhide just before a freeze, and just before an effort to turn that freeze into something usable. PLEASE wait until after Alpha has been cut to do this." He seemed slightly mollified[3] by Tomas' use of compatibility symlinks and rpm provides. When Benny Amorsen wondered why such breakage was occurring again with openssl Tomas explained[4] that the design "declar[ed] some important structures which have to be changed/extended with new functionality in the public headers. Unless they move these structures to private headers this situation is going to happen again." Christopher Aillon joked[5] that it was happening again because Benny had not ported his applications to use NSS(see FWN#107[6]). Later Horst von Brand reported[7] widespread problems with many packages which seemed to fail. RalfErtzinger explained[8] that "[t]he problem is that the openssl package was supposed to contain symlinks for libssl.so.7 and libcrypto.so.7, and rpm -ql says that the package does contain them, but they are, in fact, missing from the filesystem." Tomas Mraz scrambled[9][10] to sort out the problem by trying to run ldconfig in the %post of the openssl package. Kevin Kofler suggested[11] a possible cause. Jesse Keating fretted[12] that all of this was exactly what he did not want just before next week's alpha freeze[13]. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00758.html [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00761.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00764.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00880.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00977.html [6] https://fedoraproject.org/wiki/FWN/Issue107#Crypto_Consolidation [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00941.html [8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00942.html [9] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00943.html [10] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00946.html [11] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01051.html [12] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01000.html [13] https://fedoraproject.org/wiki/Releases/11/Schedule --- MinGW Package Reviews Requested --- Richard W.M. Jones noted[1] that the rapid development cycle[2] meant that Fedora 11 was already approaching (2009-01-20) alpha-freeze and asked for package reviews of the outstanding parts of the MinGW Windows cross-compiler feature[3]. He offered to trade reviews with interested parties and provided links to outstanding reviews. There is apparently no question that the feature, which will allow generation of Windows targets on Fedora, will slip from Fedora 11. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00793.html [2] https://fedoraproject.org/wiki/Releases/11/Schedule [3] https://fedoraproject.org/wiki/Features/Windows_cross_compiler --- MySQL 5.1 Coming to Rawhide After Alpha-Freeze --- A heads-up was posted[1] by Tom Lane to advise that mysql-5.1.30 would be pushed into rawhide immediately after the alpha freeze. He warned: "This involves an ABI break: libmysqlclient.so has increased its major version number from 15 to 16 [...]" and provided a list of affected packages along with the offer to launch rebuilds for anyone who wished. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00721.html --- Spins SIG Controversy --- A vigorous disagreement erupted when Jeroen van Meeuwen announced[1] that the Spins SIG[2] would henceforth be having meetings every two weeks (Jeroen later rescheduled[3] the meeting to Mondays at 17:00 UTC) and that the first meeting would be to finalize a new process arrived at during the last FUDCon. Rahul Sundaram contended[4] that "[s]uch decisions shouldn't be taken at FUDCon because it automatically excludes people who cannot be present at the event. You should use the events only to discuss the issues and make the decisions over mailing lists or irc where others can participate as well." A long thread mostly involving just Rahul, Jeroen and Josh Boyer resulted. In response to Rahul's point that the new process was onerous as it mandated a weekly compose and report JoshBoyer seemed[5] to be of the opinion that this was a good thing. BillNottingham added[6]: "It's not really adding anything to the amount of work that needs to be done, in total. It's just shifting around who it gets done by and when." Some weight was given to Rahul's argument that the method of arriving at the new process was a problem when Jeroen posted[7] that no minutes had been kept of the meeting and pointed to a "5-minute after best-recollection of what happened" summary on the wiki[8] as a source of information. JesseKeating argued[9] that FUDCon was a useful, "high-bandwidth" means of having discussions and that public email was too slow to make decisions compared to IRC, IM, phone and face-to-face meetings. Subsequently he added that the result of the FUDCon discussions was a proposal and not a decision and suggested that unless the skeleton process was approved quickly then there might be no spins for Fedora 11. Rahul responded[10] that the original post had been a simple declaration which did not suggest it was merely a proposal. Rahul added[11] that there was a need to clarify the process in order to avoid the confusion of the past. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00695.html [2] http://fedoraproject.org/wiki/SIGs/Spins [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00782.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00789.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00811.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00826.html [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00838.html [8] http://fedoraproject.org/wiki/SIGs/Spins_NewProcess [9] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00864.html [10] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00872.html [11] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00874.html -- Documentation -- In this section, we cover the Fedora Documentation Project. http://fedoraproject.org/wiki/DocsProject Contributing Writer: Jason Taylor --- Fedora Content Management System (CMS) --- There has been a need for a CMS within the project and there will soon be a decision made in this regard. Karsten posted[0] the reasoning behind moving to a CMS[1] and the need for people with CMS administration experience to lend a hand. [0] https://www.redhat.com/archives/fedora-docs-list/2009-January/msg00077.html [1] https://fedoraproject.org/wiki/CMS_solution_for_Fedora_Project_websites#B... -- Translation -- This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee --- Dimitris Glezos Appointed to the Fedora Board --- The current chair of the Fedora Localization Steering Comittee (FLSCo), DimitrisGlezos has been selected[1] to fill one of the appointed seats on the Fedora Board[2]. [1] https://www.redhat.com/archives/fedora-announce-list/2009-January/msg0000... [2] http://fedoraproject.org/wiki/Board --- New Team for Kashmiri and New Coordinator Marathi --- RakeshPandit announced[2] the start of the Kashmiri Translation Project for Fedora. The Marathi Translation team found its new coordinator in SandeepShedmake[3]. [2] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00040.html [3] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00073.html --- Packagekit Translations for Fedora 11 --- RichardHughes, the maintainer of Packagekit announced that a new version of the package would be released in a couple of weeks and this version would be included in Fedora 11. He mentions that quite a few popular languages do not have complete translations at the moment. Translators can mail the packagekit mailing list for queries regarding translateable strings[4]. Meanwhile, it has been noticed that both the Gnome and Fedora Status pages do not contain updated translations statistics for this package[5]. [4] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00071.html [5] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00075.html --- Confusion over Translations for Newly Coined Words --- RichardvanderLuit brought forward an interesting problem related to the translations of newly coined words for English, which are specifically targetted for computer science[6]. The word in question is "untrusted" which differs from the general English antonym for "trusted". [6] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00080.html --- Branching of Fedora Packages --- AnkitPatel started a discussion about the availability of a branching process in the VCS for Fedora packages, to provide for backporting of translations[7]. MiloslavTrmac (Mirek) suggested submitting patches in bugzilla for such cases, as upstream packages generally do not branch out for versions in the distributions[8]. Linking up the translation interface with an automated bug sumission process was suggested by AsgeirFrimannsson as a possible solution[9]. Discussions still continue, listing merits and demerits of the possibility of large scale backporting via bugzilla and separation of the translations from the packages. [7] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00046.html [8] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00047.html [9] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00051.html --- New Members in FLP --- ZakWang from Hunan, China[10] joined the Simplified Chinese team and RakeshPandit joined to start the Kashmiri Team for Fedora[11]. [10] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00068.html [11] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00040.html -- Artwork -- In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei --- Theming Fedora 11 --- For this release cycle, the Art team is trying a slightly different process with linking the desktop theme to the release name, so just after the codename "Leonidas" was announced for Fedora 11, the process started with Máirín Duffy proposing on @fedora-art two possible approaches, navigation "We could get some inspiration from traditional nautical tools, like compasses, navigational charts, telescope, all that kind of stuff. It could have a kind of steampunk look" and water "Or we can get some inspiration from water and water traffic. For example, imagine time lapse photos of a river in a city over the course of a day, with folks rowing crew in the morning, sailing in the afternoon, with tour/party boats coming through in the evening - for the time-lapse wallpaper". [1] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00034.html Nicu Buculei observes[2] that even if the release name is based on a historical ship, most people will associate it with the ancient Greek hero "Technically the vote was for the ship but I am sure (and the reaction after the announcement are a reassurance) most people voted for the Spartan" and support a theme based on the Ancient Greece culture "So I am thinking about the Golden ratio, used a loot in the Ancient Greek architecture, notably on the Parthenon and probably a graphic based on the Golden ratio would be fit", a take endorsed[3] by Samuele Storari "The Hellenic age was the top of the acient greece time and it spouse the first concept as well, maybe we can use a steam punk, futuristic theme for the old art" and Konstantinos Antonakoglou[4] "Basically, I imagine a trireme-like, or even an ancient fish-boat (with or without the Fedora logo on its sail :P) sailing on a sea of stars (with splashes on its front). I guess it can be combined with the golden ratio , math etc." [2] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00045.html [3] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00046.html [4] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00047.html At the same time, Charlie Brej noted[5] some possible inadvertent uses of the release name "The only problem is the theme should be as acceptable to as many people as possible. So, for the Leonidas theme we should stay away from: violence, nudity, blood, glorification of war, nationalistic sentiments etc..." [5] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00048.html Mark reiterated[6] his old idea or reusing the theme of an older release, "How do you guys feel about a full theme in the old fedora (Core 1 till 4) colors? The link with the F11 name is (just making it up now) : Reviving old days. (the name represents something old and the theme represents the beginning years of fedora)", an idea not liked by the rest of the team, as noted by Máirín Duffy][7] and Luya Tshimbalanga[8]. [6] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00053.html [7] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00054.html [8] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00055.html Máirín Duffy started[9] a wiki page[10] to collect all the proposals, keep an eye on it to follow the development. [9] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00050.html [10] https://fedoraproject.org/wiki/Artwork/F11_Artwork Closely related tot he theme development is the draft scedule[11] for the Art Team proposed[12] by John Poelstra. [11] http://poelstra.fedorapeople.org/schedules/f-11/f-11-art-tasks.html [12] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00058.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 --- * nfs-utils-1.1.4-6.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * tqsllib-2.0-5.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * bind-9.5.1-1.P1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * xine-lib-1.1.16-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * amarok-2.0.1.1-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * drupal-6.9-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... --- Fedora 9 Security Advisories --- * bind-9.5.1-1.P1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * nfs-utils-1.1.2-9.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * xine-lib-1.1.16-1.fc9.1 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * tqsllib-2.0-5.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * drupal-6.9-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... -- Virtualization -- In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley --- Libvirt List --- This section contains the discussion happening on the libvir-list. ---- sVirt 0.30 Released ---- James Morris announced[1] "the release of v0.30 of sVirt[2], a project to add security labeling support to Linux-based virtualization. [1] http://www.redhat.com/archives/libvir-list/2009-January/msg00158.html [2] http://selinuxproject.org/page/SVirt ---- sVirt Qemu Hurdles ---- Daniel J Walsh began to work on the svirt lock down of the qemu process, and saw[1] a problem with "the image:Echo-package-16px.pngqemu binaries are being used to both setup the guest image environment and then to run the guest image." "The problem with this is the act of installing an image or setting up the environment an image runs within requires much more privileges then actually running the image." "SELinux runs best when one processes forks/execs another process this allows us to run the two processes under different labels. Each process with the privileges required to run." [1] http://www.redhat.com/archives/libvir-list/2009-January/msg00198.html ---- Fine Grained Access Controls ---- Konrad Eriksson desired[1] is "an addition[2] to image:Echo-package-16px.pnglibvirt that enables access control on individual actions and data that can be accessed through the library API. This could take the form of an AC-module that, based on the identity of the caller, checks each call and grants/denies access to carry out the action (could also take parameters in account) and optionally filter the return data. The AC-module could then interface different backend AC solutions (SELinux, RBAC, ...) or alternatively implement an internal scheme." Daniel P. Berrange pointed[3] out how this relates to sVirt. "At this stage sVirt is primarily about protecting guests from each other, and protecting the host from guests. Konrad's suggestions are about protecting guests/hosts from administrators, by providing more fine grained control over what libvirt APIs an admin can invoke & on what objects. Both bits of work are required & are complementary to each other." [1] http://www.redhat.com/archives/libvir-list/2009-January/msg00282.html [2] http://wiki.libvirt.org/page/TodoFineGrainedSecurity [3] http://www.redhat.com/archives/libvir-list/2009-January/msg00362.html ---- Configuring Host Interfaces RFC ---- David Lutterkort composed[1] an RFC beginning "For certain applications, we want image:Echo-package-16px.pnglibvirt to be able to configure host network interfaces in a variety of ways; currently, we are most interested in teaching libvirt how to set up ordinary ethernet interfaces, bridges, bonding and vlan's. Below is a high-level proposal of how that could be done. Please comment copiously ;)" Adding this type of support struck some as a complex open-ended prospect. John Levon argued[2] "We should be considering why libvirt is /well-placed/ to configure the host. I think it should be pretty clear that it's actually not: the problems around distro differences alone is a good indication. The proposed API is anaemic enough to not be of much use. This is way beyond carving out the physical system into virtual chunks and it's a big step towards lib*virt* becoming libmanagement." Daniel P. Berrange countered[3] "The existance of many different [implementations] is exactly the reason for libvirt to have this capability. Libvirt is providing a consistent mgmt API for management of guests and host networking interfaces is as much a part of this as the storage management. Libvirt is providing this capability across virtualization technology." Also saying[4] "Network interface APIs are the core missing piece of libvirt API functionality IMHO." [1] http://www.redhat.com/archives/libvir-list/2009-January/msg00350.html --- end FWN 159 --- ----------------- Pascal Calarco, Fedora Ambassador http://fedoraproject.org/wiki/User:Pcalarco

14 years, 4 months

1
0
0 / 0

FUDCon F11 Barcamp Session Video Available

by Chris Tyler

Video from the FUDCon F11 Barcamp is available via the barcamp schedule page: https://fedoraproject.org/wiki/FUDCon:FUDConF11_BarCamp_schedule These videos are in unedited .ogg/.ogv format and are under a CC-BY-SA 3.0-US license. -Chris

14 years, 4 months

1
0
0 / 0

Migration of the Fedora Mailing Lists

by Jon Stanley

Over the last several years, there has been some contention over why our mailing lists are @redhat.com instead of @fedoraproject.org, and there are also some concerns over the process of requesting new lists and so on. As a result, we (myself and Dennis Gilmore) are beginning an effort to migrate fedora-*(a)redhat.com to lists.fedoraproject.org. WHAT BENEFIT DOES THIS HAVE FOR FEDORA? =========================================== We will now be in control of our own mailing lists, can be more responsive to the community for questions or issues with the lists. It also give us our own identity for the lists, separate from Red Hat. WHAT DOES THIS MEAN TO ME? ============================= Right now, nothing. We are still working on some of the backend infrastructure in order to allow this migration to occur. However, in the near future, we'll be working with each of the list owners in order to migrate. We'll start with small lists, and gradually work our way up to larger ones. Subscriber lists will be copied from the Red Hat mailman instance to the Fedora one. Mail filters will need to be changed in order to accommodate the new List-ID headers from this new instance of mailman. Archives will reamin posted at the redhat.com mailman instance. WHAT NOTICE WILL BE PROVIDED? =============================== We'll work with each individual list owner in order to determine a date for the migration. Several weeks prior to the date, we'll send a reminder e-mail to the list in question. We'll always be available for questions in #fedora-admin on irc.freenode.net. As always, if you have any questions about this, feel free to reach out to me directly, either via e-mail or jds2001 on IRC, or extension 5102788 on Fedora Talk!

14 years, 4 months

1
0
0 / 0

Fedora Weekly News #158

by Pascal Calarco

Fedora Weekly News Issue 158 Welcome to Fedora Weekly News Issue 158 for the week ending January 11th, 2009. http://fedoraproject.org/wiki/FWN/Issue158 In this first FWN issue of 2009, we bring you several announcements of the outcomes of recent Fedora-related elections. Fedora 8 reaches its end of life (time to upgrade!), and FUDCon 11 reports abound. Much news coverage of the Fedora Planet, including Fedora 10 vs. OpenSuSE, explanations on some of the recent security items now in the latest (2.6.28) Linux Kernel, and Fedora and OLPC goodness. From the development realm, useful coverage of the state of Intel graphics under Fedora 10 and debates on disabling staging drivers. Release notes and packaging guide areas need volunteers in the documentation project, and the translation team welcomes new members and suggests new language teams. In artwork, announcement of a new November/December issue of Echo Monthly News, another great sister Fedora publication. Security advisories for Fedora 9 and 10 are brought to light and the issue round out with more virtualization coverage, including announcement of Xen 3.3.1 in Rawhide and a new Fedora virtualization list, "everything concerning Fedora and virtualization, including Xen." Read on! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. We welcome reader feedback: fedora-news-list(a)redhat.com FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala [1] http://fedoraproject.org/wiki/NewsProject/Join -- Announcements -- In this section, we cover announcements from the Fedora Project. http://www.redhat.com/archives/fedora-announce-list/ http://www.redhat.com/archives/fedora-devel-announce/ Contributing Writer: Max Spevack --- Election Results --- Bill Nottingham and Matt Domsch were re-elected to the Fedora Board for two-release terms[1]. Josh Boyer, Dan Horák, Jarod Wilson, and Jon Stanley were elected to the Fedora Engineering Steering Committee for two-release terms[2]. Max Spevack, Joerg Simon, Francesco Ugolini, Thomas Canniot, Rodrigo Padula, David Nalley, and Susmit Shannigrahi were elected to the Fedora Ambassadors Steering Committee for two-release terms[3]. Paul Frields announced that Dimitris Glezos has been appointed to fill the final seat on the Fedora Board[4]. [1] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg0001... [2] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg0001... [3] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg0001... [4] http://www.redhat.com/archives/fedora-announce-list/2009-January/msg00007... --- FUDCon Boston 2009 --- Hopefully, you were able to attend to attend FUDCon Boston, January 9-11. If you weren't, keep reading below for coverage! [1] https://fedoraproject.org/wiki/FUDCon/FUDConF11 --- Fedora 8 End of Life -- The end-of-life for Fedora 8 is Wednesday, January 7[1]. No further updates will be issued, no new builds will be allowed in the build system, and all open bugs against Fedora 8 will be closed WONTFIX[2]. [1] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg0001... [2] https://fedoraproject.org/wiki/End_of_life -- Planet Fedora -- In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. http://planet.fedoraproject.org Contributing Writer: Adam Batkin --- General --- Michael DeHaan wrote[1] an essay entitled Academics, Innovation, Patents, And a Path Beyond? about FOSS, cross-organizational collaboration and encouraging innovation. Jef Spaleta had some ideas[2] about "how to do more focused new contributor recruitment and training in Fedora" and using the Mugshot online service to gather statistics and create personalized notifications (invitations) to its users. Máirín Duffy created[3] a list of questions (and provoked a healthy discussion) that could be used to develop a set of guidelines for notifications ("Chatty Applications"). Greg DeKoenigsberg wrote[4] about some of the work going in to synchronizing Fedora and OLPC efforts. James Morris explained[5] some of the security changes that have gone in to the latest (2.6.28) Linux Kernel. Karsten Wade asked "why aren’t you publishing on the Fedora wiki?"[6] and followed up with a set of thoughts to encourage documentation contributions. After a few Fedora 10 frustrations, Scott Williams tried-out[7] OpenSuSE and found some good bits and some not-so-good bits. The latest Red Hat Magazine included[8] a video interview of Michael DeHann discussing Cobbler "and how it simplifies network installations for datacenters and other large-scale linux environments". James Laska continued[9] his tutorial on Creating a virtual test lab (using tools such as Cobbler, Koan and SNAKE). David Nalley thanked[10] HP for providing Mini-notes (with Linux preinstalled!) for Fedora Ambassadors. Jef Spaleta wrote[11] an open letter to Mark Shuttleworth questioning the openness (or lack thereof) of Canonical's Launchpad. [1] http://www.michaeldehaan.net/?p=820 [2] http://jspaleta.livejournal.com/31456.html [3] http://mihmo.livejournal.com/66637.html [4] http://gregdek.livejournal.com/43404.html [5] http://james-morris.livejournal.com/37583.html [6] http://iquaid.org/2009/01/06/the-outside-and-inside-of-documentation-or-w... [7] http://vwbusguy.wordpress.com/2009/01/07/review-opensuse-111/ [8] http://www.redhatmagazine.com/2009/01/07/video-spotlight-on-cobbler/ [9] http://jlaska.livejournal.com/3910.html [10] http://www.nalley.sc/david/?p=171 [11] http://jspaleta.livejournal.com/31829.html --- FUDCon 11 --- A small selection of FUDCon-related posts: [1] http://sexysexypenguins.com/2009/01/10/fudcon-f11-not-in-boston-listen-li... ("Not in Boston? Listen Live, Watch Videos After!") [2] Photos: http://mihmo.livejournal.com/67003.html [3] More photos: http://mihmo.livejournal.com/67287.html [4] Even more photos: http://mihmo.livejournal.com/67388.html -- Developments -- In this section the people, personalities and debates on the @fedora-devel mailing list are summarized. Contributing Writer: Oisin Feeley --- Default ssh-agent Dialog Pop-up --- Confusion abounded when user "nodata" reported[1] that running ssh-add from the command-line popped up a gnome dialog requesting his private SSH key. "nodata" disliked handing out his private key in such a manner. The confusion resulted from the availability of at least two possible ssh-agents[2] and also a change in configuration between Fedora 9 and Fedora 10 which presents the authentication dialog by default. Ricky Zhou was among those who suggested (with a manpage quote) that the SSH_ASKPASS environment variable determined whether the passphrase was read from a terminal or by an X11 dialog. Separately Jesse Keating[3] and Nalin Dahyabhai explained[4] that the dialog was presented by gnome-keyring and not gnome-ssh-askpass. "nodata" questioned[5] whether the behavior had changed between Fedora 9 and Fedora 10 and expressed irritation that a "[...] GUI is popping up when I am using a command line app." Jesse Keating responded[6]: "You're using a command line app from a graphical terminal. Also, cli apps aren't the only use for ssh and ssh keys." This did not appeal to many respondents including John Linville who questioned[7] the benefit of changing focus to a new window to type a passphrase. Callum Lerwick rather tartly outlined[8] some benefits including preventing key logging attacks. Matthias Clasen suggested[9] using gconftool-2 -s -t bool /apps/gnome-keyring/daemon-components/ssh false to turn off the behavior for those who dislike it and this led to several requests to make this the default. Andrew Haley put[10] the case that "[t]he key argument against a pop-up dialog box that asks for the passphrase is that we're training people to type secrets into pop-up dialog boxes. Bad psychology, bad security." ][MatthiasClasen|Matthias Clasen]] and Tomas Mraz with Jerry Amundson explored[11] the use of SSH_ASKPASS as an alternate method to disable the GUI dialog. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00486.html [2] Private keys are stored by ssh agents so that they may handle all key related operations requested by clients. The passphrase to decrypt the key thus need only be typed into the agent once instead of per-operation. [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00487.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00536.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00492.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00495.html [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00523.html [8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00533.html [9] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00498.html [10] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00517.html [11] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00540.html --- Intel Graphics Installation Woes --- "Mike" requested[1] information on when a working xorg-x11-drv-i810 driver for Intel graphics chipsets had a chance of appearing. He was disappointed that it was non-trivial to get two machines with 82945G and 82845G chipsets installed and had needed to fall back to using the vesa driver instead of the intel one. Others listed outstanding bugzilla entries for a wide range of Intel chipsets. Dan Williams asked[2] if using Option "EXANoComposite" "true" as a workaround for problems with the i830 chipsets was succesfull and received mixed reports. It seemed that he was making some progress with resolving some of the issues. MAYoung suggested[3] that setting "NoAccel true" in xorg.conf might work for some people but that "[...] intel graphics are highly flaky on Fedora 10." Robert Arendt laid[4] the blame at the door of upstream merges of GEM/DRM into the kernel and noted that other distributions were suffering identical problems. "Mike" later confirmed[5] this with a list of bugzilla entries from upstream freedesktop.org: "It would be nice if Intel would help to get this fixed, and there are indeed problems with Suse, Ubuntu and Mandriva also with newer drivers and Intel graphics chipsets of various flavors - this is really bad!" [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00435.html [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00475.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00443.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00445.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00467.html --- KPackageKit Auto-update Bug --- Michael B Allen reported[1] that his system had performed an update without his permission and asked how to completely disable such behavior. It appeared[2] that this was due to a bug in KPackageKit which has been unfixable[3] for over a month due in part to the complexity of the code. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00461.html [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00504.html [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00510.html --- Disabling Staging Drivers ? --- Rahul Sundaram asked[1] if enabling the many new drivers in the staging tree[2] would make sense in rawhide in order to support a wider range of hardware such as the EeePC's ralink wireless chipset. Opinion was roughly split between those who were completely against the idea and those who suggested avoiding codifying a rigid policy. Matthew Garrett believed[3] that it would be "somewhat user-hostile" to, for example enable the ralink drivers in rawhide but possibly remove them for a general release. He argued that the ralink drivers were a dead-end[4] which would never merge upstream. On the other hand Dave Jones preferred[5] to take a case-by-case approach as long as "[...] we have someone responsible for working on it, with the goal of getting it out of staging, and dealing with bugs etc. Not unlike the same reasoning for us adding various not-yet-upstream drivers to the Fedora kernel really." While preferring to completely disable the staging drivers Thorsten Leemhuis expressed[6] the intention to provide RPM Fusion kmods in that case. Dan Williams made[7] a strong argument that "-staging" itself was a bad idea as it gave "legitimacy to drivers of questionable quality" and John Linville limned[8] the tortured history of the at76 driver. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00459.html [2] "linux-staging" is a kernel tree whose purpose is to test drivers and filesystems for later inclusion in mainline http://lkml.org/lkml/2008/6/10/329 [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00462.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00474.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00472.html [6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00465.html [7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00473.html [8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00476.html --- git-* Commands Moved to /usr/libexec/git-core/ --- Adam Tkac worried[1] that scripts would break due to the latest git branch in rawhide which had moved all the git-* binaries to /usr/libexec/git-core in order to comply with upstream practice. The issue was previously discussed (see FWN#141[2)] with the resolution that updating to git-1.6.0 would be a flag day for this change. Adam suggested that the new location could be added to the PATH environment variable but this received no support. Karel Zak advocated[3] that such scripts should be fixed as the change had been coming since 2006. Bryn Reeves wondered[4] if compatibility symlinks and a release note would ease the transition over a couple of releases. Although the symlinks were generally felt to be a non-effective strategy Todd Zulinger was encouraged[5] by Paul W. Frields to open a bugzilla entry against the Release Notes to ensure that the documentation team take care of highlighting the issue for Fedora 11. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00404.html [2] http://fedoraproject.org/wiki/FWN/Issue141#Git-1.6.0_Commands_to_be_Moved... [3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00408.html [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00410.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00460.html --- Mandatory FHS Adherence --- JasonTibbitts posted[1] a summary and links to the 2009-01-06 FPC meeting deliberations. Interest on @fedora-devel was mostly sparked by the item which declared that the FPC would "Make adherence to the FHS a MUST [.]" Jason encouraged reading of the full minutes in order to understand this item. Doug Ledford discussed[2] the problem his MPI[3] implementations experienced with the FHS and Richard W. M. Jones expressed [4] concern that the FHS was a moribund standard and adhering to it would block projects such as MinGW without any method to evolve the standard. Toshio Kuratomi responded in detail in both threads and pointed out[5] that the MinGW case had been addressed in the meeting and also that there were problems with changing the FHS. [1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00362.html [2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00424.html [3] http://www.open-mpi.org/papers/ipdps-2006/ [4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00469.html [5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00483.html -- Documentation -- In this section, we cover the Fedora Documentation Project. http://fedoraproject.org/wiki/DocsProject Contributing Writer: Jason Taylor --- Docs Project and FUDCon --- At FUDCon the Documentation Project tasks[0] were discussed and some headway was made. There is still work to be done and the information contained here[0] can be used to pickup where tasks were left off. [0] https://fedoraproject.org/wiki/Your_Docs_Project_BarCamp_session_FUDConF11 --- Documentation Team Ownership Deadline --- The Docs Project has divided the published documentation into teams[0]. The teams consist of a Lead who manages the overall direction of the document and writers who write and/or edit various pieces of the published document. There are two publications that need a lead, the release notes[1] and the packaging guide[2]. The packaging guide needs a rewrite and the release notes will start the update/publication process for F11. The deadline for claiming a publication is the week of 11-Jan-2009. [0] https://fedoraproject.org/wiki/Docs_Project_content_tasks_for_experienced... [1] https://fedorahosted.org/release-notes/ [2] https://fedoraproject.org/wiki/PackagingGuidelines -- Translation -- This section covers the news surrounding the Fedora Translation (L10n) Project. http://fedoraproject.org/wiki/L10N Contributing Writer: Runa Bhattacharjee --- cvsl10n Sponsorship and Listing of Sponsors --- As a follow-up to the ongoing discussion about the "cvsl10n" sponsorship procedure, NorikoMizumoto and IgorSoares have put together a page[1][2] with the name of the Administrators and Sponsors of the "cvsl10n" group. IgorSoares suggested the formation of language groups to ease the sponsorship and an aging policy for unattended requests[3]. RunaBhattacharjee suggested if a patch to the existing FAS interface as possible, that would allow addition of the language name when a new member sends a request to join the FLP[4]. ChristianRose also suggested a patch for damned-lies that would allow addition of the "sponsor" information directly on the team's page[5]. [1] https://fedoraproject.org/wiki/L10N/GroupSponsors [2] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00091.... [3] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00086.... [4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00085.... [5] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00024.html --- New Administrators for cvsl10n --- The FLSCo members were upgraded to "Administrators" of the "cvsl10n" group by KarstenWade[6]. [6] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00108.... --- TQSG upgraded --- NorikoMizumoto announced[7] the availability of the updated .pot and .po files of the Translation Quick Start Guide (TQSG). FLP members can also join the TQSG project to help in its maintenance. [7] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00008.html --- New Members in the FLP Project --- ChristopheAlladoum (French)[8], Luís Gomes (Portugeuse)[9], Mieszko Ślusarczyk (Polish)[10], Mario Jalsovec (Croatian)[11], Kris Thomsen (Danish)[12], David Kjær (Danish)[13], Wes Freeman (Spanish)[14] join the FLP teams. [8] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00014.html [9] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00113.... [10] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00112.... [11] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00109.... [12] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00107.... [13] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00094.... [14] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00009.html -- Artwork -- In this section, we cover the Fedora Artwork Project. http://fedoraproject.org/wiki/Artwork Contributing Writer: Nicu Buculei --- Echo News and Development --- After a month of absence, Martin Sourada announced[1] on @fedora-art a new issue[2] of Echo Monthly News "We've just published latest Echo Monthly News Issue. Due too lack of enough content, it is joint of November's and December's happenings" [1] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00021.html [2] https://fedorahosted.org/echo-icon-theme/wiki/MonthlyNews/Issue4-5 [3] https://fedorahosted.org/echo-icon-theme/wiki/MonthlyNews In other Echo related news, Martin announced[4] a poll[5] regarding the future development of the theme "I've just posted a poll about Echo Perspective on Fedora Forum to see our user base opinion and I'd like to hear the opinions of the Art Team members as well" [4] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00030.html [5] http://forums.fedoraforum.org/showthread.php?t=210159 -- 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 --- * proftpd-1.3.1-8.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * xterm-238-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * samba-3.2.7-0.25.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * zoneminder-1.23.3-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * thunderbird-2.0.0.19-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * p7zip-4.61-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * avahi-0.6.22-12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * openssl-0.9.8g-12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... --- Fedora 9 Security Advisories --- * xterm-238-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * proftpd-1.3.1-8.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * thunderbird-2.0.0.19-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * p7zip-4.61-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * am-utils-6.1.5-8.1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * samba-3.2.7-0.23.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... * openssl-0.9.8g-9.12.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg0... --- Fedora 8 Security Advisories --- Fedora 8 is now EOL Per FESCo support for Fedora 8 was discontinued on January 7th 2009 https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.... -- Virtualization -- In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. Contributing Writer: Dale Bewley --- Enterprise Management Tools List --- This section contains the discussion happening on the et-mgmt-tools list -- Help Perfect Cobbler SELinux Policy --- Dominick Grift posted[1] "instructions on how to install a bare SELinux policy for image:Echo-package-16px.pngcobbler. Feedback in the form of AVC denials would be appreciated so that we can perfect this bare policy." Michael DeHaan asked[2] "Would someone like to take a shot at refining this policy some or at least running Cobbler with that for a while (in permissive mode) to identify what else needs to be allowed?" and added the policy to the cobbler wiki[3]. [1] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00003.html [2] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00004.html [3] http://fedorahosted.org/cobbler/wiki/SeLinuxPolicy --- Fedora Virtualization List --- This section contains the discussion happening on the fedora-virt list. --- New Fedora Virtualization List --- On @fedora-xen, Daniel Veillard announced[1] the creation of the new @fedora-virt list. "As the initiator for [the fedora-xen] list, I must admit I made a mistake 3 years ago, I should have picked a list name agnostic from the hypervisor name. With the current state of Xen in Fedora recent releases it really make sense to try to correct that mistake ... it's never too late ! So http://www.redhat.com/mailman/listinfo/fedora-virt is born, I don't want to mass-subscribe people, especially as I think the current list should survive with its Xen centric focus. You can subscribe directly to the new URL above. The topic is everything concerning Fedora and virtualization including Xen. I think the [fedora-xen] list would be a good place for people still using Fedora <= 8 with Xen, but it's just a suggestion :-)" And on @et-mgt-tools Richard W.M. Jones suggested[2] "we should fold et-mgmt-tools into fedora-virt too." [1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00014.html [2] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00010.html --- Fedora Xen List --- This section contains the discussion happening on the fedora-xen list. --- Xen 3.3.1 in Rawhide --- Pasi Kärkkäinen pointed[1] out the release of image:Echo-package-16px.pngxen 3.3.1. A few days later it was made available[2] in Rawhide. [1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00008.html [2] http://koji.fedoraproject.org/koji/packageinfo?packageID=7 --- Manage Shutdowns of KVM Xenner Guests --- Felix Schwarz used[1] image:Echo-package-16px.pngkvm and image:Echo-package-16px.pngxenner to migrate a Fedora 8 Xen dom0 host to Fedora 10. "So far this was easier than expected. :-) Of course there are some smaller issues (Xenner does not work with SElinux, NetworkManager does not support bridges) but now there is only one real issue left: How can I automatically shut down all running VMs when my host machine goes down? All VMs do poweroff if I press the 'shutdown' button in virt-manager. So I guess it's just a matter of sending this signal to all running VMs and waiting a bit." [1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00001.html --- Test Dom0 Kernel For Fedora 10 --- Michael Young has[1] "succeeded in getting a fedora based image:Echo-package-16px.pngkernel to build with Dom0 patches added." ... "If anyone wants to inspect it, the source rpm generated is at http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.28-0.106.rc6.fc10.src.rpm It is completely untested beyond the fact that it compiles for me, so I have no idea if a kernel built from it will actually boot." See also Xen[2] and Fedora[3] wikis. [1] http://www.redhat.com/archives/fedora-xen/2008-December/msg00028.html [2] http://wiki.xensource.com/xenwiki/XenParavirtOps [3] http://fedoraproject.org/wiki/Features/XenPvopsDom0 --- Libvirt List --- This section contains the discussion happening on the libvir-list. -- Interface Bandwidth Controls Max Zhen described[1] a goal of enabling image:Echo-package-16px.pnglibvirt to configure bandwidth rate limits for the network interface of virtual machines, and asked for comments on implementation ideas. [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00644.html --- RHEL 5 Support --- Markus Armbruster posted[1] a "patch series attempts to make image:Echo-package-16px.pnglibvirt just work on RHEL-5. Right now it doesn't, mostly because libvirt relies on version number checks in a couple of places, and RHEL-5's version numbers aren't the whole truth due to various backports of later stuff." Adding "I'm not proposing this for immediate commit, as I'm still testing. But I'd appreciate review: is this the right way to do it?" [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00629.html --- Choice of Private Network Range --- Peter Anvin was[1] "kind of wondering why image:Echo-package-16px.pnglibvirt defaults to 192.168.122.0/24". Refering to RFCs 2544 and 3330. Peter suggested the following alternative ranges: * 192.0.2.0/24 - reserved as "test and example network" * 198.18.0.0/15 - reserved as "benchmark test network" [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00545.html --- Guest-Safe libvirtd Restarts --- A restart of libvirtd will necessarily also restart KVM virtual machine guests. Guido Günther sought[1] to rectify this with a submission of several patches. [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00346.html [2] http://fedoraproject.org/wiki/FWN/Issue146#Maintaining_VM_State_While_Res... --- end FWN #158 --- Pascal Calarco https://fedoraproject.org/wiki/User:Pcalarco

14 years, 5 months

1
0
0 / 0

Fedora 11 release name

by Paul W. Frields

The Fedora 11 release name is: Leonidas The full GPG-signed message from our election coordinator, Nigel Jones, is attached. Thank you to the community for their suggestions, Josh Boyer and the Board for their work on additional diligence searches, and Nigel Jones for setting up the voting. -- 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

14 years, 5 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

announce January 2009