One is networking. I've yet to get networking working between the
and the host. Some examples of a working networking addresses (via
ifconfig and dmesg host/guest) would be nice.
At least I could feel certain I wasn't missing anything. In fact,
whole XEN network documentation seems pretty week. It's just suppose
"work" (very Microsoftish thinking). I will note the "getting
wiki" at Redhat was useful, but needs to be updated. Redhat RPM's
ability to install in a specific root is nice. I used that feature
get the kernel-xen-guest installed in my LVM guest root.
Second, these version of xen have locked up my system while
the net from dom0 (dom1, was still not able to see the net).
So what trace logs should I submit?
We have been working at Yumex we need a little bit of help. The newest
version of Yumex has a group browsing feature and we don't really have a
icon for that. I am not a artist or familiar with making icons. I have a
idea for a icon:
Can someone direct me to a graphic in bluecurve or help me out in
refining this concept and making a icon. It has to be a 48x48 graphic
that user can click on the yumex window.
Also attached is a yumex window:
This will be placed on the left column above where it says "Groups".
Thank you for your help.
I have created a craptastic web page to keep track of the status of
X.Org X11R7 modularization with my mad w3b sk1llz. This is an informal
page only, and isn't always 100% up to date, however since many people
have been asking how things are progressing, I wanted to make something
publically available for people to watch.
So, please bookmark the following page and refer to it any time you
would like to know what the current status of modular X.Org is for
Fedora Core 5.
If anyone notices any mistakes or omissions, please bring them to my
attention in IRC or email, and I'll try to correct the page.
Also, if anyone feels they're l33t enough to challenge my web skillz,
and wants to restructure the page to look more pretty or improve
the overall layout in any way, feel free to snarf the data and send
me back a tarball demonstrating how badly your web page hacking skillz
X.Org modularization status page:
If you are involved in the development of Fedora Core as a packager,
here is information that will be relevant to you.
FC5test1 devel freeze now November 14th
Rawhide is undergoing a large amount of churn as we are preparing for
the switch from monolithic to modular X. Modular X is one of the larger
and more important changes of FC5, meaning we need extensive test
exposure. For this reason the test1 devel freeze has been postponed
until November 14th.
Fedora Core 5 Development Schedule has been updated.
Participants of the Fedora Documentation project have an updated
schedule here for release notes content and translation deadlines.
If you are brave and willing to deal with the unpredictability of
rawhide, your assistance in testing, reporting and fixing bugs as we
approach the November 14th devel freeze would be greatly appreciated.
Modular X requires FE5 Fixes
The major change created by modular X is that XFree86-devel and
xorg-x11-devel are no longer provided in the buildroot. All packages in
both Core and Extras are now expected to have BuildRequires on the
individual libFOO-devel packages of the newly split modular X. In order
to ease into this, the current monolithic xorg-x11 package in rawhide
contains many virtual provides for libFOO-devel. Modular X itself will
hit rawhide *REAL SOON NOW*.
In addition to the lack of XFree86-devel and xorg-x11-devel,
/usr/X11R6/lib will disappear so packages that previously hardcoded this
path will need to be fixed. mharris has indicated that he is preparing
a webpage with further details about modular X and things that need to
Unfortunately FC5 rawhide will not be consistent and suitable for many
FE5 builds until the entire modular X tree is pushed. But when it does
happen, everyone's help will be needed to find problems in Core and
rebuild packages in Extras in order to rapidly prepare everything for test1.
>From: Jeff Pitman [mailto:firstname.lastname@example.org]
>Sent: Thursday, November 3, 2005 09:16 PM
>To: 'Development discussions related to Fedora Core'
>Subject: Re: Self-Introduction: Denis Ovsienko and /etc/net project
>On 11/3/05, Denis Ovsienko <linux(a)pilot.org.ua> wrote:
>> How can we start?
>Basically, you are advocating a rewrite of /etc/sysconfig/networking and
>/etc/sysconfig/network-scripts. You may start with a detailed explanation as
>to why the setup, that Redhat has provided, is not up to task.
Just my 2 cents worth:
Wireless WPA support is a glaring omission, for one. The wpa_supplicant software doesn't integrate well with the current RedHat scripts.