devel October 2009

devel@lists.fedoraproject.org

259 participants
256 discussions

Fedora with Universal Binaries?
by Neal Gompa 05 Nov '09

05 Nov '09

Hello, I just saw this article about an effort to create Universal binary style ELF binaries for Linux, and I thought that this would be something to watch, so that Fedora could integrate both x86-32 and x86-64 into single DVD sets. http://icculus.org/fatelf/ There is even a proof of concept VM of Ubuntu 9.04 that has both 32-bit and 64-bit kernels and all the apps compiled as FatELF binaries

16 21

Kernel using LZMA compression
by Ikem Krueger 04 Nov '09

04 Nov '09

As I know, the kernel is compressed with bzip2 or gzip. How about using LZMA instead? Or is that already the case?

4 8

orphaning (eol) gtk-qt-engine
by Rex Dieter 03 Nov '09

03 Nov '09

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: https://bugzilla.redhat.com/show_bug.cgi?id=kcm-gtk -- Rex

4 13

Buyer Beware: A Major Change in NFS (in Rawhide) is about to happen
by Steve Dickson 03 Nov '09

03 Nov '09

[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 http://www.iaps.com/NFSv4-new-features.html 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. -# Defaultvers=4 +Defaultvers=3 # # Setting this option makes it mandatory the server supports the # given version. The mount will fail if the given version is steved.

14 36

Fedora PPC for oldworld Mac?
by Tony Nelson 03 Nov '09

03 Nov '09

Sorry to bug developers, but I didn't get any bites from PPC users on fedora-list. 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.) -- ____________________________________________________________________ TonyN.:' <mailto:tonynelson@georgeanelson.com> ' <http://www.georgeanelson.com/>

6 9

Font rendering slightly degraded in recent rawhide
by Christoph Frieben 02 Nov '09

02 Nov '09

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

12 22

Re: Fwd: Request to update ATi OSS driver for Fedora 12
by Liang Suilong 02 Nov '09

02 Nov '09

Hi, 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 it is, is there anything I can use for measuring? Michal btw, mesa-dri-drivers-experimental does not work at all for me (glx apps segfault) 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. -- <url>http://www.liangsuilong.info</url> Fight for freedom!!!!(3F） Ask not what your Linux distro can do for you! Ask what you can do for your Linux distro!

3 6

How to add upstream developer as a (co)maintainer of the existing application?
by Peter Lemenkov 02 Nov '09

02 Nov '09

Hello All! 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 (co)maintainer. -- With best regards, Peter Lemenkov.

9 12

Problem building Asterisk sounds
by Jeffrey Ollie 02 Nov '09

02 Nov '09

I'm trying to build the latest Asterisk sounds package, but I'm getting the following error: error: Recognition of file "/builddir/build/BUILDROOT/asterisk-sounds-core-1.4.16-1.fc13.noarch/usr/share/asterisk/sounds/fr/digits/1.g729" 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: http://koji.fedoraproject.org/koji/taskinfo?taskID=1730585 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? -- Jeff Ollie

2 3

What to do with package that wants to use sse?
by Bruno Wolff III 02 Nov '09

02 Nov '09

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?

5 10

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel October 2009