polish/y2k/index.wml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

#pddp bluszcz
#use wml::debian::template title="Debian and Y2K" GEN_TIME="yes"
#use wml::fmt::url
#use wml::debian::translation-check translation="1.7"

<p>One of the goals of Debian is to provide the most robust system possible.
This is why we have created a system that makes upgrading completely seamless
and why we are investigating how Y2K compliant Debian is.</p>

<p>In evaluating whether a system is Y2K compliant you must look at not only
the base system (the kernel and the basic libraries and tools that create a
system), but all the tools that you use every day. The near Y2K compliance
of a system is meaningless if the failure of even a single non-Y2K
compliant component causes your mission critical system to stop functioning.</p>

<p>Unlike some bloated monolithic operating systems on the market, Debian 
is created by adding a large number of tools on top of the Linux kernel. 
This type of design allows parts of the system to be upgraded without 
affecting the rest. It allows for levels of abstraction in design that 
create a much more robust and flexible system.  Since the interaction of 
different components is well understood, we only need to test the Y2K 
compliance of each component to verify the compliance of the system.</p>

<p>As a service to our customers, we are collecting a list of packages 
and their state of the Y2K compliance. Since Y2K compliance is most 
important to IT departments we have separated the list of 'base' 
system packages and components most used on server machines from the 
rest of the packages we provide (over 2500).</p>

<p>Go to the <a href="extra">list of optional and extra packages</a>.</p>

<p>[Note: If you know of any other links, send mail to
&lt;<a href="mailto:webmaster@debian.org">webmaster@debian.org</a>&gt;]</p>

#include "../../english/y2k/index.data"