On Fri, 29.04.11 17:46, Greg KH (greg(a)kroah.com) wrote:
> > > I think /srv actually makes a lot of sense. Probably not so much on the
> > > desktop, but the boundaries are blurry, and I see no reason to set
> > > things up differently in this respect between servers and desktops. I
> > > see little benefit in removing this directory.
> > >
> > > Lennart
> > >
> > I think moving /selinux is a bit more complicated then just a simple
> > kernel change. We have libselinux changes, Lots of tools have learned
> > over the years the path of /selinux and lots of users know about it.
> > I am willing to work towards the goal of moving /selinux, but I might
> > end up with a symbolic link if we can not fix all of the problems.
> A symbolic link from /selinux to point at /sys/fs/selinux/ is a good
> idea to help people migrate. The startup tools should be able to create
> this if /sys/fs/selinux/ is not present, right?
This is not necessarily easy to do actually, since for upgraded systems
/selinux needs to be an actual directory in the rootfs to be useful as
mount points. At boot time the rootfs is read-only, hence removing the
dir then and turning it into a symlink is difficult.
However, we can use the same approach as we did for moving /var/run to
/run: on new installs create it as a symlink and on upgrades simply make
it a bind mount.
For the long run we could also add %post scripts to filesystem.rpm which
moves away the old /selinux, and recreates it as symlink. Unfortunately
that cannot be done completely atomic, but that property is not really
necessary here anyway I think.
So, yeah, it isn't super-pretty doing this move, but we can handle it
more or less exactly like the /var/run → /run move.
Lennart Poettering - Red Hat, Inc.
The clock is ticking. The days are counting down. The release of
Fedora 15, codenamed "Lovelock," is scheduled for release in late
May. Fedora is the leading edge, free and open source operating
system that continues to deliver innovative features to users
worldwide, with a new release every six months.
We are delighted to announce the availability of the Beta release
of Fedora 15.
"I beta one American dollar that you will love this release!"
Come see why we love Fedora so much. We are betting you will,
too. Download it now: http://fedoraproject.org/get-prerelease?wkanF15b
== What is the Beta Release? ==
The beta release is the last important milestone of Fedora 15. Only
critical bug fixes will be pushed as updates leading to the general
release of Fedora 15 in May. We invite you to join us in making
Fedora 15 a solid release by downloading, testing, and providing
your valuable feedback.
Of course, this is a beta release, meaning that some problems may still
be lurking. A list of the problems we already know about can be seen on
the Common F15 bugs page, at http://fedoraproject.org/wiki/Common_F15_bugs.
If you find a bug that's not found on that page, be sure it gets
fixed before release by reporting your discovery at
https://bugzilla.redhat.com/ Thank you!
== Features ==
Desktop enthusiasts and end users of all sorts can look forward to:
* Gnome Shell and the Gnome 3 desktop. Gnome 3 is the next major
version of the Gnome desktop. After many years of a largely
unchanged Gnome 2.x experience, GNOME 3 brings a fresh look
and feel with GNOME Shell.
* LibreOffice Productivity Suite. LibreOffice is a fork of
OpenOffice, with the support of the OpenOffice.org community.
All of the applications you know and love are still there,
including apps for spreadsheets, document creation, and presentations.
* Desktop environments a-plenty. The Xfce and LXDE spins have
been updated, and the Fedora Spins SIG has other offerings
tailored to a wide variety of user needs.
Sysadmins will love features such as:
* Appliance building. BoxGrinder creates appliances (virtual
machines) from simple plain text appliance definition files
for various virtual platforms, and is great for building
appliances for use in a Cloud environment.
* Dynamic Firewall. The dynamic firewall mode aims to make it
possible to change firewall settings without the need to restart
the firewall and to make persistent connections possible.
Coders have lots of new development tools to try out, including:
* Updates to popular languages. Python 3.2, Rails 3.0.3, and
OCaml 3.12 are all included in Fedora 15.
* Project tooling. Maven 3 is a Java project management, project
comprehension, and build system tool.
* Compiling and debugging. GDB gets an update to 7.3, and GCC
4.6 is included. (Fedora 15 has also been rebuilt using GCC 4.6!)
And that's only the beginning. A more complete list and details of
all the new features in Fedora 15 is available here:
We have nightly composes of alternate spins available here:
== Contributing ==
For more information on common and known bugs, tips on how to report
bugs, and the official release schedule, please refer to the release
notes at http://docs.fedoraproject.org.
There are many ways to contribute beyond bug reporting. You can help
translate software and content, test and give feedback on software
updates, write and edit documentation, help with all sorts of promotional
activities, and package free software for use by millions of Fedora
users worldwide. To get started, visit http://join.fedoraproject.org today!
devel-announce mailing list
On Fri, 29.04.11 16:34, Greg KH (greg(a)kroah.com) wrote:
> > > I think it's a very good decision - I never understood why selinux dir
> > > is directly under /.
> > Yes, I think this would be a good thing to have in F16.
> > Note however that this needs a tiny kernel patch to work, to create the
> > mount point under /sys/fs/selinux. This is a trivial patch and has been
> > done for /sys/fs/cgroup before, so I assume this would be easy to get
> > in and just needs a champion to push this forward.
> As I did this for /sys/fs/cgroup I can do it for /sys/fs/selinux as
> well, just let me know.
I'd say "yes, please" to this, right-away.
But I guess this is up to Dan Walsh to say.
Dan, could you say "yes" to this, please? If so, then the first step to
making this happen for F16 would already have been taken!
Lennart Poettering - Red Hat, Inc.
I've got a question whose answer I expected to find on one of these
pages, but no joy:
I'm packaging a library that does some heavy mathematical
computations. The build system tries to cleverly determine whether an
Intel CPU with vector instructions is being used. Until I can
convince upstream to do this at runtime, I'll need to build the
package (a library) for the lowest common denominator. The package
checks for MMX, SSE, SSE2, SSE3, and SSSE3. For i686, can I assume
MMX? SSE? I believe I can also build an SSE2 version of the library
and drop it into /usr/lib/sse2. How about for x86_64? Can I assume
SSE2 is available? (I thought I could, but I see that /usr/lib64/sse2
exists on my machine, so now I'm uncertain.) I don't see a
/usr/lib64/sse3 or /usr/lib64/ssse3, so I just have to forget those,
If there is a wiki page that answers these questions, I'd appreciate a
pointer. If not, perhaps someone with edit privileges could add the
answer to one of the pages listed above. Thanks,
-----BEGIN PGP SIGNED MESSAGE-----
Hi, I'm new to contributing but not new to Linux. I started on RHL 7.1
around 2000 and have used Slackware, Gentoo and Debian in the past. I
was active at my university LUG and Gaming Club (running the game
servers on Slackware) and now I work for Red Hat since August 2007 in
I have been building RPMs for myself on and off almost since I started
at Red Hat and switched from Debian to Fedora. I built RPMs for
Rivendell  which is a large radio automation suite and some
recommended getting that into Fedora but at the time it seemed too
Now I am getting into DJing and in particular using FOSS to do it. I
have used Mixxx and xwax. I am becoming the co-maintainer of Mixxx in
rpmfusion  and have just submitted my first package review request
for Fedora for xwax.  I would like to make Fedora a good platform
for digital DJing.
Mixxx was affected by a portaudio bug that had been fixed in Ubuntu
but not Fedora so I opened a bug  on that and got that fixed.
I have created a mixxx on fedora page for the Mixxx wiki. 
My FAS account is John2583 but you can find me on Freenode as
JBstrikesagain (I think that username was too long for FAS).
I am in #fedora and #fedora-devel among other channels.
You can check out my website to see some other stuff I do:
John Brier, RHCA, RHCVA, RHCX
Senior Technical Support Engineer - NA
gpg: 1024D/251D9FF9 6F7B 242A 9375 F4CC BC6D F453 60D8 35FF 251D 9FF9
http://opensource.com - Where Open Source Multiplies
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----
On Mon, Apr 18, 2011 at 08:18:23PM -0400, Bill McGonigle wrote:
> Hi, Rich,
> I see that you got tagged as owner on the unison packages. Are you
> planning to package any updates, or did you just inherit it by
> default because of its OCaml nature?
Pretty much I inherited it.
> I was going to write a message to -devel, but then I saw Gerard
> didn't own the package anymore, and thought it best to drop you a
> note directly first.
> A new stable was declared in January, so we're officially 3 and 6
> years out of date on the existing packages. It turns out many of my
> complaints about unison have been fixed in the past 3 years!
> Since I don't know any OCaml and this package probably needs to
> combine 3 versions and label multiple binaries, I shouldn't
> volunteer to build this as my first package. But I'd be happy to do
> some manual builds and share notes if that would be useful.
There was a reason for splitting it in the first place which is to do
with (in-)compatibility between the versions. Because the protocol
sometimes changes incompatibly between releases and because we want to
interoperate with servers which may be running different versions, we
need to package up the different versionse separately. However this
is a big pain to maintain, not least because whenever a new
incompatible version comes along we have to apply for a new Unison
package to be added to Fedora(!)
It's probably going to be better to do something with multiple source
files in a single 'unison' package building multiple sub-packages.
Anyhow if you want to co-maintain it, please check the boxes at
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
I've recently been working on updating the Eclipse Mylyn stack in
Fedora. For the impatient, eclipse-mylyn* 3.5.1 packages are already
available in rawhide ;-) Updates for F15 will be pushed soon.
As some of you might know Eclipse Mylyn is now a top-level Eclipse
project and has been split into several sub-projects as of their 3.5
With release 3.5 of Mylyn, there are now a total of 17 binary RPMs
available in Fedora. The two most exciting new features are custom
workflow support for Bugzilla bug trackers and Mylyn Builds (which
provides swift CI interaction from within Eclipse). With its new custom
workflow support, Mylyn 3.5 can now be used to interact (without
restriction) with Red Hat's Bugzilla instance. There is no need to
switch to the browser anymore. See  as to how to set up a Red Hat
Bugzilla task repository with the correct custom transitions file. Note
that we are currently working with upstream to make this setup even
Due to Mylyn's restructuring upstream, we have decided to restructure
Fedora SRPMs as well.  describes the new Fedora SRPMs/RPMs in detail.
If you are a Mylyn user, updates from 3.4 to 3.5 should work fine
without further action. If you are a maintainer of an Mylyn dependent
Eclipse plug-in in Fedora, this could mean that you have to update
requirements/build requirements in your spec-file. Please make sure that
your plug-ins work with new Mylyn 3.5 packages in Fedora. I'd like to
push the Mylyn 3.5 update for Fedora 15 soon and would appreciate if you
could make sure that this doesn't break your plug-ins.  should
provide you with enough information as to what has changed in rawhide
(or will change soon for F15).
Feel free to get back to me should you have questions regarding the
Mylyn update. I'm also on IRC in #fedora-java, #fedora-devel, etc. My
nick is jerboaa.
Having been not terribly impressed with GNOME 3 in F-15 alpha, I thought
I'd try installing the beta with KDE, just to see if the grass is any
greener. I'm still trying to find my way around that one too, but
I've run into one significant problem: when I close my laptop, the
machine doesn't go to sleep. (The sleep indicator light doesn't go on,
I can still ssh into it, it stays rather warmer than it should, etc.)
1. An F-15 bug (and if so, which component ought I file it against)?
2. Expected behavior/missing feature for KDE?
3. My own ignorance about how to configure KDE? (I did look into the
power management settings, which seem remarkably over-engineered
and don't offer any clear "sleep" option...)
regards, tom lane