Anmerkungen über das Leben, das Universum und den ganzen Rest
If anybody still needs free tickets for LinuxTag, please comment below you need to get yourself one as mine are all gone.
Falls noch jemand Gratis-Tickets für den LinuxTag braucht, bitte unten kommentieren. Selbst besorgen, denn meine sind jetzt alle weg.
After months of – sometimes controversial – discussion I am happy to announce the new FAmSCo election guidelines. For those of you, who did not follow the discussion, here is a brief summary of the three most important changes:
Instead of electing all seats once a year, we follow the example of the Fedora Board and FESCo and elect half of the committee every 6 months or with every release of Fedora. FAmSCo will not change over sudden and new members can easily catch up with their new duties by learning from others.
Every committee is in danger of members becoming inactive. This can happen to all of us for various reasons such as our dayjobs or personal problems. Under the old guidelines, we had to wait until 3 members left – even with 2 left the committee is hardly operational – and then call a supplementary election – which never happened even though some FAmSCo’s had only 4 active members. Now we are filling vacant seats when necessary, either with runner-up candidates from the previous elections or by appointing new members.
The ambassadors represent the whole Fedora Project, this is why now not only ambassadors are eligible to vote for FAmSCo, but everybody who has signed the Fedora Project Contributors Agreement (FCPA) and is member of (at least) one other group in the Fedora Account System (FAS) is allowed to vote. This will not only strengthen FAmSCo’s position but also help candidates who are active in other groups of the Fedora project.
Last but not least the guidelines have been massively cleaned up.
We think that the new guidelines are a big improvement and want them to come into effect as soon as possible. Therefor we will have a special election for Fedora 18 (the next regular elections were scheduled for F19). All 7 seats in FAmSCo will be open for election. In order to make the transition to the new alternating terms, the top 4 vote-getters will serve 2 Fedora releases, the bottom 3 will have to run for re-election after one release.
More about the upcoming ambassadors elections to come later this week as part of the general Fedora 18 elections announcement or on the elections wiki page. Please help us building a better, stronger and more active FAmSCo by casting your votes.
If you have feedback or questions, please don’t hesitate to ask. We are looking forward for your input on the Fedora ambassadors mailing list or in the ticket in FAmSCo’s trac.
I usually keep my VM’s in /home, because unlike /var it’s a separate partition and has plenty of free space. As I am also using SELinux, I want to set proper file contexts (even if /home is unconfined, I just want to do it right.)
# semanage fcontext -a -t virt_image_t "/home/libvirt/images(/.*)?" # semanage fcontext -a -t virt_var_lib_t "/home/libvirt(/.*)?" # matchpathcon /home/libvirt/images/test /home/libvirt/images/test system_u:object_r:virt_var_lib_t:s0
That’s not what we want, so we set the context for /home/libvirt/images again:
# semanage fcontext -a -t virt_image_t "/home/libvirt/images(/.*)?" # matchpathcon /home/libvirt/images/test /home/libvirt/images/test system_u:object_r:virt_var_lib_t:s0
Nothing has changed. Let’s start over again:
# semanage fcontext -d "/home/libvirt/images(/.*)?" # semanage fcontext -d "/home/libvirt(/.*)?" # semanage fcontext -a -t virt_var_lib_t "/home/libvirt(/.*)?" # semanage fcontext -a -t virt_image_t "/home/libvirt/images(/.*)?" # matchpathcon /home/libvirt/images/test /home/libvirt/images/test system_u:object_r:virt_image_t:s0
So order does matter? And one has to remove contexts to set them again in the right order? That doesn’t scale. Imagine you have to remove contexts all the way up to your root directory…
I would expect something like „specific overwrites general“ but definitely not „last come, first served“.
FUDCon is over and we made quite some progress in various areas. However, there is still a lot of work to do, because we need to implement everything we brainstormed and discussed. Here’s my personal To-Do list:
Please bear with me if it takes me some time to get everything done because I am pretty busy with my dayjob.
The Fedora Board had a meeting on Friday as part of FUDCon Blacksburg and one of the topics we dicussed were the strategic goals the board agreed on last year. The top three ranked ones were:
While we all agree that these goals are worthy, we realized that are problematic:
I think I need explain the last one a little: In addition to the the individual goals we listed examples. In order to make it easy to join Fedora, all our teams should have some documentation about how to join them. It would be easy to have the Board reach out to all groups and say: „We decided you need documentation on how to join your team. Please have it written by next week and report back to us.“ But that’s not how it works.
Instead of enforcing things, we rather need to encourage and enable people. This means that we need to provide tools and manpower to get things done. In this example we would try to liaise a new contributor with a volunteer from the Documentation project and somebody from the group in question. These three people make a perfect team: The new contributor will ask the questions, the group member can answer them and the documentation writer can document is all in nicely for future reference. A win-win situation for everybody: The group gets documentation and hopefully more contributors in the future. The docs writer gains more insight into other parts of the Fedora project and the new contributor can work on something useful right from the start.
Even if there may not have been much progress of the strategic goals in the last year, I think we learned some very important lessons:
This time we had a short cycle and only a few updated packages, but I really wanted to get the 2.3.4 release out the door. It fixes not only the annoying build error that affected many people but also includes another fix for the Range header DoS vulnerability in the Apache webserver.
For a complete list of changes please refer to the release notes.
The upgrade form 2.3.1 is straight forward, there is nothing special you need to care about. If you are upgrading from 2.2.4, please follow the instructions to upgrade from 2.2.4 to 2.3.0 as outlined in the 1st.README file.
Documentation and OpenPKG packages are available as shown on the download page. Binary packages for Debian GNU/Linux 6.0 (Squeeze/stable) and 5.0 (Lenny/oldstable) on x86 platforms can be found next to the sources. As soon as they have synced, you can also use the mirrors.
You can check the integrity of the downloaded files by importing our file distribution key and verify the OpenPGP signature and SHA1 checksums:
$ wget https://ssl.intevation.de/Intevation-Distribution-Key.asc $ gpg --import Intevation-Distribution-Key.asc $ gpg --verify SHA1SUMS.sig $ sha1sum -c SHA1SUMS
Please report bugs in our bug tracker.
Flight to Milan and back:103 EUR
Hotel in Milan: 145 EUR
Hotdog costume on Ebay: 15 EUR
Fun at FUDPub: priceless!
Yesterday I released the Kolab Groupware Server Community OpenPKG Edition 2.3.3. It not only fixes some annoying bugs but also includes some security updates.
For a complete list of changes please refer to the release notes.
The upgrade form 2.3.2 is straight forward, there is nothing special you need to care about. Only if you are compiling packages yourself you need to recompile some due to the OpenSSL update as described in the 1st.README file.
If you are upgrading from 2.2.4, please follow the instructions to upgrade from 2.2.4 to 2.3.0 as outlined in 1st.README.
Documentation and OpenPKG packages are available as shown on the download page. Binary packages for Debian GNU/Linux 6.0 (Squeeze/stable) and 5.0 (Lenny/oldstable) on x86 platforms can be found next to the sources. As soon as they have synced, you can also use the mirrors.
You can check the integrity of the downloaded files by importing our file distribution key and verify the OpenPGP signature and SHA1 checksums:
$ wget https://ssl.intevation.de/Intevation-Distribution-Key.asc $ gpg --import Intevation-Distribution-Key.asc $ gpg --verify SHA1SUMS.sig $ sha1sum -c SHA1SUMS
The native packages for Fedora, EPEL and Debian will be updated to 2.3.3 within the next week.
Please report bugs in our bug tracker.
Original
Fälschung
Unglaublich wie die Synchronisation einen Film verhunzen kann. Bitte unbedingt auf Englisch gucken!
Wie ich eben vom geschwätzigen Moderator hören musste, wird Pops tönende Wunderwelt, die wohl dienstälteste Radiosendung Deutschlands, eingestellt. Am 23. September gibt es eine Abschiedsparty in Bremen, 25. September eine 4stündige Abschiedssendung und danach ist Schluss, aus, Ende und vorbei.
Ein schwerer Schlag, den ich erst mal verdauen muss. Für mich hieß es die letzten 24 Jahre mehr oder weniger regelmäßig „Sonntag Abend gehört Paul E. Pop.“ und ich weiß nicht, was ich jetzt nach dem Tatort machen soll.