From: Tamer Sahin (ts@securityoffice.net)
Date: Sat 30 Nov 2002 - 13:20:58 EET
-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5
Saturday, November 30, 2002, 8:20:38 AM, you wrote:
BB> Selamlar,
BB> Kisaca adamlar "burada ISO ya yazilim satan biziz, onu da satin alsik=20
BB> gerekirse standartlari da biz belirleriz." gibisinden laf etmisler. Fakat=20
BB> Microsucks=AE Wincows=99' da cokmelerin bile bir standardi yok. Wincows=999=
BB> =D7=20
Microsoft'un kendi icinde "Blue Screen Resource Center" isimli bi
departmani var orada blue screen'lerin onune gecmek icin kendilerini
yirtiyorlar. Eee buyuk patron (sanirim win98) lansmaniydi blue
screen'le karsilasinca tantana koptu.
Microsoft'un yukaridaki belirttiginiz adresteki komik iddialarina ciddi cevaplar
Turkiye'deki opensource camiasindan gelmisti
http://www.acikkod.org/show_article.php?id=5&cat=5 adresinden dokumana
ulasilabilir.
Bunun disinda Microsoft Windows urununun neden sunucu isletim
sistemleri icin dogru bir secim olmadigini
www.securityoffice.net/mssecrets/hotmail.html adresinde acikliyor.
Tamamen Microsoft yazilim muhendisleri tarafindan hazirlanan
confidential bir dokuman.
Ornegin yukaridaki dokumandan "PROBLEMS WITH WINDOWS" baslikli kisimdan
bazi alintilar;
======================== SNIP =====================================
"PROBLEMS WITH WINDOWS
Consider the above list of UNIX strengths to be also a list of Windows
weaknesses. However, there are some specific issues that need to be
called out.
1) A GUI bias. Windows 2000 server products continue to be
designed with the desktop in mind. There are too many functions
that are either too difficult or impossible to perform using a
text-based interface.
Why is this important? There are several reasons:
* GUI operations are essentially impossible to script. With
large numbers of servers, it is impractical to use the GUI to carry out
installation tasks or regular maintenance tasks.
* Text-based operations are more versatile; an administrator can
usually do more to a system (good and bad) than is provided by the restricted,
planned methods using the GUI.
* There is in place at Hotmail an established secure channel
into the production system, using a text-based secure shell interface.
* Using a GUI amounts to hiding the true system modifications
from the system administrators and operators. UNIX operators like the sense of
control that comes from their ability to modify system tables and configuration
files more directly.
* Operating a GUI through a slow network connection can be too
slow to be useful. Although this is less important, it can still be a
consideration when there is a need to administer or diagnose a system through
a dialup connection.
There are, indeed, many non-GUI administrative programs provided in the
core Windows 2000 product and in the Resource Kit. The problem is that the
collection is somewhat arbitrary, incoherent and inconsistent. Programs seem to
have been written to fill an immediate need and there is stylistic inconsistency
and poor feature coverage.
2) Complexity. A Windows server out of the box is an elaborate
system. Although it performs specific tasks well (such as being a web server)
there are many services that have a complex set of dependencies, and it is never
clear which ones are necessary and which can be removed to improve the
system's efficiency.
3) Obscurity. Some parameters that control the system's operation
are hidden and difficult to fully assess. The metabase is an obvious
example. The problem here is that is makes the administrator nervous; in a
single-function system he wants to be able to understand all of the
configuration-related choices that the system is making on his behalf.
4) Resource utilization. It's true that Windows requires a more
powerful computer than Linux or FreeBSD. In practice, this is a less important
constraint. When you are building a large operation, you will use smaller
numbers of relatively powerful systems. The PC systems in use at Hotmail
are perfectly capable of running Windows, and the machine's basic power is
the same whether it is run with UNIX or Windows. For most of the time, it is only
executing application code and most of the extra elaboration is not
apparent.
5) Image size. The team was unable to reduce the size of the image
below 900MB; Windows contains many complex relationships between pieces, and
the team was not able to determine with safety how much could be left out of the
image. Although disk space on each server was not an issue, the time taken to
image thousands of servers across the internal network was significant. By
comparison, the equivalent FreeBSD image size is a few tens of MB.
6) Reboot as an expectation. Windows operations still involves too
many reboots. Sometimes they are unnecessary, but operators reboot a system
rather than take the time to debug it. For example, a service may be hung, and
rather than take the time to find and fix the problem, it is often more
convenient to reboot. By contrast, UNIX administrators are conditioned to quickly
identify the failing service and simply restart it; they are helped in this by the
greater transparency of UNIX and the small number of interdependencies. Some
reboots are demanded by an application installation, and are not strictly necessary.
7) License costs. As we will see when discussing load balancing,
the license cost of Windows software is a major consideration when
converting from the unencumbered UNIX implementations. Although there were no
costs to the Hotmail project, as a Microsoft department, the team did consider the
software costs in order to make the conversion a useful model for future
customers.
* They used Server in preference to Advanced Server (no features
of Advanced Server were necessary).
* They reluctantly used Services for UNIX and Interix, to get
access to features that were not adequately provided in Windows. Future releases
of Windows will have the features that would make it unnecessary to add
those subsystems and avoid their notional cost.
* No business analysis was undertaken to determine whether the
benefit of the conversion would outweigh the notional cost of the Windows
licenses."
======================== SNIP =====================================
Iyi Calismalar,
Tamer Sahin
http://www.securityoffice.net
-----BEGIN PGP SIGNATURE-----
Version: 2.6
iQEVAwUAPeifIPpL5ibJRTtBAQEc+Af7ByCJCqvawuqmXGWW5e5WsGYLb0OShTYv
PzolgPXoD4S0aCYhZcxkIGK+mpSmoOHzNrh1Y1WQNCRMH2RvlU0wRQ/6lpUBMMcN
qEPrxbx/wJzmlIw6WdTB8kpTO0PGCJZokZpRPozOZbhK0sNSZ//8sAGg9mHijxny
Z4ef0sKqPulrJYBUSF+W4Vdm4lPEyPiaw6Mgxcj45WYx0rfLXgccvo7nuitsYWgB
wkbDiKYtNfq92K2wu5nz9RuRAnYYm/5P9/lzxyJvMRydiGumnJkAsqkqmnc3tF3j
bD1xL/VwzuZHb67MuBxGubWNtkDRG7QCRSLh0bvH8tr4+3JXcV1C7w==
=3ZZZ
-----END PGP SIGNATURE-----
-----------------------------------------------------------------------
Liste üyeliğiniz ile ilgili her türlü işlem için
http://liste.linux.org.tr adresindeki web arayüzünü kullanabilirsiniz.
Listeden çıkmak için: 'linux-request@linux.org.tr' adresine,
"Konu" kısmında "unsubscribe" yazan bir e-posta gönderiniz.
-----------------------------------------------------------------------