This is to announce my intentions to orphan (and hopefully eol) gtk-qt-
engine in fedora.
For F-12+, my plan is to allow the new kcm-gtk package to Obsoletes it. It
will provide a systemsettings/kcm module to configure gtk theming, but
without the problematic "Qt" gtk engine. See also:
[With the next nfs-utils rawhide build, I will be flipping the ]
[switch that will cause all NFS client mounts to try NFS v4 first ]
[At the bottom of this email has the workarounds if this change does ]
[indeed cause pain ]
As part of the https://fedoraproject.org/wiki/Features/NFSv4Default feature
I am one commit away from changing the default protocol version NFS will
be using (or at least trying to use).
What does this means to you? Hopefully nothing! In theory this should
be a very seamless transition but with all new technology there
will be (and are) some rough spots.
Why are make the change? See the NFSv4Default wiki for details,
but in a nutshell:
* Better performance - V4 is now a stateful protocol. Meaning the server keeps
state on all the clients access a particular file or directory. This
allows the server to give out delegations (or leases) which in turn
allows the client to aggressive cache both data and meta data locally
* Firewall Friendly- With v4 only one port is used 2049 for all traffic
including mounting and file locking.
* Finally it enables us use upcoming minor releases of the the protocol.
NFS version 4.1 and pNFS are two example of upcoming minor releases.
FYI, V4 was introduced in Fedora Core 2 so it has been around for a while. I
personally have been using it for my home directory for a couple years now..
For more of the nitty gritty details see
That's the good news... Here is the bad....
Because the mount command will try NFS v4 first, mounts to older Linux servers
will start failing like:
# mount linux-server:/export /mnt
mount.nfs: mounting linux-server:/export failed, reason given by server:
No such file or directory
This is due to a defect in the Linux server exporting code, which is fixed
in F-12, *but* there are a number of workarounds
On the server (Which is suggested):
* Add the following entry to the /etc/exports file:
/ *(ro,fsid=0) Note: 'fsid=0' is explained in the exports(5) man pages.
On the client, go back to v3 mounts by doing one of the following:
* Add -o v3 to command line, similar to:
mount linux-server:/export /mnt
* Change the default mount version in the new /etc/nfsmount.conf file by
uncommenting the Nfsvers=3 setting in the 'NFSMount_Global_Options' section.
See nfsmount.conf(5) man page for details. The diff would look like:
--- /etc/nfsmount.conf.orig 2009-10-26 09:30:21.000000000 -0400
+++ /etc/nfsmount.conf 2009-10-26 10:31:30.227443686 -0400
@@ -31,7 +31,7 @@
# Protocol Version [2,3,4]
# This defines the default protocol version which will
# be used to start the negotiation with the server.
# Setting this option makes it mandatory the server supports the
# given version. The mount will fail if the given version is
Sorry to bug developers, but I didn't get any bites from PPC users on
Does Fedora PPC work or install on oldworld PCI Macs, such as a beige
G3 desktop? My impression is that no one has tried it on an oldworld
Mac in the last few releases, and that getting it to boot at all would
be an adventure.
(Otherwise I'm going to try Debian Lenny, which is said to work, but
about which I know nothing. The machine has 416 MB memory and I'll
install a 40 GB hard disk for Linux, so other than speed it should be
good to go.)
I have the impression that since about 2 days ago the font rendering
in Fedora rawhide is less good than before. Fonts appear fuzzier, and
in particular Luxi Mono looks more deformed. There hasn't been a
freetype update, thus some GNOME package might be responsible.
I have noticed this effect on 2 different systems, one with an ATI
video card, the other with an Intel onboard graphics device. ~C
I've installed F-12 beta on my new laptop with ati radeon hd 4570 graphic
card, I was going to file new bug. With kms enabled, everything is really
sloooow, with 'nomodeset' it's much faster. I can't say exactly "how" slow
is, is there anything I can use for measuring?
btw, mesa-dri-drivers-experimental does not work at all for me (glx apps
To Michal Hlavinka,
Hi, in Fedora 12, KMS for R600/R700 is an experimental features. The next
mainline kernel, 2.6.32 will official support KMS of R600/R700.
Xorg still does not release opensource drivers for R600/R700 to run 3D
program. Mesa-dri-drivers-experimental is just a testing package. It can run
compiz. But compiz is easy to crash with this dri-drivers. Believe that,
Fedora developers still work hard for opensource ati driver. Please wait a
moment. 3D acceleration is coming soon.
Fight for freedom!!!!(3F）
Ask not what your Linux distro can do for you!
Ask what you can do for your Linux distro!
There is a package, already included in Fedora, and there is a
friendly and active upstream developer, who wants to be a
(co)maintainer of this app. (S)he doesn't maintain any packages in
Fedora currently. So the question is - is there a policy on how such
situations should be handled?
I remember, that if Redhat hires someone from upstream, then no
additional procedures with review requests and sponsorship needed (at
least visible to others, outside Redhat) - (s)he just started to be a
With best regards, Peter Lemenkov.
I'm trying to build the latest Asterisk sounds package, but I'm
getting the following error:
error: Recognition of file
failed: mode 100444 zlib: invalid stored block lengthsempty (gzip
compressed data, reserved method, encrypted, last modified: Tue Nov 9
20:48:48 2010, max speed)
The full build log is here:
The build fails in mock locally as well but koji actually gives me a
better error message. The file in question isn't gzip compressed,
it's an audio file compressed with G.729 audio compression. Can
anyone help me out here?
I am working on packaging pagedgeometry and I noticed that when building
on gcc it passes -msse which I am guessing says to use sse instructions.
I think that even in F12 we can't assume these instructions are available.
The package may gain a lot of benefit from using those instructions.
(I haven't tested that yet as I am still pretty early in the process.)
Is there some relatively standard way to handle something like this?
since a year or so the AMD K10 thermal sensors module (k10temp) seems to
be floating around the web. I would appreciate some kernel packager
integrating it into the fedora 11 stock kernel - since without it I can
not build (and trust!) a silent cooling system.
Any plans on this issue?