[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.18,
1.19
Yuri Kozlov
yuray-guest at alioth.debian.org
Tue Apr 3 18:01:01 UTC 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv21851/sgml
Modified Files:
release-notes.en.sgml
Log Message:
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- release-notes.en.sgml 2 Apr 2007 17:52:30 -0000 1.18
+++ release-notes.en.sgml 3 Apr 2007 18:00:59 -0000 1.19
@@ -75,7 +75,7 @@
<item><p>The status of your package database before and after the
upgrade, using the backup procedure described at <ref
- id="backup">.
+ id="backup">.</p></item>
<item><p>Your aptitude logs, available at <file>/var/log/aptitude</file>.</p></item>
@@ -167,9 +167,10 @@
&architecture; platform.</p>
]]>
+<!--
<p>&debian; &release; for the &arch-title; architecture ships with
kernel version &kernelversion;.</p>
-
+-->
<sect id="newdistro"><heading>What's new in the distribution?</heading>
@@ -218,8 +219,6 @@
<item>the GNU Compiler Collection 4.1 as default compiler</item>
- <item>PHP 5.5</item>
-
<item>language interpreters: PHP 5.2, Python 2.4</item>
<item>server software:
@@ -231,7 +230,7 @@
<!-- TODO: Cherokee, lighttpd, and Tomcat 5 are NEW -->
<!-- Note: No significant changes for Roxen4, Boa, and thttpd -->
<item>web servers: Apache 2.2, fnord 1.10</item>
-
+
<item>database servers: MySQL 5.0.32, PostgreSQL 8.1</item>
<item>the OpenSSH server, version 4.3</item>
@@ -283,7 +282,7 @@
id="http://www.debian.org/doc/manuals/securing-debian-howto/ch7#s-deb-pack-sign"
name="Package signing in Debian"> chapter of the <em/Securing Debian
Manual/ and the <url id="http://wiki.debian.org/SecureApt"
- name="wiki documentation">.</p>
+ name="Debian Wiki">.</p>
</sect1>
<sect1 id="volatile"><heading>debian-volatile now an official service</heading>
@@ -292,8 +291,9 @@
unofficial service with the release of &oldreleasename; has now
become an official &debian; service.</p>
- <p>This means that it no longer has a <tt/.debian.net/ address,
- but now uses a <tt/.debian.org/ address. Please make sure to update
+ <p>This means that it now uses a <tt/.debian.org/ address<footnote>
+ The old <tt/volatile.debian.net/ address will also remain valid for
+ the time being. </footnote>. Please make sure to update
your <file>/etc/apt/sources.list</file> accordingly if you were
already using this service.</p>
@@ -301,13 +301,13 @@
update stable packages that contain information that quickly goes out
of date. Examples are a virus scanner's signatures list or a spam
filter's pattern set. For more information and a list of mirrors,
- please see the archive's <url id="&url-debian-volatile"
+ please see the archive's <url id="&url-debian-volatile;"
name="web page">.</p>
</sect1>
</sect>
- <sect id="improves_in_etch"><heading>System improvements</heading>
+ <sect id="system-changes"><heading>System improvements</heading>
<p>There have been a number of changes in the distribution that will
benefit new installations of &releasename;, but may not be automatically
@@ -345,7 +345,7 @@
<p>Note that SELinux support is <em/not/ enabled by default. Information
on setting up and enabling SELinux can be found on the
- <url id="&url-wiki-selinux" name="Debian Wiki">.
+ <url id="&url-wiki-selinux;" name="Debian Wiki">.
</p></item>
<tag>New default inet superdaemon</tag>
@@ -400,6 +400,128 @@
name="Debian Wiki"> has some additional information about changes between
&oldreleasename; and &releasename;.</p>
+ </sect>
+
+ <sect id="kernel-changes"><heading>Major kernel-related changes</heading>
+
+ <p>&debian; &release; ships with kernel version &kernelversion; for all
+ architectures; 2.4 kernels are no longer officially supported.</p>
+
+ <p>There have been major changes, both in the kernel itself and in the
+ packaging of the kernel for Debian. Some of these changes complicate
+ the upgrade procedure and can potentially result in problems while
+ rebooting the system after the upgrade to &releasename;. This section
+ gives an overview of the most important changes; potential issues and
+ information on how to work around them is included in later chapters.</p>
+
+<![ %defaulted-2.4 [
+ <p>If you are currently using a 2.4 kernel, you should read
+ <ref id="upgrade-to-2.6"> carefully.</p>
+]]>
+
+ <sect1 id="kernel-packaging"><heading>Changes in kernel packaging</heading>
+
+ <p><taglist>
+ <tag>Kernel packages renamed</tag>
+ <item><p>All Linux kernel packages have been renamed from <tt/kernel-*/
+ to <tt/linux-*/ to clean up the namespace: it will make it easier to
+ include non-Linux kernels in Debian in the future.</p></item>
+
+<![ %i386 [
+ <tag>Flavor "386" replaced with "486"</tag>
+ <item><p>Support for the 80386 sub-architecture for Intel x86 has been
+ dropped in &releasename;. The 386 kernel flavor is no longer supported
+ and has been replaced by the new 486 flavor.</p></item>
+]]>
+<![ %amd64 [
+ <tag>Single generic kernel for &arch-title;</tag>
+ <item><p>In &oldreleasename; had separate kernel flavors for different
+ processor families. Because of changes in the kernel which will
+ automatically optimize the kernel for the processor(s) in the system,
+ there is no longer any real need for seperate kernel flavors.</p></item>
+]]>
+
+<![ %i386-amd64-ia64 [
+ <tag>Standard kernels have SMP abilities</tag>
+ <item><p>Multiprocessor systems no longer require a <tt/*-smp/ flavor of the
+ Linux kernel. For &arch-title;, <tt/linux-image/ packages without the <tt/-smp/
+ suffix support both uniprocessor and multiprocessor systems.
+<![ %i386 [
+ There is one exception: the 486 flavor only supports a single processor.
+]]>
+ </p></item>
+]]>
+ </taglist></p>
+
+ <p>Where possible, dummy transition packages that depend on the new packages
+ have been provided for the dropped packages.</p>
+
+ </sect1>
+
+ <sect1 id="kernel-initrd"><heading>New utilities to generate initrds</heading>
+
+<![ %no-initrd [
+ <p>The Debian kernel image packages for &arch-title; do not require an
+ initrd for booting the system. This means that the information in this
+ section may not really be relevant for you, but is still included for
+ reference.</p>
+]]>
+ <p>
+<![ %uses-initrd [
+ The Debian kernel image packages for &arch-title; require an initrd
+ for booting the system.
+]]>
+ Because of changes in the kernel, the utility used to generate initrds in
+ &oldreleasename;, <package/initrd-tools/ can no longer be used and has been
+ deprecated. Two new utilities have been developed that replace it:
+ <package/initramfs-tools/ and <package/yaird/. The concepts behind the new
+ utilities are very different; an overview is available on the
+ <url id="http://wiki.debian.org/InitrdReplacementOptions" name="Debian Wiki">.
+ Both will generate an initrd using the <em/initramfs/ file system, which is
+ a compressed <prgn/cpio/ archive.
+ The default and recommended utility is <package/initramfs-tools/.
+ </p>
+
+<![ %uses-initrd [
+ <p>Upgrading to an &releasename; kernel will cause
+ <package/initramfs-tools/ to be installed by default.
+<![ %defaulted-2.4 [
+ If you are upgrading from a 2.4 kernel to a 2.6 Debian kernel,
+ you must use <package/initramfs-tools/. Using
+ <package/yaird/ will cause linux-image-2.6 installations to
+ fail if you are running a 2.2 or 2.4 kernel.
+]]>
+ </p>
+
+ <p>The package <package/initrd-tools/ is still included in &releasename;
+ because it is needed for upgrades from &oldreleasename;. The package will
+ be dropped for the next release.</p>
+]]>
+
+ </sect1>
+
+ <sect1 id="kernel-devfs"><heading>Dynamic <file>/dev</file> management</heading>
+
+ <p>&releasename; kernels no longer provide support for <prgn/devfs/.</p>
+
+ <p>The replacement for <prgn/devfs/ is <prgn/udev/.
+ <p><package/udev/ is a userspace implementation of devfs. It is mounted
+ over the <file>/dev</file> directory and will populate that directory
+ with devices supported by the kernel. It will also dynamically add and
+ remove devices as kernel modules are loaded or unloaded respectively,
+ based on events generated by the kernel. <prgn/udev/ is a lot more
+ versatile than <prgn/devfs/ and offers services that are used by other
+ programs like <prgn/hal/ (hardware abstraction layer).</p>
+
+<![ %uses-initrd [
+ <p>If you install a Debian kernel image, <package/udev/ will be installed
+ by default as <package/initramfs-tools/ depends on it.</p>
+ <p>You can avoid installing <package/udev/ by compiling a custom non-modular
+ kernel or by using an alternative initrd generator, such as <package/yaird/.
+ However, <package/initramfs-tools/ is the recommended initrd generator.
+]]>
+
+ </sect1>
</sect>
</chapt>
@@ -477,7 +599,7 @@
installer. If you are interested in an overview of the detailed
changes since &oldreleasename;, please check the release announcements
for the &releasename; beta and RC releases available from the
- Debian Installer's <url id="&url-installer-news" name="news history">.</p>
+ Debian Installer's <url id="&url-installer-news;" name="news history">.</p>
<sect1 id="inst-changes"><heading>Major changes</heading>
@@ -625,7 +747,7 @@
<tag>Improved system-wide localization</tag>
<item><p>Most of the internationalization and localization tasks that
were previously handled by the <package>localization-config</package> tool are now
- included in the stock &debian; installer or in packages themselves. This
+ included in the stock Debian installer or in packages themselves. This
means that selection of a language will automatically install packages
necessary for that language (dictionaries, documentation, fonts...) in both
standard and desktop environments. Configuration that is no longer
@@ -846,7 +968,7 @@
</sect1>
- <sect1><heading>Checking packages status</heading>
+ <sect1 id="package_status"><heading>Checking packages status</heading>
<p>Regardless of the method used for upgrading, it is recommended
that you check the status of all packages first, and verify that
@@ -1291,7 +1413,7 @@
</example></p>
<p>This step will automatically upgrade <package/libc6/ and
- <package/locales/ and will pull in SE linux support libraries
+ <package/locales/ and will pull in SELinux support libraries
(<package/libselinux1/). At this point, some running services will be
restarted, including <prgn/xdm/, <prgn/gdm/ and <prgn/kdm/, as a
consequence local X11 sessions will be disconnected.</p>
@@ -1309,7 +1431,7 @@
# dpkg -l "xlibmesa-glu*" | grep ^ii
</example>
- if you have them installed then you have to install the latest
+ If you have them installed then you have to install the latest
versions from &releasename;. The following command will install both,
if you have only one of them you should remove the other:
@@ -1492,19 +1614,9 @@
Please read the information in this section about potential issues
with kernel upgrades.</p>
- <p>All Linux kernel packages have been renamed from <package/kernel-*/ to
- <package/linux-*/ to clean up the namespace.</p>
-
<![ %defaulted-2.4 [
- <p>If you are currently using a kernel from the 2.4 series,
- the older stable Linux kernel series, you should upgrade to a 2.6
- series kernel, as 2.4 is no longer supported in &releasename;.
- If you are currently using a kernel from the 2.2 series, you
- must upgrade to (at least) the 2.4 series, preferably to a 2.6 series
- kernel, prior to upgrading your packages.
-<!-- TODO: incorporate this part in this section -->
- Some general issues associated with an upgrade to 2.6 are documented
- in <ref id="upgrade-to-2.6">.</p>
+ <p>If you are currently using a 2.4 kernel, you should also read
+ <ref id="upgrade-to-2.6"> carefully.</p>
]]>
<sect1><heading>Installing the kernel metapackage</heading>
@@ -1531,6 +1643,10 @@
<tt>uname -r</tt> and look for a package with a similar name.
For example, if you see '2.4.27-3-686', it is recommended that you
install <package/linux-image-2.6-686/.
+<![ %i386 [
+ (Note that the 386 flavor no longer exists; if you are currently using
+ the 386 kernel flavor, you should install the 486 flavor instead.)
+]]>
You may also use <prgn>apt-cache</prgn> to see a long description of each
package in order to help choose the best one available.
For example:
@@ -1575,8 +1691,8 @@
To upgrade the kernel before the upgrade, take
all the steps up to and including the steps related to the a minimal
upgrade of the system, as described in <ref id="minimal_upgrade">.
- Once <package/initrd-tools/ have been upgraded after those steps
- you can then do the following (changing the kernel package name to the one most
+ Once the package <package/initrd-tools/ has been upgraded after those steps,
+ you can do the following (changing the kernel package name to the one most
suited to your system by substituting <em><flavor></em>):
<example>
# aptitude install linux-image-2.6-<flavor>
@@ -1597,11 +1713,12 @@
<p><em>TRY</em>: In aptitude, upgrade only 'required' 'important'
'standard' packages limit by pressing 'l' and input
!~v(~pextra|~poptional) keep with : for hold this time upgrade by
- pressing 'U" and 'g' (untested but ...) (You can do this in much
+ pressing 'U' and 'g' (untested but ...) (You can do this in much
finer steps.)
-->
</sect1>
+<![ %defaulted-2.4 [
<sect1 id="upgrade-from-2.4"><heading>Upgrading from a 2.4 kernel</heading>
<p>If you have a 2.4 kernel installed, and your system relies on
@@ -1612,7 +1729,7 @@
is removed from the system (in favor of <package/udev/) when you do a full system
upgrade. If you do not do the kernel upgrade before this your system might
not boot up properly from this point on. Once you have done an upgrade
- to a the 2.6 series kernel in &oldreleasename; you can do a kernel upgrade
+ to a 2.6 series kernel in &oldreleasename; you can do a kernel upgrade
as described in <ref id="upgrade-from-2.6">.</p>
<p>If your system does not rely on <package/hotplug/<footnote>You can
@@ -1628,54 +1745,6 @@
</p>
</sect1>
-
- <sect1><heading>initrd-tools deprecated</heading>
- <p><package/initrd-tools/ is no longer supported and has been
- superseded by <package/initramfs-tools/ and <package/yaird/.
- Upgrading to an &releasename; kernel will cause
- <package/initramfs-tools/ to be installed by default.
-<![ %defaulted-2.4 [
- If you are upgrading from a 2.4 kernel to a 2.6 kernel for the
- first time, you must use <package/initramfs-tools/. Using
- <package/yaird/ will cause linux-image-2.6 installations to
- fail if you are running a 2.2 or 2.4 kernel.
-]]>
- </p>
- </sect1>
-
- <sect1><heading>devfs deprecated</heading>
- <p>&releasename; no longer provides support for <prgn>devfs</prgn>.
- It is recommended that users switch to <package>udev</package> for dynamic
- <file>/dev</file> management.
- Debian kernels no longer include support for <prgn>devfs</prgn>,
- so <prgn>devfs</prgn> users will need to convert their systems
- manually before upgrading to an &releasename; kernel.</p>
-
- <p>If you see the string 'devfs' in <file>/proc/mounts</file>,
- you are most likely using <prgn>devfs</prgn>.
- Any config files that reference <prgn>devfs</prgn> style names will need to be
- adjusted to use <prgn>udev</prgn> style names. Files that are most likely to
- refer to <prgn>devfs</prgn> style device names are <file>/etc/fstab</file>,
- <file>/etc/lilo.conf</file>, <file>/boot/grub/menu.lst</file>, etc.</p>
-
- <p>More information about potential issues is available in bug report
- <url id="http://bugs.debian.org/341152" name="#341152">.</p>
- </sect1>
-
-<![ %i386-amd64-ia64 [
- <sect1><heading>Standard kernels have SMP abilities</heading>
- <p>Multiprocessor systems no longer require a *-smp flavor of the
- Linux kernel. For &arch-title;, linux-image packages without the -smp
- suffix support both uniprocessor and multiprocessor systems.</p>
- </sect1>
-]]>
-
-<![ %i386 [
- <sect1><heading>386 kernel flavor deprecated</heading>
- <p>Support for the 80386 sub-architecture for &arch-title; has been dropped
- in &releasename;. The 386 kernel flavor is no longer supported and has been
- replaced by the new 486 flavor.</p>
- </sect1>
]]>
<sect1 id="device-reorder"><heading>Device enumeration reordering</heading>
@@ -1803,6 +1872,22 @@
"formal" upgrade is complete, but there are some other things
that should be taken care of <em/before/ the next reboot.</p>
+ <sect1 id="convert-devfs"><heading>Converting from devfs</heading>
+ <p>Debian kernels no longer include support for <prgn>devfs</prgn>,
+ so <prgn>devfs</prgn> users will need to convert their systems
+ manually before booting an &releasename; kernel.</p>
+
+ <p>If you see the string 'devfs' in <file>/proc/mounts</file>,
+ you are most likely using <prgn>devfs</prgn>.
+ Any config files that reference <prgn>devfs</prgn> style names will need to be
+ adjusted to use <prgn>udev</prgn> style names. Files that are most likely to
+ refer to <prgn>devfs</prgn> style device names are <file>/etc/fstab</file>,
+ <file>/etc/lilo.conf</file>, <file>/boot/grub/menu.lst</file>, etc.</p>
+
+ <p>More information about potential issues is available in bug report
+ <url id="http://bugs.debian.org/341152" name="#341152">.</p>
+ </sect1>
+
<![ %sparc [
<sect1 id="missingdrivers"><heading>Possible missing drivers in initrd</heading>
<p>The &releasename; kernels do not yet have full sysfs support for
@@ -1838,13 +1923,13 @@
<p>If you are using <package/lilo/ as your bootloader (it is the
default bootloader for some installations of &oldreleasename;) it is strongly recommended
- that you rerun lilo after the upgrade:
+ that you rerun <prgn>lilo</prgn> after the upgrade:
<example>
# /sbin/lilo
</example></p>
<p>Notice this is needed even if you did not upgrade your system's kernel, as
- lilo's second stage will change due to the package upgrade.</p>
+ <prgn>lilo</prgn>'s second stage will change due to the package upgrade.</p>
<p>Also, review the contents of your <file>/etc/kernel-img.conf</file> and
make sure that you have <em>do_bootloader = Yes</em> in it. That way the
@@ -2131,6 +2216,18 @@
bug reports and other information mentioned in <ref id="morereading">.
</p>
+ <sect1 id="udev"> <heading>Problems with devices related to udev</heading>
+ <p>Although <package/udev/ has been tested extensively, you may experience
+ minor problems with some devices that will need to be fixed. The most
+ common problems are changed permission and/or ownership of a device.
+ In some cases a device may not be created by default (e.g.
+ <file>/dev/video</file> and <file>/dev/radio</file>).</p>
+
+ <p><package/udev/ provides configuration mechanisms to deal with these
+ issues. See <manref name="udev" section="8"> and <file>/etc/udev</file>
+ for further information.</p>
+ </sect1>
+
<sect1 id="window-scaling"><heading>Certain networking site cannot be reached by TCP</heading>
<p>
Since 2.6.17, Linux aggressively uses TCP window scaling which is specified in RFC 1323.
@@ -2234,13 +2331,6 @@
lightly. This section aims to make you aware of some of the issues
you may face.</p>
-<!-- TODO - needs to be changed for etch, not TRUE -->
- <p>You are therefore strongly advised not to upgrade to a 2.6 kernel
- as part of the upgrade from &oldreleasename; to &releasename;.
- Instead, you should first make sure your system works correctly
- with either the old kernel or with a 2.4 kernel from &releasename;
- and do the upgrade to a 2.6 kernel later as a separate project.</p>
-
<p>If you compile your own kernel from source, make sure you install
<package/module-init-tools/ before you reboot with the 2.6 kernel.
This package replaces <package/modutils/ for 2.6 kernels. If you
@@ -2262,7 +2352,7 @@
<!-- JFS: Can't this device name change even for some other disk controllers? I've found
references in debian-user posts talking about some strange chipsets and BIOS
which are seen in sarge' 2.4 as hda and in etch's 2.6 as hdf... -->
-<![ %i386-amd64 [
+<![ %i386 [
<p>For some SATA disk controllers, the device assigned to a drive and
its partitions may change from <file>/dev/hdX</file> to
<file>/dev/sdX</file>. If this happens, you will have to modify your
@@ -2285,7 +2375,7 @@
already running a 2.6 kernel you will automatically retrieve the
latest kernel when upgrading the rest of the system (see <ref
id="upgrading_other">). Failing to do this will result in an system
- that does not boot,
+ that does not boot.
</p>
]]>
@@ -2297,7 +2387,6 @@
prevents you booting the old kernel.</p>
<![ %not-s390 [
-<![ %not-amd64 [
<sect1 id="2.6-keyboard">
<heading>Keyboard configuration</heading>
@@ -2330,7 +2419,6 @@
first case you will not be affected by this issue.</p>
]]>
</sect1>
-]]> <!-- %not-amd64 -->
<sect1 id="2.6-mouse">
<heading>Mouse configuration</heading>
@@ -2365,41 +2453,9 @@
</sect1>
]]> <!-- %not-s390 -->
-
-<!-- FJP: May already be covered by kernel team text
- Etch Debian kernels depend on udev via initramfs-tools -->
- <sect1 id="2.6-udev">
- <heading>Switching to 2.6 may activate udev</heading>
-
- <p><package/udev/ is a userspace implementation of devfs. It is mounted
- over the <file>/dev</file> directory and will populate that directory
- with devices supported by the kernel. It will also dynamically add and
- remove devices as kernel modules are loaded or unloaded respectively,
- working together with <package/hotplug/ to detect new devices.
- <package/udev/ works only with 2.6 kernels.</p>
-
- <p>As <package/udev/ is automatically installed as a dependency of the new
- default initrd generator used with the 2.6 kernels
- (<package/initramfs-tools/), upgrading to a 2.6 kernel will normally result
- in <package/udev/ being activated. You can avoid installing <package/udev/
- if you install an alternate initrd generator, such as <package/yaird/.
- <package/initramfs-tools/ is the recommended initrd generator.</p>
-
- <p>Although <package/udev/ has been tested extensively, you may experience
- minor problems with some devices that will need to be fixed. The most
- common problems are changed permission and/or ownership of a device.
- In some cases a device may not be created by default (e.g.
- <file>/dev/video</file> and <file>/dev/radio</file>).</p>
-
- <p><package/udev/ provides configuration mechanisms to deal with these
- issues. See <manref name="udev" section="8"> and <file>/etc/udev</file>
- for further information.</p>
-
- </sect1>
</sect>
]]> <!-- %defaulted-2.4 -->
-
<sect id="xorg"> <heading>XFree86 to X.Org transition</heading>
<p>The transition to X.Org involves some structural changes. In case
all installed packages are from Debian and also included in &releasename;,
@@ -2475,6 +2531,32 @@
</sect>
+ <sect id="zope"> <heading>Upgrading Zope and Plone</heading>
+ <p>Zope and all related products have been updated. Many products were
+ also dropped from the distribution (either because they were obsoleted,
+ or because they are incompatible with the newer Zope, CMF or Plone.</p>
+ <p>Unfortunately there is no easy and guaranteed way to upgrade a
+ complex <prgn/zope/ or <prgn/plone/ server. Even though Plone includes
+ a migration tool, experience has shown that automatic migrations
+ can easily fail.</p>
+
+ <p>For this reason, users are recommended to set up their system so they
+ can continue to run the &oldreleasename; installation of Zope/Plone
+ alongside the new &releasename; versions while testing the migration.</p>
+ <p>The easiest and safest way to achieve this, is to make a copy of your
+ &oldreleasename; system to another hard disk or partition, and then
+ upgrade only one of the two copies. You can then use <prgn/chroot/ to
+ run the &oldreleasename; version in parallel to the &releasename;
+ version.</p>
+
+ <p>For Zope, you may also be able to keep the old packages installed on
+ your &releasename; system. For most packages this is possible as they
+ use a different name space. To keep the old versions, you will need to
+ package holding as documented in <ref id="package_status">. This method
+ is not possible for Plone because the <package/zope-cmfplone/ package
+ is not versioned.</p>
+ </sect>
+
<sect id="php-globals"> <heading>Deprecated insecure php configurations</heading>
<p>For many years, turning on the <tt/register_globals/ settings in PHP
has been known to be insecure and dangerous, and this option has defaulted to
@@ -2482,7 +2564,7 @@
now finally deprecated on Debian systems as too dangerous.
The same applies to flaws in <tt/safe_mode/ and <tt/open_basedir/, which
have also been unmaintained for some time.</p>
-
+
<p>Starting with this release, the Debian security team does not provide
security support for a number of PHP configurations which are known to
be insecure. Most importantly, issues resulting from
More information about the l10n-russian-cvs-commits
mailing list