facti.net

I've installed and have been trying to use F9 on one of my machines for a while now, and if you are thinking of trying it I would suggest that you do not.   It is the worst release in a very long time, maybe of all time for Fedora.  I have used Fedora since it started, and there is something fundamentally worse about this release than all the others. 

Just some of the issues: removal of some important configuration options during install, quite unstable wi-fi drivers, terrible GDM, and the removal of KDE 3 for what can only be described as the currently dreadful KDE 4 implementation.  Stick to F8 until some of the really significant fixes have been implemented, or maybe skip F9 altogether and wait for F10.  F8 was quite a good release.

KDE4 in particular is disappointing. KDE used to be (pre 4) quite a fast and pragmatic desktop that conformed well to the way one worked.  Very configurable and stable and one could configure it just right so one was free to 'just get the job done'. 

xmlcopyeditor is a free, open-source, simple, and light-weight XML editor with schema and correctness validation capabilities. Unfortunately there is no Fedora package for it yet. Installation is simple once you know how, are willing to ignore the INSTALL file, and fix a simple bug.

First install the dependencies:
sudo yum install wxGTK wxGTK-devel pcre-devel xerces-c xerces-c-devel aspell-devel

Next, fix the /usr/include/wx-2.8/wx/filename.h file (line 393) by changing [0u] to [0] (see bug information here: https://bugzilla.redhat.com/show_bug.cgi?id=295521).

Then download the package from sourceforce (I used version 1.1.0.6): http://xml-copy-editor.sourceforge.net/

Then:

tar xvzf  xmlcopyeditor-1.1.0.6.tar.gz
cd  xmlcopyeditor-1.1.0.6
./configure  --enable-unicode
make 
make install

Now you can run it using the xmlcopyeditor command.

Sometimes the failsafes on a system can get in the way of reconstructing things after a boo boo. For example, if you try and re-install a package over itself after accidentally removing a file -- yum won't let you. However it is relatively easy to recover if you know how.

The first step of course is determining which packages may have been damaged. To verify a package use rpm -V, and possibly --nomtime to avoid showing when files were modified, e.g.

rpm -V --nomtime packageName

Where packageName is the name of the package. To verify all packages on your system use something like this:

rpm -qa | xargs -t -n1 -ipName rpm -V --nomtime pName

Or, if you're looking for any damaged packages in a set of related packages you can do something like this:

rpm -qa | grep partOfPackageName | \

xargs -n1 -i pName rpm -V --nomtime pName

Where partOfPackageName is part of the package name.

Installation of the vserver packages is simple in F8:

yum install util-vserver util-vserver-build

However, for anything to actually work you need to build a custom kernel. Once the custom kernel is installed you also need to update the distributions to include F8:

1. cd /usr/lib64/util-vserver/distributions/
2. svn export http://svn.linux-vserver.org/svn/util-vserver/trunk/distrib/f8 f8

Once the distribution is installed you can build the new vserver using the vserver build command, e.g.:

vserver myvserver build -m yum --interface eth0 --interface lo -- -d f8

Where myvserver is the name of your new vserver. Once the build completes you can start your vserver with "vserver myvserver start".

To install additional software packages use vyum:

vyum myvserver -- install packagename

where packagename is the name of the package to install.

Information on getting linux-vserver working on Fedora 8 (F8) seems a bit lacking. While the packages are available (util-vserver), a custom kernel with the appropriate vserver patches must be built or a cryptic "Function not implemented" error will show up when trying to build the vserver guest.

To build the custom kernel, obtain the kernel and corresponding patch from the links provided at the linux-vserver web site. Then bunzip2 and untar the kernel to some appropriate location (I use /usr/src/kernels), e.g.:

1. cd /usr/src/kernels
2. bunzip2 linux-2.6.22.14.tar.bz2
3. tar xvf linux-2.6.22.14.tar
4. cd xvf linux-2.6.22.14
5. patch -p1 ../patch-2.6.22.10-vs2.2.0.5.diff

The patch will give you an initial error, but that can be ignored since it corresponds to a mismatch in the kernel version (...14 vs the expected ...10). Edit the Makefile to change the EXTRAVERSION so it has your own string, I used ".14-vs" to remember it was for vserver.