[Fedora Project Wiki] Update of "Docs/Beats/BackwardsCompatibility/KDE3" by KevinKofler
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by KevinKofler:
http://fedoraproject.org/wiki/Docs/Beats/BackwardsCompatibility/KDE3
The comment on the change is:
Write page about the KDE 3 backwards compatibility support.
New page:
=== KDE 3 Development Platform / Libraries ===
The primary version of KDE in Fedora 9 is KDE 4.0. KDE 3 is no longer offered as a full desktop environment. However, to make it possible to run and build the many existing KDE 3 applications, the following KDE 3.5 library packages are provided:
* `kdelibs3`, `kdelibs3-devel`: KDE 3 libraries
* `kdebase3`, `kdebase3-devel`: KDE 3 core files required by some applications
In addition, while the main purpose of the `kdegames3` package is to include the games which are not ported to KDE 4 yet, it also contains a KDE 3 version of `libkdegames` which is required by some third-party KDE 3 games.
Moreover, the KDE 4 `kdebase-runtime` package, which provides `khelpcenter`, also sets up `khelpcenter` as a service for KDE 3 applications, so help in KDE 3 applications works. (The KDE 3 version of `khelpcenter` is no longer provided, the KDE 4 version is used instead.)
These packages are designed to:
* comply with the Filesystem Hierarchy Standard (FHS), and
* be completely safe to install in parallel with KDE 4, including the `-devel` packages.
In order to achieve this, Fedora KDE SIG members made 2 changes to the KDE 4 `kdelibs-devel` packages:
* The library symlinks are installed to `/usr/lib/kde4/devel` or `/usr/lib64/kde4/devel` depending on system architecture.
* The `kconfig_compiler` and `makekdewidgets` tools have been renamed `kconfig_compiler4` and `makekdewidgets4`, respectively.
These changes should be completely transparent to the vast majority of KDE 4 applications that use `cmake` to build, since `FindKDE4Internal.cmake` has been patched to
match these changes. The changes were made to the KDE 4 `kdelibs-devel` rather than to `kdelibs3-devel` because KDE 4 stores these locations in a central place, whereas KDE 3 applications usually contain hardcoded copies of the library search paths and executable names.
Note that `kdebase3` does '''not''' include the following:
* a complete KDE 3 desktop (workspace) which could be used instead of KDE 4: in particular, KDE 3 versions of KWin, KDesktop, Kicker, KSplash and KControl are '''not''' included,
* the KDE 3 versions of `kdebase` applications such as Konqueror and KWrite, which are redundant with the KDE 4 versions and would conflict with them,
* the `libkdecorations` library required for KWin 3 window decorations, as those window decorations cannot be used in the KDE 4 version of KWin,
* the `libkickermain` library required by some Kicker applets, as there is no Kicker in Fedora 9 and thus Kicker applets cannot be used.
Please note that, as with any backwards-compatibility library, developing new software against the legacy API is discouraged!
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/Virtualization" by KarstenWade
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by KarstenWade:
http://fedoraproject.org/wiki/Docs/Beats/Virtualization?action=diff&rev2=...
The comment on the change is:
be wary of "allow you to"; it's a sign that i) it needs to be removed, and ii) the sentence can be tighter. ;-)
------------------------------------------------------------------------------
Virtualization in Fedora [[GetVal(DocsDict,BeatsVer)]] has some major changes, and new features, that continue to support the Xen and KVM platforms:
- * paravirt ops in the kernel: previously, the Xen kernel was created by forward-porting Xen bits from the 2.6.18 kernel into the current Fedora kernel. This was an arduous task, that was labor intensive, and resulted in the Xen kernel being several releases behind the bare-metal kernel. The inclusion of paravirt ops means that this process is no longer necessary. Once paravirt ops is merged upstream, it will no longer be necessary to have a separate kernel for Xen.
+ * The story of paravirt ops in the kernel: previously, the Xen kernel was created by forward-porting Xen bits from the 2.6.18 kernel into the current Fedora kernel. This was an arduous task, that was labor intensive, and resulted in the Xen kernel being several releases behind the bare-metal kernel. The inclusion of paravirt ops means that this process is no longer necessary. Once paravirt ops is merged upstream, it will no longer be necessary to have a separate kernel for Xen.
- * Improved storage management: previously, Fedora introduced the ability to manage existing guest domains remotely using `libvirt`. It was not possible to create new guests due to the lack of storage management capabilities. In Fedora [[GetVal(DocsDict,BeatsVer)]], new storage management tools allow you to to create and delete storage volumes from a remote host using `libvirt`.
+ * Improved storage management: previously, Fedora introduced the ability to manage existing guest domains remotely using `libvirt`. It was not possible to create new guests due to the lack of storage management capabilities. In Fedora [[GetVal(DocsDict,BeatsVer)]], new storage management can create and delete storage volumes from a remote host using `libvirt`.
* PolicyKit integration: previously, the `virt-manager` application ran as root when managing a local hypervisor, and used `consolehelper` to authenticate from a desktop session. Running GTK applications as root is bad practice. By integrating with PolicyKit, it is now possible to run `virt-manager` as a regular user.
* Improved remote authentication: previously, Fedora introduced support for secure remote management using TLS/SSL, and x509 certificates. Fedora [[GetVal(DocsDict,BeatsVer)]] improves remote management capabilities, by adding support for authentication against a username and password database, Kerberos domain controller, or system authentication using PAM. This feature applies to all tools using `libvirt`.
- * A new P2V tool, shipping as a Live CD, which allows you to convert a bare-metal install to a virtual guest.
+ * A new P2V tool, shipping as a Live CD, for converting a bare-metal install to a virtual guest.
- * A new tool, `xenner`, that allows you to run Xen-paravirtual kernels on top of KVM.
+ * A new tool, `xenner`, for running Xen-paravirtual kernels on top of KVM.
* Storage and network paravirtual-drivers for KVM guests.
* Full support for monitoring network and block statistics of QEMU and KVM has been added to `libvirt` and `virt-top`, bringing parity with statistics monitoring, previously only available to Xen guests.
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/Virtualization" by MurrayMcAllister
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by MurrayMcAllister:
http://fedoraproject.org/wiki/Docs/Beats/Virtualization?action=diff&rev2=...
The comment on the change is:
rewriting, adding a little extra markup...
------------------------------------------------------------------------------
{{{#!html
<h2>Virtualization</h2>}}}
- Virtualization in Fedora [[GetVal(DocsDict,BeatsVer)]] has some major changes and new features that continue to support both the Xen and KVM platforms.
+ Virtualization in Fedora [[GetVal(DocsDict,BeatsVer)]] has some major changes, and new features, that continue to support the Xen and KVM platforms:
- * para_virt ops in the kernel. Previously, the Xen kernel was created by forward-porting the Xen bits from 2.6.18 into the current Fedora kernel. This is an arduous task that was labor intensive and resulted in the Xen kernel being several releases behind the bare-metal kernel. The inclusion of para_virt ops means that this process is no longer necessary. Once para_virt ops is merged upstream, it will no longer be necessary to have a separate kernel for Xen.
+ * para_virt ops in the kernel: previously, the Xen kernel was created by forward-porting Xen bits from the 2.6.18 kernel into the current Fedora kernel. This was an arduous task, that was labor intensive, and resulted in the Xen kernel being several releases behind the bare-metal kernel. The inclusion of para_virt ops means that this process is no longer necessary. Once para_virt ops is merged upstream, it will no longer be necessary to have a separate kernel for Xen.
- * Improved storage management. Previously, Fedora introduced the ability to manage existing guest domains remotely using libvirt. It was not possible to create new guests due to lack of storage management capabilities. In Fedora [[GetVal(DocsDict,BeatsVer)]], new storage management tools add the ability to list, create and delete storage volumes from a remote host using libvirt.
+ * Improved storage management: previously, Fedora introduced the ability to manage existing guest domains remotely using `libvirt`. It was not possible to create new guests due to the lack of storage management capabilities. In Fedora [[GetVal(DocsDict,BeatsVer)]], new storage management tools allow you to to create and delete storage volumes from a remote host using `libvirt`.
- * PolicyKit integration. Previously, the `virt-manager` application ran as root when managing a local hypervisor. It used `console-helper` to authentication from a desktop session. Running GTK applications as root is generally considered bad practice. By integrating with PolicyKit it is now possible to run `virt-manager` as a regular user.
+ * PolicyKit integration: previously, the `virt-manager` application ran as root when managing a local hypervisor. It used `consolehelper` to authenticate from a desktop session. Running GTK applications as root is bad practice. By integrating with PolicyKit, it is now possible to run `virt-manager` as a regular user.
- * Improved remote authentication. Previously, Fedora introduced support for secure remote management using TLS/SSL and x509 certificates. Fedora [[GetVal(DocsDict,BeatsVer)]] improves remote management capabilities by adding support for authentication against a username/password database, Kerberos domain controller, or system-auth using PAM. This feature applies to all tools using libvirt.
+ * Improved remote authentication: previously, Fedora introduced support for secure remote management using TLS/SSL, and x509 certificates. Fedora [[GetVal(DocsDict,BeatsVer)]] improves remote management capabilities by adding support for authentication against a username and password database, Kerberos domain controller, or system authentication using PAM. This feature applies to all tools using `libvirt`.
- * Introducing a P2V tool, shipping as a Live CD, which allows for the conversion of an existing bare-metal install to a virtual quest.
+ * A new P2V tool, shipping as a Live CD, which allows you to convert a bare-metal install to a virtual guest.
- * Introducing `xenner` - a tool to run the Xen paravirt kernels on top of KVM
- * Introducing paravirtual drivers for storage and network to KVM guests.
+ * A new tool, `xenner`, that allows you to run Xen-paravirtual kernels on top of KVM.
+ * Storage and network paravirtual-drivers for KVM guests.
- * Introducing full support for network and block stats monitoring of QEMU and KVM into `libvirt` and `virt-top`, bringing parity with the previous stats monitoring available only to Xen guests
+ * Full support for monitoring network and block statistics of QEMU and KVM has been added to `libvirt` and `virt-top`, bringing parity with the previous statistic monitoring available only to Xen guests.
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/I18n" by JensPetersen
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by JensPetersen:
http://fedoraproject.org/wiki/Docs/Beats/I18n?action=diff&rev2=131&rev1=130
The comment on the change is:
note on qtimmodules
------------------------------------------------------------------------------
Input methods only start by default on desktops running in an Asian locale. The current locale list is: `as`, `bn`, `gu`, `hi`, `ja`, `kn`, `ko`, `ml`, `mr`, `ne`, `or`, `pa`, `si`, `ta`, `te`, `th`, `ur`, `vi`, `zh`. Use `im-chooser` via ''System -> Preferences -> Personal -> Input Method'' to enable or disable Input method usage on your desktop.
+ ==== Qt immodules ====
+ Currently `qt4` does not yet support immodules other than XIM.
+
==== SCIM hotkeys ====
SCIM now only defines trigger hotkeys for Asian languages
as in the following table:
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/Xorg" by MurrayMcAllister
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by MurrayMcAllister:
http://fedoraproject.org/wiki/Docs/Beats/Xorg?action=diff&rev2=51&rev1=50
The comment on the change is:
minor changes...
------------------------------------------------------------------------------
=== X Configuration Changes ===
- The X.Org [[GetVal(DocsDict,XorgVer)]] X server has been modified to automatically detect and configure most hardware, eliminating the to modify the `/etc/X11/xorg.conf` configuration file. The only hardware configured by default in the `xorg.conf` file written by Anaconda is:
+ The X.Org [[GetVal(DocsDict,XorgVer)]] X server has been modified to automatically detect and configure most hardware, eliminating the need to modify the `/etc/X11/xorg.conf` configuration file. The only hardware configured by default in the `xorg.conf` configuration file written by Anaconda is:
* the graphics driver.
* the keyboard map.
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/Xorg" by MurrayMcAllister
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by MurrayMcAllister:
http://fedoraproject.org/wiki/Docs/Beats/Xorg?action=diff&rev2=50&rev1=49
The comment on the change is:
upper-case Org for X.Org
------------------------------------------------------------------------------
{{{#!html
<h2>X Window System (Graphics)</h2>}}}
- This section contains information related to the X Window System implementation, X.org, provided with Fedora.
+ This section contains information related to the X Window System implementation, X.Org, provided with Fedora.
=== X Configuration Changes ===
- The X.org [[GetVal(DocsDict,XorgVer)]] X server has been modified to automatically detect and configure most hardware, eliminating the to modify the `/etc/X11/xorg.conf` configuration file. The only hardware configured by default in the `xorg.conf` file written by Anaconda is:
+ The X.Org [[GetVal(DocsDict,XorgVer)]] X server has been modified to automatically detect and configure most hardware, eliminating the to modify the `/etc/X11/xorg.conf` configuration file. The only hardware configured by default in the `xorg.conf` file written by Anaconda is:
* the graphics driver.
* the keyboard map.
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/Xorg" by MurrayMcAllister
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by MurrayMcAllister:
http://fedoraproject.org/wiki/Docs/Beats/Xorg?action=diff&rev2=49&rev1=48
The comment on the change is:
try to remove passive voice, lower-case lists...
------------------------------------------------------------------------------
=== X Configuration Changes ===
- The X.org [[GetVal(DocsDict,XorgVer)]] X server has been modified to automatically detect and configure most hardware, eliminating the need for users or administrators to modify the `/etc/X11/xorg.conf` configuration file. The only hardware configured by default in the `xorg.conf` file written by anaconda is:
+ The X.org [[GetVal(DocsDict,XorgVer)]] X server has been modified to automatically detect and configure most hardware, eliminating the to modify the `/etc/X11/xorg.conf` configuration file. The only hardware configured by default in the `xorg.conf` file written by Anaconda is:
- * The graphics driver
+ * the graphics driver.
- * The keyboard map
+ * the keyboard map.
- All other hardware, such as monitors (both LCD and CRT), USB mice, and touchpads should be detected and configured automatically.
+ All other hardware, such as monitors (both LCD and CRT), USB mice, and touchpads, should be detected and configured automatically.
- The X server queries the attached monitor for supported resolution ranges, and attempts to pick the highest resolution available with the correct aspect ratio for the display. Users can set their preferred resolution in ''System > Preferences > Screen Resolution'', and the default resolution for the system can be changed with ''System > Administration > Display''.
+ The X server queries the attached monitor for supported resolution ranges, and attempts to pick the highest resolution available with the correct aspect ratio for the display. Set the preferred resolution in ''System > Preferences > Screen Resolution'', and the default resolution for the system in ''System > Administration > Display''.
- If the `/etc/X11/xorg.conf` configuration file is not present, X also automatically detects the appropriate driver, and assumes a 105-key US keyboard layout.
+ If the `/etc/X11/xorg.conf` configuration file is not present, X automatically detects the appropriate driver, and assumes a 105-key US keyboard layout.
=== Intel Driver notes ===
- Fedora [[GetVal(DocsDict,BeatsVer)]] contains two drivers for Intel integrated graphics controllers:
+ Fedora [[GetVal(DocsDict,BeatsVer)]] contains two drivers for Intel Integrated Graphics Controllers:
- * The default `i810` driver, which contains support for Intel graphics chipsets up to and including i945 and i965
+ * the default `i810` driver, which contains support for Intel graphic chipsets up to and including i945 and i965.
- * The experimental `intel` driver, which contains support for Intel graphics chipsets up to and including i945
+ * the experimental `intel` driver, which contains support for Intel graphic chipsets up to and including i945.
- The `i810` driver is limited to resolutions available in the BIOS. If you need support for non-standard resolutions, such as those used in some widescreen displays, you may want to switch to the `intel` driver. You may switch drivers by using `system-config-display`, available in the menus under ''System > Administration > Display''.
+ The `i810` driver is limited to resolutions available in the BIOS. For support for non-standard resolutions, such as those used in certain widescreen displays, use the `intel` driver. Switch drivers by running the {{{system-config-display}}} command, which is also available in the menu under ''System > Administration > Display''.
- We welcome feedback on the experimental `intel` driver. Please report success in [http://bugzilla.redhat.com/bugzilla/ Bugzilla], attaching the full output of `lspci -vn` for your machine. Given success reports, various chipsets may be switched to use the `intel` driver by default.
+ We welcome feedback on the experimental `intel` driver. Please report success in [http://bugzilla.redhat.com/bugzilla/ Bugzilla], attaching the full output of the {{{lspci -vn}}} command for your machine. Given success reports, various chipsets may be switched to use the `intel` driver by default.
=== Third Party Video Drivers ===
- If you intend to use third party video drivers, refer to the [http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers Xorg third party drivers] page for detailed guidelines.
+ Refer to the [http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers Xorg third-party drivers] page for detailed guidelines on using third-party video drivers.
16 years, 2 months
[Fedora Project Wiki] Update of "Docs/Beats/ProjectOverview" by MurrayMcAllister
by fedorawiki-noreply＠fedoraproject.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification.
The following page has been changed by MurrayMcAllister:
http://fedoraproject.org/wiki/Docs/Beats/ProjectOverview?action=diff&rev2...
The comment on the change is:
adding periods to end of lists
------------------------------------------------------------------------------
In addition to the website, the following mailing lists are available:
- * fedora-list(a)redhat.com, for users of Fedora releases
+ * fedora-list(a)redhat.com, for users of Fedora releases.
- * fedora-test-list(a)redhat.com, for testers of Fedora test releases
+ * fedora-test-list(a)redhat.com, for testers of Fedora test releases.
- * fedora-devel-list(a)redhat.com, for developers, developers, developers
+ * fedora-devel-list(a)redhat.com, for developers, developers, developers.
- * fedora-docs-list(a)redhat.com, for participants of the Documentation Project
+ * fedora-docs-list(a)redhat.com, for participants of the Documentation Project.
To subscribe to any of these lists, send an email with the word "subscribe" in the subject to ''<listname>-request'', where ''<listname>'' is one of the above list names. Alternately, you can subscribe to Fedora mailing lists through the Web interface at http://www.redhat.com/mailman/listinfo/.
16 years, 2 months