backend/common
by Jan Pazdziora
backend/common/rhnLib.py | 4 ----
1 file changed, 4 deletions(-)
New commits:
commit 62fb0afba5a96b2dc1a7442298d5a11199578016
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 17:33:36 2011 +0100
With fix_url gone, exception InvalidUrlError gets unused, removing.
diff --git a/backend/common/rhnLib.py b/backend/common/rhnLib.py
index 9d3d347..3ce97e2 100644
--- a/backend/common/rhnLib.py
+++ b/backend/common/rhnLib.py
@@ -139,10 +139,6 @@ def parseUrl(url):
return tuple(parsed)
-class InvalidUrlError(Exception):
- pass
-
-
def hash_object_id(object_id, factor):
"""Given an object id (assumed to be <label>-<number>), returns the
last few digits for the number. For instance, (812345, 3) should
13 years, 2 months
web/html
by Jan Pazdziora
web/html/javascript/token_channel_select.js | 24 ------------------------
1 file changed, 24 deletions(-)
New commits:
commit 64871ce64c2e7b3077ebd4e42a70d807fb403fae
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 17:22:05 2011 +0100
token_channel_select.js not referenced, removing.
diff --git a/web/html/javascript/token_channel_select.js b/web/html/javascript/token_channel_select.js
deleted file mode 100644
index 5f023ef..0000000
--- a/web/html/javascript/token_channel_select.js
+++ /dev/null
@@ -1,24 +0,0 @@
-function base_channel_selected() {
-
- var i;
- var channels = document.edit_token.token_channels;
- for (i = 0; i < channels.options.length; i++) {
- channels.options[i].selected = false;
- }
-
-// var elems = document.edit_token.elements;
-/* var msg;
-
- for (i = 0; i < elems.length; i++) {
- msg += elems[i].name + "\n";
- }
-
- alert(msg);
-*/
-// document.all.header.disabled = true;
-
-// document.edit_token.token_channels.options.length = 0;
-// document.edit_token.token_channels.optgroups.length = 0;
-// alert("PING!");
-
-}
\ No newline at end of file
13 years, 2 months
rel-eng/comps
by Tomas Lestach
rel-eng/comps/comps-spacewalk-server-fedora14.xml | 1 -
1 file changed, 1 deletion(-)
New commits:
commit 25afc6cdf83b354f4fc40da24ac6be254810db3d
Author: Tomas Lestach <tlestach(a)redhat.com>
Date: Mon Jan 3 17:20:03 2011 +0100
removing PyPAM from F14 compose
diff --git a/rel-eng/comps/comps-spacewalk-server-fedora14.xml b/rel-eng/comps/comps-spacewalk-server-fedora14.xml
index 13938d8..731d836 100644
--- a/rel-eng/comps/comps-spacewalk-server-fedora14.xml
+++ b/rel-eng/comps/comps-spacewalk-server-fedora14.xml
@@ -56,7 +56,6 @@
<packagereq type="default">perl-NOCpulse-Utils</packagereq>
<packagereq type="default">perl-Satcon</packagereq>
<packagereq type="default">ProgAGoGo</packagereq>
- <packagereq type="default">PyPAM</packagereq>
<packagereq type="default">python-gzipstream</packagereq>
<packagereq type="default">quartz</packagereq>
<packagereq type="default">quartz-oracle</packagereq>
13 years, 2 months
web/modules
by Jan Pazdziora
web/modules/rhn/RHN/DB/DataSource/xml/system_search_setbuilder.xml | 310 ----------
1 file changed, 310 deletions(-)
New commits:
commit 4d02ae2892347663786d26c57850474041eaea20
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 17:20:20 2011 +0100
As RHN::DB::Search is gone, system_search_setbuilder.xml is not used, removing.
diff --git a/web/modules/rhn/RHN/DB/DataSource/xml/system_search_setbuilder.xml b/web/modules/rhn/RHN/DB/DataSource/xml/system_search_setbuilder.xml
deleted file mode 100644
index 78c10fd..0000000
--- a/web/modules/rhn/RHN/DB/DataSource/xml/system_search_setbuilder.xml
+++ /dev/null
@@ -1,310 +0,0 @@
-<datasource_modes>
-<mode name="search_simple">
- <query params="user_id, search_string">
-SELECT S.id
- FROM rhnUserServerPerms USP,
- rhnServer S
- WHERE USP.user_id = :user_id
- AND S.id = USP.server_id
- AND ( ( INSTR(UPPER(S.name), UPPER(:search_string)) > 0 )
- OR ( INSTR(UPPER(S.description), UPPER(:search_string)) > 0 ) )
- </query>
-</mode>
-
-<mode name="search_id">
- <query params="user_id, search_string">
-SELECT S.id
- FROM rhnUserServerPerms USP,
- rhnServer S
- WHERE USP.user_id = :user_id
- AND S.id = USP.server_id
- AND ( S.id = :search_string
- OR INSTR(S.id, :search_string) > 0)
- </query>
-</mode>
-
-<mode name="search_custom_info">
- <query params="user_id, search_string">
-SELECT DISTINCT SCDV.server_id
- FROM rhnServerCustomDataValue SCDV,
- rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND USP.server_id = SCDV.server_id
- AND (INSTR(UPPER(SCDV.value), UPPER(:search_string)) > 0 )
- </query>
-</mode>
-
-<mode name="search_snapshot_tag">
- <query params="user_id, search_string">
-SELECT DISTINCT ST.server_id
- FROM rhnTagName TN,
- rhnTag T,
- rhnSnapshotTag ST,
- rhnUserServerPerms USP,
- web_contact wc
- WHERE wc.id = :user_id
- AND USP.user_id = :user_id
- AND T.org_id = wc.org_id
- AND T.name_id = TN.id
- AND (INSTR(UPPER(TN.name), UPPER(:search_string)) > 0 )
- AND USP.server_id = ST.server_id
- AND ST.tag_id = T.id
- </query>
-</mode>
-
-<mode name="search_cpu_model">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnCPU C
- WHERE C.server_id = USP.server_id
- AND INSTR(UPPER(C.model), UPPER(:search_string) ) > 0)
- </query>
-</mode>
-
-<mode name="search_cpu_mhz_lt">
- <query params="user_id, search_value">
-SELECT distinct USP.server_id
- FROM rhnCPU C, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND USP.server_id = C.server_id
- AND ROUND(TO_NUMBER(C.mhz) / (50 / 3)) < (ROUND(:search_value / (50 / 3)))
- </query>
-</mode>
-
-<mode name="search_cpu_mhz_gt">
- <query params="user_id, search_value">
-SELECT distinct USP.server_id
- FROM rhnCPU C, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND USP.server_id = C.server_id
- AND ROUND(TO_NUMBER(C.mhz) / (50 / 3)) > (ROUND(:search_value / (50 / 3)))
- </query>
-</mode>
-
-<mode name="search_ram_lt">
- <query params="user_id, search_value">
-SELECT distinct USP.server_id
- FROM rhnRAM R, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND USP.server_id = R.server_id
- AND R.ram < :search_value
- </query>
-</mode>
-
-<mode name="search_ram_gt">
- <query params="user_id, search_value">
-SELECT distinct USP.server_id
- FROM rhnRAM R, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND USP.server_id = R.server_id
- AND R.ram > :search_value
- </query>
-</mode>
-
-<mode name="search_hwdevice_driver">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnhwdevice HD
- WHERE HD.server_id = USP.server_id
- AND INSTR(UPPER(HD.driver), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_hwdevice_description">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnhwdevice HD
- WHERE HD.server_id = USP.server_id
- AND INSTR(UPPER(HD.description || HD.device), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_hwdevice_device_id">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnhwdevice HD
- WHERE HD.server_id = USP.server_id
- AND INSTR(UPPER(HD.device_id || ' ' || HD.subdevice_id), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_hwdevice_vendor_id">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnhwdevice HD
- WHERE HD.server_id = USP.server_id
- AND INSTR(UPPER(HD.vendor_id || ' ' || HD.subvendor_id), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_dmi_system">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnServerdmi SD, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND SD.server_id = USP.server_id
- AND ( INSTR(UPPER(SD.vendor || SD.system || SD.product), UPPER(:search_string)) > 0 )
- </query>
-</mode>
-
-<mode name="search_dmi_bios">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnServerdmi SD, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND SD.server_id = USP.server_id
- AND INSTR(UPPER(SD.bios_vendor || SD.bios_version || SD.bios_release), UPPER(:search_string) ) > 0
- </query>
-</mode>
-
-<mode name="search_dmi_asset">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnServerdmi SD, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND SD.server_id = USP.server_id
- AND INSTR(UPPER(SD.asset), UPPER(:search_string) ) > 0
- </query>
-</mode>
-
-<mode name="search_hostname">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnServerNetwork SN, rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND SN.server_id = USP.server_id
- AND INSTR(UPPER(SN.hostname), UPPER(:search_string) ) > 0
- </query>
-</mode>
-
-<mode name="search_ip">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServerNetwork SN
- WHERE SN.server_id = USP.server_id
- AND INSTR(SN.ipaddr, :search_string) > 0 )
- </query>
-</mode>
-
-<mode name="search_installed_packages">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnPackageName PN, rhnPackageEVR PE, rhnServerPackage SP
- WHERE SP.server_id = USP.server_id
- AND SP.name_id = PN.id
- AND SP.evr_id = PE.id
- AND INSTR(UPPER(PN.name || '-' || PE.evr.as_vre_simple()), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_needed_packages">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnPackageName PN, rhnPackageEVR PE, rhnPackage P, rhnServerNeededPackageCache SNPC
- WHERE SNPC.server_id = USP.server_id
- AND SNPC.package_id = P.id
- AND P.name_id = PN.id
- AND P.evr_id = PE.id
- AND INSTR(UPPER(PN.name || '-' || PE.evr.as_vre_simple()), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_location_address">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServerLocation SL
- WHERE SL.server_id = USP.server_id
- AND INSTR(UPPER(SL.address1 || ' ' || SL.address2
- || ' ' || SL.city || ', ' || SL.state || ' ' || SL.country),
- UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_location_building">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServerLocation SL
- WHERE SL.server_id = USP.server_id
- AND INSTR(UPPER(SL.building), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_location_room">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServerLocation SL
- WHERE SL.server_id = USP.server_id
- AND INSTR(UPPER(SL.room), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_location_rack">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServerLocation SL
- WHERE SL.server_id = USP.server_id
- AND INSTR(UPPER(SL.rack), UPPER(:search_string)) > 0)
- </query>
-</mode>
-
-<mode name="search_registered">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServer S
- WHERE S.id = USP.server_id
- AND SYSDATE - S.created > :search_string)
- </query>
-</mode>
-
-<mode name="search_checkin">
- <query params="user_id, search_string">
-SELECT USP.server_id
- FROM rhnUserServerPerms USP
- WHERE USP.user_id = :user_id
- AND EXISTS (SELECT 1
- FROM rhnServerInfo SI
- WHERE SI.server_id = USP.server_id
- AND SYSDATE - SI.checkin > :search_string)
- </query>
-</mode>
-
-</datasource_modes>
13 years, 2 months
web/html
by Jan Pazdziora
web/html/network/software/channels/subscribe_confirm.pxt | 46 ---------------
1 file changed, 46 deletions(-)
New commits:
commit 02a072aa942579952ef6a293e95fcfe8aa7e704c
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 17:17:45 2011 +0100
subscribe_confirm.pxt not referenced, removing.
diff --git a/web/html/network/software/channels/subscribe_confirm.pxt b/web/html/network/software/channels/subscribe_confirm.pxt
deleted file mode 100644
index e2031c7..0000000
--- a/web/html/network/software/channels/subscribe_confirm.pxt
+++ /dev/null
@@ -1,46 +0,0 @@
-<?xml version="1.0" encoding="utf8"?>
-<pxt-passthrough>
- <pxt-use class="Grail::Frame" />
- <pxt-use class="Sniglets::Channel" />
- <pxt-use class="Sniglets::Users" />
- <pxt-use class="Sniglets::Lists" />
-
- <grail-canvas-template base="/templates/c.pxt" mode="main_canvas">
-
-<rhn-channel-details>
- <h1><img src="/img/rhn-icon-channels.gif" /> {channel_name}</h1>
-</rhn-channel-details>
-
- <rhn-navi-nav prefix="channel_details" depth="0" file="/nav/channel_detail.xml" style="contentnav" />
-
- <h2>
- <img src="/img/rhn-icon-system.gif" />
- Confirm channel subscription
- </h2>
-
- <div class="page-summary">
- <p>
- The following systems will be subscribed to this channel.
- </p>
- </div>
-
-<pxt-include-late file="/network/components/message_queues/local.pxi" />
-
-<rhn-listview class="Sniglets::ListView::SystemList" mode="in_set">
-
- <formvars>
- <var name="cid" />
- <var name="set_label" type="literal">target_systems_for_channel</var>
- </formvars>
-
- <column name="System" label="server_name" align="left">
- <url>/rhn/systems/details/Overview.do?sid={column:id}</url>
- </column>
-
- <action name="Confirm" label="confirm_channel_subscribe" url="/rhn/channels/ChannelDetail.do" />
-
-</rhn-listview>
-
- </grail-canvas-template>
-</pxt-passthrough>
-
13 years, 2 months
web/html
by Jan Pazdziora
web/html/network/components/release_notes/rhel3as_release_notes.txt | 901 ----------
web/html/network/components/release_notes/rhl9_release_notes.txt | 647 -------
2 files changed, 1548 deletions(-)
New commits:
commit c6a625f4b23f8cec20337165f2afe18bc96e637e
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 17:16:37 2011 +0100
The RHL9 and RHEL 3 release notes are not referenced, removing.
diff --git a/web/html/network/components/release_notes/rhel3as_release_notes.txt b/web/html/network/components/release_notes/rhel3as_release_notes.txt
deleted file mode 100644
index 0f21f19..0000000
--- a/web/html/network/components/release_notes/rhel3as_release_notes.txt
+++ /dev/null
@@ -1,901 +0,0 @@
- Red Hat Enterprise Linux AS 3 Release Notes
-
- Copyright (c) 2003 Red Hat, Inc.
-
- ----------------------------------------------------------------------
-
-Overview
-
- The following topics are covered in these release notes:
-
- o Booting Anaconda
-
- o Installation-related notes
-
- o Notes on input methods
-
- o General notes
-
- o Kernel notes
-
-Booting Anaconda
-
- This section describes the process necessary to boot Anaconda, the Red Hat
- Enterprise Linux installation program.
-
- The first CD-ROM is bootable, and can be used to start the installation
- process. If a CD-ROM-based installation is not desired (for example, if
- you want to install Red Hat Enterprise Linux 3 over a network connection),
- a CD-ROM image file containing only those files required to start the
- installation process is also available as boot.iso in the images/
- directory on the first CD-ROM.
-
-Installation-Related Notes
-
- This section describes issues related to the Red Hat Enterprise Linux
- installation program Anaconda.
-
- o The sequence for processing CD-ROMs has changed for Red Hat Enterprise
- Linux 3. The first CD-ROM is required when booting the installation
- program, and again after subsequent CD-ROMs have been processed.
-
- o The Red Hat Enterprise Linux installation program has the ability to
- test the integrity of the installation media. It works with the CD,
- hard drive ISO, and NFS ISO installation methods. Red Hat recommends
- that you test all installation media before starting the installation
- process, and before reporting any installation-related bugs (many of
- the bugs reported are actually due to improperly-burned CDs). To use
- this test, type linux mediacheck at the boot: prompt.
-
- o Red Hat Enterprise Linux 3 includes a new kernel known as the hugemem
- kernel. This kernel supports a 4GB per process user space (versus 3GB
- for the other kernels), and a 4GB direct kernel space. Using this
- kernel allows Red Hat Enterprise Linux to run on systems with up to
- 64GB of main memory. The hugemem kernel is required in order to use
- all the memory in system configurations containing more than 16GB of
- memory. The hugemem kernel can also benefit configurations running
- with less memory (if running an application that could benefit from
- the larger per process user space, for example.)
-
- To remind you of this issue, the Red Hat Enterprise Linux 3 kernel
- displays a message at boot time if your system configuration contains
- more than 16GB of memory. After the system has booted, the following
- command can be used to see if your system displayed the message:
-
- dmesg | less
-
- NOTE: To provide a 4GB address space for both kernel and user space,
- the kernel must maintain two separate virtual memory address mappings.
- This introduces overhead when transferring from user to kernel space;
- for example, in the case of system calls and interrupts. The impact of
- this overhead on overall performance is highly application dependent.
-
- Also note that, because some drivers were not originally written to
- work well in large-memory environments, Red Hat only supports a
- validated subset of drivers when the hugemem kernel is used. Drivers
- that have been validated by Red Hat for use with the hugemem kernel
- are contained in the kernel-hugemem package. Drivers that have not
- been validated, but are still provided, are available in the
- kernel-hugemem-unsupported RPM. To see the list of drivers in these
- RPMs, use the following command:
-
- rpm -qlp <kernel-rpm>
-
- (Where < kernel-rpm> is the complete filename of the appropriate
- hugemem RPM. Note that these RPMs can be found on CD-ROM #2, in the
- RedHat/RPMS/ directory.)
-
- Should you decide that the hugemem kernel's additional overhead and
- the subset of available drivers present no problem for your hardware
- configuration and system environment, and you wish to use the hugemem
- kernel, you must first install it. To install the hugemem kernel,
- enter the following command while logged in as root:
-
- rpm -ivh <kernel-rpm>
-
- (Where <kernel-rpm> is the name of the hugemem kernel RPM file --
- kernel-hugemem-2.4.21-3.EL.i686.rpm, for example.)
-
- After the installation is complete, reboot your system, making sure to
- select the newly-installed hugemem kernel. After testing your system
- for proper operation while running the hugemem kernel, you should
- modify the /boot/grub/grub.conf file so that the hugemem kernel is
- booted by default.
-
- o Red Hat Enterprise Linux 3 can be installed on the IBM eServer
- xSeries(R) 440 and 445. However, the installation process supports
- configurations containing no more than one chassis, and no attached
- RXE-100 Remote Expansion Enclosures. If your system configuration does
- not conform to these requirements, you can remove any additional
- chassis and/or RXE-100s, and then perform the installation. Once the
- installation is complete, the chassis and/or RXE-100s can then be
- re-installed, and will operate normally under Red Hat Enterprise
- Linux.
-
- o Red Hat Enterprise Linux 3 now includes support for Logical Volume
- Management (LVM). LVM is a means of allocating disk space into one or
- more logical volumes, which can then be used to implement
- easily-resizable file systems.
-
- o While most present-day computers are able to start the installation
- process by booting directly from the first Red Hat Enterprise Linux
- distribution CD, some hardware configurations require the use of a
- boot diskette. If your hardware requires a boot diskette, you should
- be aware of the following change.
-
- Red Hat Enterprise Linux 3 uses a different boot diskette layout than
- previous releases of Red Hat Enterprise Linux. There is now a single
- boot diskette image file (bootdisk.img) that is used to boot all
- systems requiring a boot diskette.
-
- If you are performing anything other than an installation from an IDE
- or USB device, you will be asked to insert a driver diskette created
- from one of the following image files:
-
- . drvnet.img -- For network installations
-
- . drvblock.img -- For SCSI installations
-
- . pcmciadd.img -- For PCMCIA installations
-
- As with previous releases of Red Hat Enterprise Linux, these image
- files can be found in the images/ directory on the first installation
- CD.
-
- o Text mode installations using a serial terminal work best when the
- terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8.
- For Windows, Kermit '95 works well. Non-UTF-8 capable terminals will
- work as long as only English is used during installation. An enhanced
- serial display can be used by passing "utf8" as a boot-time option to
- the installation program. For example:
-
- linux console=ttyS0 utf8
-
- o The firewall configuration screen in the Red Hat Enterprise Linux
- installation program has been simplified. The previous "High",
- "Medium", and "No firewall" settings have been replaced by a more
- straightforward on/off-style control. In addition, the default
- firewall configuration is now stateful, making it more secure. The new
- design also makes it possible for users of NIS authentication, NFS,
- and DNS to deploy a firewall with no additional customization required
- (although customization by specifying port and protocol is still
- possible).
-
- NOTE: This change also applies to the Security Level Configuration
- Tool (redhat-config-securitylevel).
-
- o Installation via VNC is now supported. To initiate a VNC-based
- installation, pass vnc as a boot-time option. If necessary, a password
- can be set by adding "vncpassword=<password>" to the boot-time
- options. The VNC display will be "<host>:1", where <host> is the
- hostname or IP address of the system installing Red Hat Enterprise
- Linux.
-
- It is also possible for the Red Hat Enterprise Linux installation
- program to initiate a connection to a listening VNC client. This is
- done by using the vncconnect boot-time option:
-
- linux vnc vncconnect=<client>[:<port>]
-
- (Where <client> is the hostname or IP address of the system running
- the listening VNC client, and <port> is an optional port specification
- that may be specified if the VNC client is not listening on port 5500,
- which the default port for this type of connection). The following
- examples show the how the boot-time option is specified for standard
- and non-standard ports:
-
- linux vnc vncconnect=pigdog.example.com
-
- linux vnc vncconnect=pigdog.example.com:27910
-
- The system that is to run the listening VNC client must then launch
- the appropriate software to run the VNC client in its listening mode.
- For the VNC client supplied with Red Hat Enterprise Linux 3, the
- following command is sufficient:
-
- vncviewer -listen
-
- In addition, a new kickstart directive has been added to support
- VNC-based installations:
-
- vnc [--password <password>] [--connect <host>[:<port>]]
-
- (Where --password <password> is an optional parameter for specifying a
- VNC password, and [--connect <host>[:<port>]] is an optional parameter
- for specifying the host (and optionally, port) of a system running a
- listening VNC client.
-
- NOTE: If you specify any of the VNC-related boot-time options, they
- will override the corresponding options present in the kickstart file.
-
- o The XFree86 open source vmware video driver is provided as a
- convenience to our customers and is not supported in any way by Red
- Hat, Inc. However, any problem reports with the XFree86 open source
- vmware video driver received by Red Hat will be forwarded to the
- appropriate VMware staff, so that they can investigate. Bug fixes that
- become available for this driver may be reviewed by Red Hat for
- potential inclusion in future errata and products as time permits.
-
-Input Methods
-
- This section contains general information related to the use of input
- methods.
-
- An input method allows users to enter non-Western characters into common
- applications such as word-processing, email and instant messaging. Red Hat
- Enterprise Linux comes with input method support for the following
- languages:
-
- o Chinese (Simplified and Traditional)
-
- o Japanese
-
- o Korean
-
- The following entries describe the use of input methods for each of these
- languages.
-
- o Simplified Chinese
-
- To enter Simplified Chinese characters, you use the miniChinput input
- method. To activate the input method, press Ctrl-Space.
-
- The miniChinput input method supports the following modules:
-
- . intelligent pinyin input
-
- . gbk pinyin input
-
- . shuang pin input
-
- . internal code (gb18030 code) input
-
- The miniChinput package is installed by default if Simplified Chinese
- language support is selected during installation.
-
- o Traditional Chinese
-
- To enter Traditional Chinese characters, you use the xcin input
- method. To activate the input method, press Ctrl-Space. Pressing
- Shift-Ctrl or Ctrl-Alt-Num allows you to change between input modules.
-
- The xcin input method supports the following modules:
-
- . CJ
-
- . Simplex
-
- . Phone
-
- . CantonPing
-
- . Bimsphone
-
- . Bimspinyin
-
- . Array30
-
- . Cantonping (no intonation)
-
- The xcin package is installed by default if Traditional Chinese
- language support is selected during installation.
-
- o Japanese
-
- To enter Japanese characters, you use the Canna, FreeWnn or skk input
- methods. To activate the input method, press Shift-Space.
-
- The following modules are supported:
-
- . romaji
-
- . kana (only Canna -- depends on the configuration file)
-
- The Canna, FreeWnn, and skkinput packages are installed by default if
- Japanese language support is selected during installation.
-
- o Korean
-
- To enter Korean characters, you use the ami input method. To activate
- the input method, press Shift-Space.
-
- The ami package is installed by default if Korean language support is
- selected during installation.
-
-General Notes
-
- This section contains general notes relating to post-installation issues.
-
- o The Apache HTTP server has been updated to version 2.0. The updated
- package replaces version 1.3 and has been renamed to httpd.
-
- . The auth_ldap, mod_put, mod_roaming, mod_auth_any, mod_bandwidth,
- mod_throttle, and mod_dav modules have been removed.
-
- . WebDAV functionality is now included with the httpd package.
-
- NOTE: Some changes to existing configuration files are needed.
- Third-party Apache modules may also require updating. Refer to the
- migration guide at /usr/share/doc/httpd-*/migration.html for more
- details.
-
- o Red Hat Enterprise Linux 3 supports booting over the network using the
- PXE (Pre-Boot Execution Environment) protocol. As in previous releases
- it is possible to configure Red Hat Enterprise Linux 3 as an
- installation server, which makes kernels and image files available for
- the purpose of starting network installations.
-
- Also available in Red Hat Enterprise Linux 3 is support for diskless
- environments. A diskless server (similar to an installation server)
- makes kernels and image files available to diskless client systems.
- After booting, the diskless client systems mount a root file system
- via NFS, eliminating the need for locally-attached storage.
-
- The Network Booting Tool (redhat-config-netboot) is a graphical
- configuration tool allows you to configure both environments.
-
- o The LPRng print spooler has been replaced by CUPS, and the Printer
- Configuration Tool (redhat-config-printer) is the recommended tool for
- configuring it. It may be launched from the System Settings menu,
- using the Printing menu entry.
-
- o The Security Level Configuration Tool (redhat-config-securitylevel)
- has been simplified. The previous "High", "Medium", and "No firewall"
- settings have been replaced by a more straightforward on/off-style
- control. In addition, the default firewall configuration is now
- stateful, making it more secure. The new design also makes it possible
- for users of NIS authentication, NFS, and DNS to deploy a firewall
- with no additional customization required (although customization by
- specifying port and protocol is still possible).
-
- NOTE: This change also applies to the Red Hat Enterprise Linux
- installation program.
-
- o GNOME Print Manager, a simple graphical print queue management tool,
- is now included. It may be launched from the System Tools menu, using
- the Print Manager menu entry. In addition, when a print job is in the
- queue, an icon will appear in the panel's system notification area.
-
- o Red Hat Enterprise Linux 3 includes the setarch utility. Setarch makes
- it possible to change the output produced by the uname command. This
- is useful for a number of reasons, such as running 32-bit applications
- (those written to expect a particular value from uname -m) in 64-bit
- environments.
-
- The format for the setarch command is:
-
- setarch <arch> <command>
-
- (Where <arch> represents the desired architecture string (such as
- i386), and <command> represents the command to be run while the
- architecture has been modified.) Note that <command> can be omitted,
- in which case /bin/sh is run.
-
- In addition, some applications (such as older versions of Java) are
- written to assume a 3GB virtual address space; when run on systems
- with larger virtual address spaces (such as 64-bit AMD64-based
- systems, or 32-bit systems running the hugemem kernel) such
- applications can malfunction. The setarch utility makes it possible to
- emulate a 3GB virtual address space, allowing such applications to run
- properly:
-
- setarch -3 java
-
- o Red Hat Enterprise Linux 3 includes the Native POSIX Thread Library
- (NPTL), a new implementation of POSIX threads for Linux. This library
- provides performance improvements and increased scalability.
-
- This thread library is designed to be binary compatible with the old
- LinuxThreads implementation; however, applications that rely on the
- places where the LinuxThreads implementation deviates from the POSIX
- standard will need to be fixed. Notable differences include:
-
- . Signal handling has changed from per-thread signal handling to POSIX
- process signal handling.
-
- . getpid() returns the same value in all threads.
-
- . Thread handlers registered with pthread_atfork are not run if
- vfork() is used.
-
- . No manager thread.
-
- Applications that are known to have problems using NPTL include:
-
- - Sun JRE prior to version 1.4.1
-
- - IBM JRE
-
- If an application does not work properly with NPTL, it can be run
- using the old LinuxThreads implementation by setting the following
- environment variable:
-
- LD_ASSUME_KERNEL=<kernel-version>
-
- The following versions are available:
-
- . 2.4.19 -- Linuxthreads with floating stacks
-
- . 2.2.5 -- Linuxthreads without floating stacks
-
- Note that software using errno, h_errno, and _res must #include the
- appropriate header file (errno.h, netdb.h, and resolv.h respectively)
- before they are used. However, LD_ASSUME_KERNEL=2.4.19 can be used as
- a workaround until the software can be fixed.
-
- o Multi-threaded C++ programs using thread cancellation might need to be
- forced to use the LinuxThreads library using the
- LD_ASSUME_KERNEL=2.4.19 environment variable setting. Otherwise, the
- program will terminate abnormally if the cancellation is acted on
- (since the generated exception is not caught).
-
- Newly-written C++ code that uses functions from the C runtime
- environment might have to be adjusted to take the cancellation into
- account. This can be done by one of the following methods:
-
- . Not marking the C++ function with throw() (so that callers are aware
- that an exception might be thrown) and by compiling the code with
- exceptions. This is the default compilation option; users should not
- specify -fno-exceptions when compiling.
-
- . Disabling cancellation completely before entering the functions that
- call the cancel-able C runtime functions. This can be done with the
- following call:
-
- pthread_setcancelstate (PTHREAD_CANCEL_DISABLE, &oldstate)
-
- After the C functions are called cancellation can be enabled again
- with the following call:
-
- pthread_setcancelstate (oldstate, NULL)
-
- NOTE: At this point the cancellations are acted upon and therefore the
- function calling pthread_setcancelstate() must be compiled with
- exceptions enabled and must be marked as throwing exceptions.
-
- o A new system message has been added to Red Hat Enterprise Linux 3:
-
- application bug: <app-name>(<app-pid>) has SIGCHLD set to SIG_IGN but
- calls wait(). (see the NOTES section of 'man 2 wait'). Workaround
- activated.
-
- This message (which is displayed on the system console and/or in the
- system log files) indicates that the application is not completely
- standards compliant with respect to its handling of child processes.
- If you notice this message, you should alert the application's
- developers.
-
- o Red Hat Enterprise Linux 3 includes the capability of producing
- Position Independent Executables (PIE) for C, C++, and Java. This
- feature is enabled with the -fpie and -fPIE GCC options to compile,
- which are similar in usage to the -fpic and -fPIC options,
- respectively, and at link time with the -pie option.
-
- o The fileutils, textutils, sh-utils, and stat packages have been
- replaced by the newer coreutils package.
-
- o The RPMs containing the Network Administration Tool
- (redhat-config-network) have changed names and functions. The
- redhat-config-network RPM contains the tool's graphical user
- interface, while redhat-config-network-tui contains the tool itself
- (along with its text-based user interface).
-
- o Support for XHTML1 -- the reformulation of HTML in XML -- has been
- improved. This has been done by adding the xhtml1-dtd package,
- installing the DTDs in the system catalog, and adding native support
- in the libxml2 and xsltproc tools.
-
- o The XML toolkit have been extended to support Relax-NG validation, and
- streaming of large files.
-
- o The OProfile system-wide profiler has been added to Red Hat Enterprise
- Linux 3. OProfile is a programmer's tool for analyzing system
- performance, using special hardware built into many modern computers.
- Documentation for OProfile exists in the oprofile package; after
- installing Red Hat Enterprise Linux 3, issue the command rpm -qd
- oprofile to obtain a listing of the available documentation. Visit the
- OProfile website at http://oprofile.sourceforge.net for more details.
-
- NOTE: The kernel support for OProfile in Red Hat Enterprise Linux 3 is
- based on the backported code from the 2.5 development kernel.
- Therefore, if you refer to the OProfile documentation, keep in mind
- that features listed as being 2.5-specific actually apply to the Red
- Hat Enterprise Linux kernel, even though the kernel version is 2.4.
- Likewise, this means that features listed as being specific to the 2.4
- kernel do not apply to the Red Hat Enterprise Linux kernel.
-
- o At the present time, the X Window System makes use of two font
- subsystems, each with different characteristics:
-
- . The original (15+ year old) subsystem is referred to as the "core X
- font subsystem". Fonts rendered by this subsystem are not
- anti-aliased, are handled by the X server, and have names like:
-
- -misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
-
- The newer font subsystem is known as "fontconfig", and allows
- applications direct access to the font files. Fontconfig is often used
- along with the "Xft" library, which allows applications to render
- fontconfig fonts to the screen with antialiasing. Fontconfig uses more
- human-friendly names like:
-
- Luxi Sans-10
-
- Over time, fontconfig/Xft will replace the core X font subsystem. At
- the present time, applications using the Qt 3 or GTK 2 toolkits (which
- would include KDE and GNOME applications) use the fontconfig and Xft
- font subsystem; most everything else uses the core X fonts.
-
- In the future, Red Hat may support only fontconfig/Xft in place of the
- XFS font server as the default local font access method.
-
- NOTE: One exception to the font subsystem usage outlined above is
- OpenOffice.org, which uses its own font rendering technology.
-
- If you wish to add new fonts to your Red Hat Enterprise Linux 3
- system, you must be aware that the steps necessary depend on which
- font subsystem is to use the new fonts. For the core X font subsystem,
- you must:
-
- 1. Create the /usr/share/fonts/local/ directory (if it does not
- already exist):
-
- mkdir /usr/share/fonts/local/
-
- 2. Copy the new font file into /usr/share/fonts/local/
-
- 3. Update the font information by issuing the following commands (note
- that, due to formatting restrictions, the following commands may
- appear on more than one line; in use, each commands should be entered
- on a single line):
-
- ttmkfdir -d /usr/share/fonts/local/ -o
- /usr/share/fonts/local/fonts.scale
-
- mkfontdir /usr/share/fonts/local/
-
- 4. If you had to create /usr/share/fonts/local/, you must then add it
- to the X font server (xfs) path:
-
- chkfontpath --add /usr/share/fonts/local/
-
- Adding new fonts to the fontconfig font subsystem is more
- straightforward; the new font file only needs to be copied into the
- /usr/share/fonts/ directory (individual users can modify their
- personal font configuration by copying the font file into the
- ~/.fonts/ directory).
-
- After the new font has been copied, use fc-cache to update the font
- information cache:
-
- fc-cache <directory>
-
- (Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
- directories.)
-
- Individual users may also install fonts graphically, by browsing
- fonts:/// in Nautilus, and dragging the new font files there.
-
- NOTE: If the font filename ends with ".gz", it has been compressed
- with gzip, and must be decompressed (with the gunzip command) before
- the fontconfig font subsystem can use the font.
-
- o Due to the transition to the new font system based on fontconfig/Xft,
- GTK+ 1.2 applications are not affected by any changes made via the
- Font Preferences dialog. For these applications, a font can be
- configured by adding the following lines to the file ~/.gtkrc.mine:
-
- style "user-font" {
-
- fontset = "<font-specification>"
-
- }
-
- widget_class "*" style "user-font"
-
- (Where <font-specification> represents a font specification in the
- style used by traditional X applications, such as
- "-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)
-
- o By default, the Sendmail mail transport agent (MTA) does not accept
- network connections from any host other than the local computer. If
- you want to configure Sendmail as a server for other clients, you must
- edit /etc/mail/sendmail.mc and change the DAEMON_OPTIONS line to also
- listen on network devices (or comment out this option entirely using
- the dnl comment delimiter). You must then regenerate
- /etc/mail/sendmail.cf by running the following command (as root):
-
- make -C /etc/mail
-
- Note that you must have the sendmail-cf package installed for this to
- work.
-
- o The default FTP server in Red Hat Enterprise Linux 3 is now vsftpd,
- and runs as a SysV service.
-
- o Change to fdisk's interpretation of partition size multipliers
-
- The fdisk command now has a different interpretation of the size
- multipliers that may be used when creating new disk partitions. The
- size suffixes K, M, and G now refer to multiples of thousands,
- millions, and billions of bytes, respectively. This is more consistent
- with the disk size specifications provided by disk drive
- manufacturers.
-
- Therefore, if a user wants to create a 512MB partition, the size value
- specified with an "M" suffix would be 512*1024*1024 (536,870,912),
- rounded up to a multiple of a million (537,000,000), and then divided
- by a million (537), resulting in a size specification of +537M.
-
- o While compatibility for executables and dynamic shared objects (DSOs,
- also known as shared libraries) created on earlier Red Hat Linux and
- Red Hat Enterprise Linux is supported, the same does not apply to
- object (.o) files. Object files created on earlier versions can be
- used on Red Hat Enterprise Linux 3 to create new executables or DSOs
- only if they were built without including any system header files.
-
- Otherwise, the only way to use these files is to link the object files
- to the compatibility version of glibc (part of the compat-glibc
- package). Any newly-generated object file must use the headers from
- the compatibility package. For example, to compile object files, add
- the following to the beginning of the compiler command line:
-
- -I/usr/lib/i386-redhat-linux7/include
-
- To link the resulting executable or DSO add the following to the
- command line:
-
- -L/usr/lib/i386-redhat-linux7/lib
-
- Any mixture of old object files and those compiled against the current
- system headers can have negative results. Linking old object files
- with the regular system libraries may result in completely unusable
- executables or executables with subtle bugs (such as memory
- corruption).
-
-Kernel Notes
-
- This section contains notes relating to the Red Hat Enterprise Linux 3
- kernel.
-
- o The Red Hat Enterprise Linux 3 kernel makes use of a new kernel
- packaging technique. Due to the almost limitless variety of available
- hardware, it is not possible for Red Hat to fully support all hardware
- components. Therefore, while kernel modules for fully-supported
- hardware remain in the standard kernel packages, a series of new
- unsupported kernel packages are included with Red Hat Enterprise Linux
- 3.
-
- For each kernel package shipped there is a corresponding unsupported
- kernel package. For example, the unsupported kernel package for
- kernel-smp-2.4.21-3.EL.i686.rpm is
- kernel-smp-unsupported-2.4.21-3.EL.i686.rpm.
-
- NOTE: The unsupported kernel packages are not installed by the Red Hat
- Enterprise Linux installation program; therefore, in order to use
- unsupported kernel modules, you must manually install the unsupported
- kernel package corresponding to the kernel your system uses.
-
- After installing the appropriate unsupported kernel package, you must
- use the following command to update the module dependency tree and
- your initrd:
-
- /sbin/new-kernel-pkg --mkinitrd --depmod --install <kernel-version>
-
- (Where <kernel-version> represents the version of the installed
- kernel.)
-
- Drivers contained within the unsupported kernel packages are provided
- on a best-effort basis. This means that updates and upstream fixes may
- or may not be incorporated over time, and are not covered by the same
- support expectations as the fully supported drivers. Custom support
- arrangements covering drivers in the unsupported package may be worked
- out with Red Hat in some situations.
-
- o The Red Hat Enterprise Linux 3 kernel includes more accurate process
- timing functionality. This new process timing mode uses timestamps to
- provide more accurate timing of idle and process times. When enabled,
- this information is available via the usual monitoring tools (such as
- top, vmstat, and procinfo), and the getrusage system call.
-
- To enable timestamp-based process timing, you must boot your system
- using the following boot-time option:
-
- process_timing=<value>
-
- Where <value> can be one or more of the following, with multiple
- values separated by commas:
-
- . irq -- Use timestamps to account for IRQ interrupts
-
- . softirq -- Use timestamps to account for softirq time in the kernel
-
- . process -- Allow processes to enable timestamp-based process timing
- on themselves (It is then disabled for all processes by default)
-
- . all_process -- Force timestamp-based process timing on all processes
- (including the idle tasks)
-
- . everything -- Same as specifying irq,softirq,all_process
-
- If the system is booted with the process option, no processes
- initially have timestamp-based process timing enabled by default.
- However, processes can use the prctl() system call to both determine
- and modify their process timing mode. The system call to determine the
- process timing mode is:
-
- mode = prctl(PR_GET_TIMING, 0, 0, 0, 0);
-
- The system call to set the process timing mode is:
-
- status = prctl(PR_SET_TIMING, <mode>, 0, 0, 0)
-
- (Where <mode> is PR_TIMING_STATISTICAL for enabling the traditional
- process timing mode, or PR_TIMING_TIMESTAMP for enabling
- timestamp-based process timing mode .) Note that enabling one process
- timing mode automatically disables the other.
-
- NOTE: The prctl() system call can only be used on systems booted with
- the process value. Otherwise, the system call will return -EINVAL.
- This includes attempts to disable timestamp-based process timing on
- systems booted with the all_process option.
-
- A child process's timing mode is inherited from its parent; however,
- the child can use the prctl() system call to modify its own process
- timing mode (subject to the conditions outlined in the previous note).
-
- o The BusLogic driver (for certain Mylex SCSI host bus adapters) is
- provided in the standard kernel packages, but it is only supported
- when the kernel is a guest operating system within VMWare(TM) virtual
- machine software. This is because VMWare presents an emulated SCSI
- adapter to the BusLogic driver, and this environment has been
- thoroughly tested and supported by VMWare, Inc. The BusLogic driver is
- not supported on physical SCSI host adapters because this driver has
- not been maintained in the official Linux kernel for several years,
- and has not received extensive testing in the Red Hat Enterprise Linux
- kernel.
-
- o The qla1280 driver (for the Qlogic ISP1x80/1x160 SCSI adapters) has
- not been maintained in the official Linux kernel for many years. As a
- result, although this driver works correctly with the Intel x86
- architecture, it does not work correctly with other architectures.
- Therefore, Red Hat only supports the qla1280 driver on Intel x86
- platforms.
-
- o Systems based on the Intel I865/I875 chipsets and utilizing these
- chipsets' ICH5 integrated AC97 audio functionality may experience a
- failure to produce any sound when running Red Hat Enterprise Linux 3.
-
- The ICH5 integrated AC97 audio subsystem can be identified by
- reviewing the output from the following command:
-
- /sbin/lspci -n
-
- The PCI vendor:device code for the ICH5 AC97 audio is 8086:24d5.
-
- o Systems based on the Intel I865/I875 chipsets and utilizing these
- chipsets' ICH5 Serial ATA (SATA) functionality should configure the
- BIOS settings for their SATA devices to "enhanced" or "native" mode.
- "Legacy" or "combined" mode SATA is supported, but discouraged.
-
- NOTE: Not all BIOS implementations offer the ability to change these
- settings.
-
- o New kernel support has been added to provide IPv6 capabilities. This
- support is consistent with the upstream 2.6-based implementation as of
- 2.6.0-test3.
-
- Note that Red Hat will not be implementing additional IPv6 features
- (such as any of the draft standards for Mobile IP) for this release of
- Red Hat Enterprise Linux; our goal is to focus exclusively on bugs in
- existing features.
-
- o EA (Extended Attributes) and ACL (Access Control Lists) functionality
- is now available for ext3 file systems. In addition, ACL functionality
- is available for NFS.
-
- Red Hat Enterprise Linux 3 contains a kernel providing EA and ACL
- support for the ext3 file system. Protocol extensions were also added
- to NFS to support ACL-related operations for NFS-exported file
- systems.
-
- To enable ACLs on a locally-mounted file system, the file system must
- be mounted with the -o acl mount option. By default, the NFS server
- makes use of ACLs if the underlying file system supports them. To
- disable this feature, you must specify the no_acl export option.
-
- EAs are used intrinsically for ACL support. To use EAs separately, the
- file system must be mounted with the -o user_xattr mount option.
-
- The support for this comes in several packages:
-
- . kernel -- Provides support for storing EAs and ACLs on disk for ext3
- file systems, as well the system calls to manipulate EAs and ACLs.
- Finally, the kernel package provides the mechanisms to enforce ACLs on
- file access.
-
- . e2fsprogs -- Includes knowledge of the new on-disk extended
- attribute formats so that fsck can check file systems using the new
- feature.
-
- . attr, libattr -- Provides access to extended attributes attached to
- files.
-
- . acl, libacl -- Provides tools to set, modify, and query the ACLs set
- on files.
-
- . libattr-devel, libacl-devel -- Libraries and include files to build
- programs using the acl and attr libraries.
-
- . star -- An archiving tool which can create and unpack both tar and
- pax format archives, and which can backup and restore EAs and ACLs.
-
- NOTE: The options available for star are not completely equivalent
- with those available for tar; therefore, make sure you review the star
- man page.
-
- . samba -- Samba can export ACL functionality in this release. Refer
- to the samba documentation for information on how to enable this in
- your configuration.
-
- In addition, the coreutils package has been updated so that the cp and
- mv commands copy the ACLs and EAs associated with a file.
-
- For more information on setting and reading ACLs, refer to the setfacl
- and getfacl man pages. General information about ACLs can be found in
- the acl man page.
-
- NOTE: The normal tar and dump commands will not backup ACLs and EAs.
-
- Compatibility with older systems:
-
- Any ext3 file system that has not had any ACLs or EAs set on it will
- work unchanged on older kernels, and can be checked using older
- e2fsprogs utilities.
-
- Once an EA or an ACL has been set on any file on a given file system,
- that file system will acquire the ext_attr attribute. This attribute
- can be observed by using the following command:
-
- tune2fs -l <filesystemdevice>
-
- A file system that has acquired the ext_attr attribute can be mounted
- with older kernels, but obviously those kernels are incapable of
- enforcing any ACLs that have been set.
-
- NOTE: Older versions of the file system checking program e2fsck refuse
- to check any file system with the ext_attr attribute. This corresponds
- to versions of the e2fsprogs package prior to 1.22.
-
- o The Red Hat Enterprise Linux 3 kernel now includes support for NFS
- over TCP. To use NFS over TCP, you must include the "-o tcp" option to
- mount when mounting the NFS-exported file system on the client system.
-
- NOTE: The default transport protocol for NFS remains UDP. Use the
- mount command with the "-o tcp" option to mount an NFS-exported file
- system using TCP; otherwise, UDP will be used by default.
-
- o In this kernel, the following command has been added to scan for new
- devices on all attached SCSI host adapters:
-
- echo "scsi scan-new-devices" > /proc/scsi/scsi
-
- This is currently a non-standard addition. In future kernels a
- different parameter may be used to provide the same capability, or the
- semantics of the same parameter (scan-new-devices) may change, as Red
- Hat tracks the official Linux kernel in this area.
-
- o Change in permission semantics for user-mode memory locking
-
- Red Hat Enterprise Linux 3 now allows non-root processes to use
- user-mode memory locking system calls within the bounds of their
- RLIMIT_MEMLOCK resource limit. The default limit is one physical page
- per process. Limits can be reassigned by the system administrator on a
- per user-id, per group-id, or system-wide basis via the
- /etc/security/limits.conf file. Root processes are no longer
- constrained by this resource limit.
-
- The system calls affected by this change in semantics are mlock(2),
- munlock(2), mlockall(2), munlockall(2), and shmctl(2).
-
- ( x86 )
diff --git a/web/html/network/components/release_notes/rhl9_release_notes.txt b/web/html/network/components/release_notes/rhl9_release_notes.txt
deleted file mode 100644
index 2bdc3e6..0000000
--- a/web/html/network/components/release_notes/rhl9_release_notes.txt
+++ /dev/null
@@ -1,647 +0,0 @@
-
- Copyright (c) 2003 Red Hat, Inc.
-
- ----------------------------------------------------------------------
-
-Hardware Requirements
-
- The following information represents the minimum hardware requirements
- necessary to successfully install Red Hat Linux 9:
-
- CPU:
-
- - Minimum: Pentium-class
-
- - Recommended for text-mode: 200 MHz Pentium-class or better
-
- - Recommended for graphical: 400 MHz Pentium II or better
-
- Hard Disk Space (NOTE: Additional space will be required for user data):
-
- - Custom Installation (minimum): 475MB
-
- - Server (minimum): 850MB
-
- - Personal Desktop: 1.7GB
-
- - Workstation: 2.1GB
-
- - Custom Installation (everything): 5.0GB
-
- Memory:
-
- - Minimum for text-mode: 64MB
-
- - Minimum for graphical: 128MB
-
- - Recommended for graphical: 192MB
-
- Note that the compatibility/availability of other hardware components
- (such as video and network cards) may be required for specific
- installation modes and/or post-installation usage. For more information
- about hardware compatibility, see the Red Hat Linux Hardware Compatibility
- List at http://hardware.redhat.com/hcl/
-
-Installation-Related Notes
-
- This section outlines those issues that are related to Anaconda (the Red
- Hat Linux installation program) and installing Red Hat Linux 9 in
- general.
-
- o The Red Hat Linux installation program has the ability to test the
- integrity of the installation media. It works with the CD, DVD, hard
- drive ISO, and NFS ISO installation methods. Red Hat recommends that
- you test all installation media before starting the installation
- process, and before reporting any installation-related bugs (many of
- the bugs reported are actually due to improperly-burned CDs). To use
- this test, type linux mediacheck at the boot: prompt.
-
- o While most present-day computers are able to start the installation
- process by booting directly from the first Red Hat Linux distribution
- CD, some hardware configurations require the use of a boot diskette.
- If your hardware requires a boot diskette, you should be aware of the
- following change.
-
- Red Hat Linux 9 uses a different boot diskette layout than
- previous releases of Red Hat Linux. There is now a single boot
- diskette image file (bootdisk.img) that is used to boot all systems
- requiring a boot diskette.
-
- If you are performing anything other than an installation from an IDE
- or USB device, you will be asked to insert a driver diskette created
- from one of the following image files:
-
- - drvnet.img - For network installations
-
- - drvblock.img - For SCSI installations
-
- - pcmciadd.img - For PCMCIA installations
-
- As with previous releases of Red Hat Linux, these image files can be
- found in the images/ directory on the first installation CD.
-
- o Also in the images/ directory is the boot.iso file. This file is an
- ISO image that can be used to boot the Red Hat Linux installation
- program. It is a handy way to start network-based installations
- without having to use multiple diskettes. To use boot.iso, your
- computer must be able to boot from its CD-ROM drive, and its BIOS
- settings must be configured to do so. You must then burn boot.iso onto
- a recordable/rewriteable CD-ROM.
-
- o The rescue mode environment (accessed by booting with the "linux
- rescue" boot-time command) has been enhanced. Numerous requested
- utilities have been added, and there is now support for activating
- network interfaces. Commands needed for SCSI tape support are also
- available. Please test this environment and send us your feedback.
-
- If you chose to mount an existing installation in rescue mode and you
- have man pages installed on that existing installation, the man
- command will work while in rescue mode.
-
- o The Red Hat Linux installation program now detects existing Red Hat
- products on your system, and will prompt you to select the product you
- would like to upgrade. You will also have the option of performing a
- complete re-installation of the system instead of upgrading. Please
- report any problems you may experience with this new feature.
-
- If the contents of your /etc/redhat-release file has been changed from
- the default, your Red Hat Linux installation may not be found when
- attempting an upgrade to Red Hat Linux 9.
-
- You can relax some of the checks against this file by entering the
- following at the boot: prompt:
-
- linux upgradeany
-
- Use the upgradeany option only if your existing Red Hat Linux
- installation was not detected.
-
- o isolinux is now used for booting the Red Hat Linux installation CD. If
- you have problems booting from the CD, you can write the
- images/bootdisk.img image to a diskette according to the directions in
- the Red Hat Linux Installation Guide.
-
- o During a graphical installation, you can now press SHIFT-Print Screen
- and a screenshot of the current installation screen will be taken.
- These are stored in the following directory:
-
- /root/anaconda-screenshots/
-
- The screenshots can be accessed once the newly-installed system is
- rebooted.
-
- o The parted disk partition manipulation program has been upgraded to
- version 1.6.
-
- o Users of Red Hat Linux 6.2 that want to upgrade their system to Red
- Hat Linux 9 must first have all errata updates applied before
- starting the upgrade process. The most straightforward way to
- accomplish this is to use Red Hat Network. A Red Hat Linux 6.2 system
- that is not completely up-to-date will not upgrade successfully to Red
- Hat Linux 9.
-
- o Text mode installations using a serial terminal work best when the
- terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8.
- For Windows, Kermit '95 works well. Non-UTF-8 capable terminals will
- work as long as only English is used during installation. An enhanced
- serial display can be used by passing "utf8" as a boot-time option to
- the installation program. For example:
-
- linux console=ttyS0 utf8
-
-General Notes
-
- This section describes post-installation issues.
-
- o There have been issues observed when upgrading Red Hat Linux 6.<x>,
- 7.<x>, 8.0, and 9 systems running Ximian GNOME. The issue is
- caused by version overlap between the official Red Hat Linux RPMs and
- the Ximian RPMs. This configuration is not supported by Red Hat. You
- have several choices in resolving this issue:
-
- 1) You may remove Ximian GNOME from your Red Hat Linux system prior to
- upgrading Red Hat Linux.
-
- 2) You may upgrade Red Hat Linux, and then immediately reinstall
- Ximian GNOME.
-
- 3) You may upgrade Red Hat Linux, and then immediately remove all
- remaining Ximian RPMs, and replace them with the corresponding Red Hat
- Linux RPMs.
-
- You must resolve the version overlap using one of the above choices.
- Failure to do so will result in an unstable GNOME configuration.
-
- o There has been some confusion regarding font-related issues under the
- X Window System in recent versions of Red Hat Linux. At the present
- time, there are two font subsystems, each with different
- characteristics:
-
- - The original (15+ year old) subsystem is referred to as the "core X
- font subsystem". Fonts rendered by this subsystem are not
- anti-aliased, are handled by the X server, and have names like:
-
- -misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
-
- The newer font subsystem is known as "fontconfig", and allows
- applications direct access to the font files. Fontconfig is often used
- along with the "Xft" library, which allows applications to render
- fontconfig fonts to the screen with antialiasing. Fontconfig uses more
- human-friendly names like:
-
- Luxi Sans-10
-
- Over time, fontconfig/Xft will replace the core X font subsystem. At
- the present time, applications using the Qt 3 or GTK 2 toolkits (which
- would include KDE and GNOME applications) use the fontconfig and Xft
- font subsystem; most everything else uses the core X fonts.
-
- In the future, Red Hat may support only fontconfig/Xft in place of the
- XFS font server as the default local font access method.
-
- NOTE: Two exceptions to the font subsystem usage outlined above are
- OpenOffice.org (which uses its own font rendering technology), and
- Mozilla (which uses fontconfig, but not GTK 2).
-
- If you wish to add new fonts to your Red Hat Linux 9 system,
- you must be aware that the steps necessary depend on which font
- subsystem is to use the new fonts. For the core X font subsystem, you
- must:
-
- 1. Create the /usr/share/fonts/local/ directory (if it doesn't already
- exist):
-
- mkdir /usr/share/fonts/local/
-
- If you had to create /usr/share/fonts/local/, you must then add it to
- the X font server (xfs) path:
-
- chkfontpath --add /usr/share/fonts/local/
-
- 2. Copy the new font file into /usr/share/fonts/local/
-
- 3. Update the font information by issuing the following command:
-
- ttmkfdir -d /usr/share/fonts/local/ -o
- /usr/share/fonts/local/fonts.scale
-
- 4. Reload the xfs font server using the following command:
-
- service xfs reload
-
- Adding new fonts to the fontconfig font subsystem is more
- straightforward; the new font file only needs to be copied into the
- /usr/share/fonts/ directory (individual users can modify their
- personal font configuration by copying the font file into the
- ~/.fonts/ directory).
-
- After the new font has been copied, use fc-cache to update the font
- information cache:
-
- fc-cache <directory>
-
- (Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
- directories.)
-
- Individual users may also install fonts graphically, by browsing
- fonts:/// in Nautilus, and dragging the new font files there.
-
- NOTE: If the font filename ends with ".gz", it has been compressed
- with gzip, and must be decompressed (with the gunzip command) before
- the fontconfig font subsystem can use the font.
-
- o Due to the transition to the new font system based on fontconfig/Xft,
- GTK+ 1.2 applications are not affected by any changes made via the
- Font Preferences dialog. For these applications, a font can be
- configured by adding the following lines to the file ~/.gtkrc.mine:
-
- style "user-font" {
-
- fontset = "<font-specification>"
-
- }
-
- widget_class "*" style "user-font"
-
- (Where <font-specification> represents a font specification in the
- style used by traditional X applications, such as
- "-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)
-
- o New features in XFree86 include:
-
- - Xcursor - New mouse cursor code, allowing color, antialiased, alpha
- blended (translucency), animated, themeable, multi-size mouse pointers
- to be used.
-
- - ATI Radeon 9000, 9100, FireGL 8700, 8800 3D/2D/Xv support is now
- available. ATI Radeon 9500 Pro and 9700 Pro, as well as ATI FireGL X1
- and Z1 are now supported 2D-only. Support for over 30 additional ATI
- Rage 128 chipsets have been added to this release, which should cover
- all existing Rage 128 chipsets now.
-
- - Intel i845, i852, i855, and i865 integrated video support
- (2D/3D/Xvideo), and improved Intel i830 video support. The Intel video
- driver has been completely restructured and largely rewritten to be
- much more robust, and support more hardware. Many bugs have been
- fixed, as well as many workarounds for broken laptop and motherboard
- BIOSs that limit memory to 1Mb.
-
- - New support for NVIDIA GeForce 4, nForce, GeForce 2 Go, and various
- other NVIDIA hardware. Also, the nv driver has been enhanced to
- attempt to autodetect unknown NVIDIA chips that aren't officially
- supported, but can probably be coaxed to work anyway (albeit not
- officially supported) by treating them similarly to one of the other
- supported chips in the same family. The nv driver, as in previous
- releases, remains 2D only.
-
- - At the time these release notes were finalized, NVIDIA's binary-only
- accelerated 3D drivers are not currently compatible with Red Hat Linux
- 9. NVIDIA is aware of the problem; watch the NVIDIA website
- for updates regarding this situation.
-
- - Updated Savage driver which supports the newest Savage video
- chipsets, and fixes various bugs.
-
- - A brand new driver for the National Semiconductor Geode chipset,
- nsc, is provided.
-
- - Many other video driver updates and improvements have been made.
-
- - Many new input drivers including fpit, palmax, ur98 and others have
- been added.
-
- o By default, the Sendmail mail transport agent (MTA) does not accept
- network connections from any host other than the local computer. If
- you want to configure Sendmail as a server for other clients, you must
- edit /etc/mail/sendmail.mc and change the DAEMON_OPTIONS line to also
- listen on network devices (or comment out this option entirely using
- the dnl comment delimiter). You must then regenerate
- /etc/mail/sendmail.cf by running the following command (as root):
-
- make -C /etc/mail
-
- Note that you must have the sendmail-cf package installed for this to
- work.
-
- o CUPS is now the default print spooler, and redhat-config-printer is
- the recommended tool for configuring it. It may be launched from the
- System Settings menu, using the Printing menu entry. LPRng is still
- provided, and upgrades from previous installations using LPRng will
- continue to use it.
-
- o GNOME Print Manager, a simple graphical print queue management tool,
- is now included. It may be launched from the System Tools menu, using
- the Print Manager menu entry. In addition, when a print job is in the
- queue, an icon will appear in the panel's system notification area.
-
- o Red Hat Linux 9 includes the Native POSIX Thread Library
- (NPTL), a new implementation of POSIX threads for Linux. This library
- provides performance improvements and increased scalability for i686
- or better processors.
-
- This thread library is designed to be binary compatible with the old
- LinuxThreads implementation; however, applications that rely on the
- places where the LinuxThreads implementation deviates from the POSIX
- standard will need to be fixed. Notable differences include:
-
- - Signal handling has changed from per-thread signal handling to POSIX
- process signal handling.
-
- - getpid() returns the same value in all threads.
-
- - Thread handlers registered with pthread_atfork are not run if
- vfork() is used - no manager thread
-
- Applications that are known to have problems using NPTL include:
-
- - Sun JRE prior to version 1.4.1
-
- - IBM JRE
-
- If an application does not work properly with NPTL, it can be run
- using the old LinuxThreads implementation by setting the following
- environment variable:
-
- LD_ASSUME_KERNEL=<kernel-version>
-
- The following versions are available:
-
- - 2.4.1 - Linuxthreads with floating stacks
-
- - 2.2.5 - Linuxthreads without floating stacks
-
- NPTL support for all dynamically-linked applications can be disabled
- by using the following boot-time option:
-
- nosysinfo
-
- o A new system message has been added to Red Hat Linux 9:
-
- application bug: <app-name>(<app-pid>) has SIGCHLD set to SIG_IGN but
- calls wait(). (see the NOTES section of 'man 2 wait'). Workaround
- activated.
-
- This message (which is displayed on the system console and/or in the
- system log files) indicates that the application is not completely
- standards compliant with respect to its handling of child processes.
- If you see this message, you should alert the application's
- developers.
-
- o Python has been compiled with UCS4 support (Unicode characters
- represented on 4 bytes) as opposed to UCS2. UCS4 allows one to
- represent characters outside of the Basic Multilingual Plane. Certain
- third-party libraries may stop working because of this change;
- recompiling these libraries should be sufficient to resolve the
- problem. Please note that "pure" python modules (whose code is written
- in python) or compiled modules that do not directly use Unicode are
- not affected by this change.
-
- o The fileutils, textutils, sh-utils, and stat packages have been
- replaced by the newer coreutils package.
-
- o The RPMs containing the Network Administration Tool have changed names
- and functions. The RPM redhat-config-network contains the tool's
- graphical user interface, while redhat-config-network-tui contains the
- tool itself (along with its text-based user interface).
-
- o Support for XHTML1 - the reformulation of HTML in XML - has been
- improved. This has been done by adding the xhtml1-dtd package,
- installing the DTDs in the system catalog, and adding native support
- in the libxml2 and xsltproc tools.
-
- o The redhat-switchmail command and package have been renamed
- redhat-switch-mail. The redhat-switchmail-gnome package has been
- renamed redhat-switch-mail-gnome.
-
- o The Oprofile system-wide profiler has been added to Red Hat Linux
- 9. OProfile is a programmer's tool for analyzing system
- performance, using special hardware built into many modern computers.
- Documentation for OProfile exists in the oprofile package; after
- installing Red Hat Linux 9, issue the command rpm -qd oprofile
- to obtain a listing of the available documentation. See the OProfile
- website at http://oprofile.sourceforge.net for more details.
-
- o GDB has been enhanced to allow debugging information for applications
- to be read from separate files. This makes it possible to extract
- debugging information from binaries and place them in a supplemental
- package. During the development of Red Hat Linux 9,
- "debuginfo" packages were generated for nearly every package by
- implementing special RPM macros. By default, the RPM macro
- configuration in Red Hat Linux 9 generates "debuginfo"
- packages. If you are building packages and do not want to generate
- "debuginfo" packages, add the following to your ~/.rpmmacros file:
-
- %define debug_package %{nil}
-
-Package Changes
-
- The following packages have been added to Red Hat Linux 9:
-
- - bluez-libs - Libraries for Bluetooth(TM) utility programs
-
- - bluez-utils - Bluetooth utility programs
-
- - bogl - Graphics library for framebuffers; used by the Red Hat Linux
- installation program
-
- - ckermit - Replaces gkermit
-
- - coreutils - Replaces fileutils, textutils, sh-utils and stat
-
- - desktop-printing - Drag-and-drop printing and print job icon
-
- - devlabel - Support for persistent storage device access
-
- - elfutils - Replaces libelf
-
- - fontilus - Font viewer for Nautilus
-
- - fonts-hebrew - Hebrew fonts
-
- - gnome-icon-theme - Icons for base GNOME environment
-
- - gnome-themes - Collection of themes for GNOME environment
-
- - gstreamer - Multimedia framework library
-
- - gstreamer-plugins - Input and output plugins for gstreamer
-
- - gthumb - Graphics viewer
-
- - hpoj - HP OfficeJet support
-
- - jwhois - Replaces whois
-
- - libgnomeprint22 - Updated libraries
-
- - libgnomeprintui22 - Updated libraries
-
- - libgsf - Library for reading/writing structured files
-
- - nautilus-cd-burner - CD burning support for Nautilus
-
- - nautilus-media - Audio playing support for Nautilus
-
- - openssl096b - Compatibility maintenance package
-
- - postgresql-odbc - ODBC support for PostgreSQL
-
- - postgresql72-libs - PostgreSQL 7.2 compatibility libraries
-
- - printman - Print queue management
-
- - pyorbit - Replaces orbit-python
-
- - redhat-config-samba - Samba configuration tool
-
- - redhat-switch-mail - Renamed from redhat-switchmail
-
- - soup - SOAP implementation library
-
- - startup-notification - Support for busy cursor
-
- - subversion - Version control system
-
- - tsclient - GUI client for VNS and Windows Terminal Server
-
- - ttmkfdir - Separated from XFree86
-
- - vconfig - VLAN (802.1q) configuration program
-
- - xhtml1-dtds - XHTML1 support
-
- The following packages have been removed from Red Hat Linux 9:
-
- - WindowMaker - Developer resource constraints
-
- - Xft - Integrated into XFree86
-
- - Xtest - No longer required by Anaconda
-
- - anonftp - functionality pulled into vsftpd package
-
- - bdflush - No longer required (needed by 2.2 kernels only)
-
- - fileutils - Replaced by coreutils
-
- - fortune-mod - Unclear copyright status
-
- - gkermit - Replaced by ckermit
-
- - ipvsadm - No longer part of Red Hat Linux product profile
-
- - kbdconfig - Replaced by redhat-config-keyboard
-
- - kernel-uml - Experimental package, removed
-
- - ksymoops - No longer required by kernel
-
- - libelf - Replaced by elfutils
-
- - librpm404 - No longer required compatibility library
-
- - libxml10 - No longer required compatibility library
-
- - mouseconfig - Replaced by redhat-config-mouse
-
- - openldap12 - No longer required compatibility library
-
- - openssl095a - No longer required compatibility library
-
- - orbit-python - Replaced by pyorbit
-
- - php-dbg-base - Not used within distribution
-
- - php-dbg-client - Not used within distribution
-
- - php-dbg-server - Not used within distribution
-
- - redhat-switchmail - Renamed to redhat-switch-mail
-
- - rhmask - Red Hat no longer distributes rhmask files
-
- - rpm2html - Deprecated by author
-
- - sh-utils - Replaced by coreutils
-
- - stat - Replaced by coreutils
-
- - textutils - Replaced by coreutils
-
- - timeconfig - Replaced by redhat-config-date
-
- - whois - Replaced by jwhois
-
- - wine - Developer resource constraints
-
- - wmapm - Part of Windowmaker removal
-
- - wmclock - Part of Windowmaker removal
-
- - wmix - Part of Windowmaker removal
-
- - wu-ftpd - vsftpd is the recommended FTP daemon
-
- - xtoolwait - Not used within distribution
-
- The following packages have been deprecated, and may be removed from a
- future release of Red Hat Linux:
-
- - pine - License-related issues
-
- - LPRng - CUPS is the recommended printing solution
-
- - Glide3 - Multi-platform issues
-
- - lilo - GRUB is the recommended bootloader
-
- - sndconfig - No longer required by mainstream hardware
-
- - ncpfs - No longer part of Red Hat Linux product profile
-
- - mars-nwe - No longer part of Red Hat Linux product profile
-
-Kernel Notes
-
- This section covers issues that are related to the Red Hat Linux 9
- kernel.
-
- o Special Note: The ACL support added to the kernel in the first two
- public beta releases proved to be unstable and caused the kernel to
- regress. Red Hat has therefore removed that ACL support from the
- kernel for Red Hat Linux 9. Kernel engineers will continue
- work on improving the ACL support, which will be available in a future
- release. The attr and acl packages needed to support ACLs are still
- included to make it easier for users and developers who wish to test
- ACLs. Red Hat may, at our discretion, provide ACL support for this
- release of Red Hat Linux by means of an upgrade, if future testing
- demonstrates that the ACL support has sufficiently improved in
- quality.
-
- o The apic boot-time option allowing installation on systems with the
- Intel 440GX chipset has been removed because it caused a conflict with
- many newer systems: it caused SMM (System Management Mode) not to
- function, or to function incorrectly, causing installation on those
- systems to fail. Removing the apic boot-time option enables these
- newer systems to install successfully.
-
- A different workaround has been provided that allows at least some
- systems with the Intel 440GX chipset to boot; this workaround is
- automatically enabled, and requires no action on your part. If you
- have an Intel 440GX-based system and are unable to install Red Hat
- Linux 9 but a previous release of Red Hat Linux installs
- correctly, please file a bug report, and include the output (running
- on the previous release, of course) of the dmidecode program, run as
- root, with your bug report. Note however, that it will not be possible
- to install Red Hat Linux 9 at all.
-
- Systems with the 440GX chipset are supported only on a best-effort
- basis. Therefore, we welcome bug reports regarding systems with the
- 440GX chipset, but may or may not be able to resolve them.
-
- o The kernel support for the new NPTL feature changes several internal
- kernel programming interfaces significantly. As a result, several
- external kernel modules may not compile without modifications to match
- the new interfaces. Examples currently include the NVIDIA and ATI 3D
- modules, as well as any other modules that use kernel threads and/or
- signals.
13 years, 2 months
web/html
by Jan Pazdziora
web/html/javascript/countdown.js | 16 ----------------
1 file changed, 16 deletions(-)
New commits:
commit abfd7b3361512e0ff754c15288939ea526472814
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 17:05:43 2011 +0100
countdown.js does not seem to be used, removing.
diff --git a/web/html/javascript/countdown.js b/web/html/javascript/countdown.js
deleted file mode 100644
index 55331b6..0000000
--- a/web/html/javascript/countdown.js
+++ /dev/null
@@ -1,16 +0,0 @@
-
-<!-- In order to use this script, you must define var secondsUntilRefresh in the head of your own document -->
-function execute() {
- if(secondsUntilRefresh == 0)
- window.location= pageToRefreshTo;
-
- else
- secondsUntilRefresh -= 1;
-
- if(secondsUntilRefresh % 60 >= 10)
- document.getElementById("cntdwn").innerHTML = Math.floor(secondsUntilRefresh / 60) + ":" + (secondsUntilRefresh % 60);
- else
- document.getElementById("cntdwn").innerHTML = Math.floor(secondsUntilRefresh / 60) + ":0" + (secondsUntilRefresh % 60);
- window.setTimeout("execute()", 1000);
-}
-
13 years, 2 months
2 commits - web/modules
by Jan Pazdziora
web/modules/pxt/PXT/Debug.pm | 16 ---------
web/modules/rhn/RHN/DB/DataSource/xml/contact_group_queries.xml | 17 ----------
2 files changed, 1 insertion(+), 32 deletions(-)
New commits:
commit e5d2615ca7d8da8d4648d74a3c96f1f12ade7289
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 16:58:36 2011 +0100
Since RHN::DataSource::ContactGroup is gone, contact_group_queries.xml is unused, removing.
diff --git a/web/modules/rhn/RHN/DB/DataSource/xml/contact_group_queries.xml b/web/modules/rhn/RHN/DB/DataSource/xml/contact_group_queries.xml
deleted file mode 100644
index 02469aa..0000000
--- a/web/modules/rhn/RHN/DB/DataSource/xml/contact_group_queries.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<datasource_modes>
-
-
-<!-- query to retrieve the list of all contact groups
- for the specified org.
--->
-<mode name="orgs_contact_groups">
- <query params="org_id">
-SELECT recid id, contact_group_name
-FROM rhn_contact_groups
-WHERE customer_id = :org_id
-ORDER BY contact_group_name
- </query>
-</mode>
-
-
-</datasource_modes>
commit eec3cf4f2f84a738cc1cc67f773785c6125e4ebd
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Mon Jan 3 16:45:43 2011 +0100
PXT::Debug::log_dump not used anywhere, removing.
diff --git a/web/modules/pxt/PXT/Debug.pm b/web/modules/pxt/PXT/Debug.pm
index a00ba57..7bf9b58 100644
--- a/web/modules/pxt/PXT/Debug.pm
+++ b/web/modules/pxt/PXT/Debug.pm
@@ -1,5 +1,5 @@
#
-# Copyright (c) 2008--2010 Red Hat, Inc.
+# Copyright (c) 2008--2011 Red Hat, Inc.
#
# This software is licensed to you under the GNU General Public License,
# version 2 (GPLv2). There is NO WARRANTY for this software, express or
@@ -18,7 +18,6 @@ package PXT::Debug;
use strict;
use PXT::Config ();
-use Data::Dumper ();
sub log {
my $class = shift;
@@ -33,18 +32,5 @@ sub log {
}
}
-sub log_dump {
- my $class = shift;
- my $level = shift;
- my @structs = @_;
-
- if ($level < PXT::Config->get('debug')) {
- my (undef, $file, $line) = caller;
- my @frame = caller(1);
-
- warn sprintf("$frame[3] ($file:$line): %s\n", Data::Dumper->Dump(\@structs));
- }
-}
-
1;
13 years, 2 months
Changes to 'refs/tags/yum-rhn-plugin-1.3.2-1'
by Miroslav Suchý
Tag 'yum-rhn-plugin-1.3.2-1' created by Miroslav Suchý <msuchy(a)redhat.com> at 2011-01-03 15:42 +0000
Tagging package [yum-rhn-plugin] version [1.3.2-1] in directory [client/rhel/yum-rhn-plugin/].
Changes since rhncfg-5.9.41-1:
Jan Pazdziora (1):
RHN::Access::User not used anywhere, removing.
Milan Zazrivec (1):
655207 - exit after unsuccessful rpm header read
Miroslav Suchý (2):
666876 - respect metadata_expire setting from yum config
Automatic commit of package [yum-rhn-plugin] release [1.3.2-1].
---
backend/satellite_tools/updatePackages.py | 1
client/rhel/yum-rhn-plugin/rhnplugin.py | 3 +
client/rhel/yum-rhn-plugin/yum-rhn-plugin.spec | 5 ++
rel-eng/packages/yum-rhn-plugin | 2 -
web/modules/rhn/RHN/Access/User.pm | 42 -------------------------
5 files changed, 9 insertions(+), 44 deletions(-)
---
13 years, 2 months
2 commits - client/rhel rel-eng/packages
by Miroslav Suchý
client/rhel/yum-rhn-plugin/rhnplugin.py | 3 +++
client/rhel/yum-rhn-plugin/yum-rhn-plugin.spec | 5 ++++-
rel-eng/packages/yum-rhn-plugin | 2 +-
3 files changed, 8 insertions(+), 2 deletions(-)
New commits:
commit 7a91d1212164f3907852ad0f951a0c37cce039a3
Author: Miroslav Suchý <msuchy(a)redhat.com>
Date: Mon Jan 3 16:42:10 2011 +0100
Automatic commit of package [yum-rhn-plugin] release [1.3.2-1].
diff --git a/client/rhel/yum-rhn-plugin/yum-rhn-plugin.spec b/client/rhel/yum-rhn-plugin/yum-rhn-plugin.spec
index 28bf157..63c6ca5 100644
--- a/client/rhel/yum-rhn-plugin/yum-rhn-plugin.spec
+++ b/client/rhel/yum-rhn-plugin/yum-rhn-plugin.spec
@@ -1,6 +1,6 @@
Summary: RHN support for yum
Name: yum-rhn-plugin
-Version: 1.3.1
+Version: 1.3.2
Release: 1%{?dist}
License: GPLv2
Group: System Environment/Base
@@ -53,6 +53,9 @@ rm -rf $RPM_BUILD_ROOT
%doc LICENSE
%changelog
+* Mon Jan 03 2011 Miroslav Suchý <msuchy(a)redhat.com> 1.3.2-1
+- 666876 - respect metadata_expire setting from yum config
+
* Wed Nov 24 2010 Michael Mraka <michael.mraka(a)redhat.com> 1.3.1-1
- removed unused imports
diff --git a/rel-eng/packages/yum-rhn-plugin b/rel-eng/packages/yum-rhn-plugin
index e767546..726e0da 100644
--- a/rel-eng/packages/yum-rhn-plugin
+++ b/rel-eng/packages/yum-rhn-plugin
@@ -1 +1 @@
-1.3.1-1 client/rhel/yum-rhn-plugin/
+1.3.2-1 client/rhel/yum-rhn-plugin/
commit f9a28adf24d288931cbb512712949304b57fb039
Author: Miroslav Suchý <msuchy(a)redhat.com>
Date: Mon Jan 3 16:41:08 2011 +0100
666876 - respect metadata_expire setting from yum config
diff --git a/client/rhel/yum-rhn-plugin/rhnplugin.py b/client/rhel/yum-rhn-plugin/rhnplugin.py
index 595b1ca..937eab4 100644
--- a/client/rhel/yum-rhn-plugin/rhnplugin.py
+++ b/client/rhel/yum-rhn-plugin/rhnplugin.py
@@ -151,6 +151,7 @@ def init_hook(conduit):
gpgcheck = conduit.confBool('main', 'gpgcheck', default_gpgcheck)
sslcacert = get_ssl_ca_cert(up2date_cfg)
enablegroups = conduit.getConf().enablegroups
+ metadata_expire = conduit.getConf().metadata_expire
for channel in svrChannels:
if channel['version']:
@@ -160,6 +161,7 @@ def init_hook(conduit):
repo.proxy = proxy_url
repo.sslcacert = sslcacert
repo.enablegroups = enablegroups
+ repo.metadata_expire = metadata_expire
repoOptions = getRHNRepoOptions(conduit, repo.id)
if repoOptions:
for o in repoOptions:
@@ -268,6 +270,7 @@ class RhnRepo(YumRepository):
self.retries = 1
self.throttle = 0
self.timeout = 60.0
+ self.metadata_expire = 21700
self.http_caching = True
13 years, 2 months