[Previo por Fecha] [Siguiente por Fecha] [Previo por Hilo] [Siguiente por Hilo]

[Hilos de Discusión] [Fecha] [Tema] [Autor]

Re: [Sop.Tec.LinuxPPP] Servidor en linux



Te sugiero te inscribas a www.techrepublic.com cuando obtengas tu cuenta, te da opcion a buscar articulos, entre ellos esta uno relacionado a "NT vs Linux", dentro de tu cuenta habilitada de esta pagina usa el buscador de ahi y escribe : NT vs Linux, te apareceran varias paginas entre ellas una con titulo:"Contest winners debate Linux in the enterprise"

que contiene lo siguiente:

Home Articles

Contest winners debate Linux in the enterprise
Mike Jackman
Jul 31, 1999

We asked TechRepublic users to tell us why (or why not) a company should choose Linux as an enterprise solution over Solaris, NetWare or Windows NT. As an incentive, we offered a Diamond Rio MP3 player for first prize, and for each of the two runners-up, a copy of O'Reilly's Linux in a Nutshell.

Congratulations to our winner, Ronald Del Rosairo, and our runners-up, Tim at Netcom, and Jason L. Bowne. The judge for this contest was Web Editor David Bard.

Winner Ronald Del Rosairo wrote:


Why Linux should be chosen as an Enterprise Solution over Solaris, NetWare, and Windows NT: 1) Cost In an Enterprise which minimally consists of one mainframe, five midrange computers, and about 200 servers and 1,000 front-end workstations, the following are the costs for the software alone. (For our purposes, costs for the operating system and applications will be the same for the mainframe and five midrange computers whether you go with Linux, NetWare, Solaris, or Windows NT. The main difference in cost will be in the Server and Workstation area.) On a Linux Solution, the software costs for 200 servers and 1,000 workstations is as follows:

Operating System: 200 x $0, 1,000 x $0
Application Software: StarOffice 200 x $160, 1,000 x $100
Connectivity Software: Built in
Database Software: Assume that the cost is the same for all platforms
Cost of Media (Original Installation Media and documentation): 100 x $50 (to be shared by the enterprise)
Total Cost For Software and media: $137,000
Training: Assume the cost is the same for all although Linux training is considered less expensive than the others compared here. With NetWare, Solaris, or Windows NT the cost of the operating system alone will be in the vicinity of $530,000. At this point, it already shows that the Linux operating system, including the application software such as StarOffice plus the media, costs about one-third less than the cost to get the licenses for the operating system alone with the other platforms.

2) Openness Openness means you can run other applications written for other platforms. Windows NT can run most Windows Applications but not UNIX applications.
NetWare can only run NetWare, MS-DOS and DR-DOS applications.
Solaris can run Solaris and most UNIX applications that are also run on other UNIX platforms. Linux can run DOS applications, Windows 95 applications (which includes applications that also run in the NT environment like Microsoft Office) through an emulator like Wine, and most UNIX applications that are run on other UNIX Platforms.


3) Performance Linux performs as well as, if not better, on a 486 DX2-66, 540 MB HD, and 16 MB RAM than Windows NT on a Pentium 133, 1 GB HD, and 32 MB RAM. Try running Solaris or Novell in a machine configuration that was equal to the DX2-66 era and see if it performs better than Linux. I was able to use my IBM 9776 slc2 50 with 16 MB RAM and 540 HD with Linux and StarOffice with no performance problems.


4) Good Driver Support Installing on an IBM Microchannel Machine I think is one of the most tedious and frustrating experiences whether installing Windows NT, Linux, or NetWare. You can also try installing Solaris for PC in these types of machines and you would see what I mean. Only Linux successfully installed because of the vast availability of drivers available in the Internet. It installed on a microchannel machine with an XGA-2 card, an ACCPA sound card, a Western Digital (now SMC) Ethernet card, and a Legacy 150x Tape drive controller. Only Linux was able to make all these adapters function properly. Windows NT did not have ACCPA sound card drivers also nor for the Legacy 150x tape drive, and the XGA-2 card was not recognized by Windows NT. Remember, Enterprise Networks have lots of these machines. Even though they can be junked, enterprise system administrators just do not want to throw away those things. An old 8580 PS/2 can still function as a very efficient tape backup server. Since Linux is free, a lot of people can develop their own drivers. Even the IT division of a company can handle this rather than rely on companies that only create drivers for their top brands. The Enterprise's IT department can be more flexible here, they can buy or re-use any equipment they want because they can create drivers for them. My Mwave modem/sound card will still not run on Windows NT because of a lack of drivers for it. The Mwave is the best DSP card for organizations or enterprises that need to videoconference or talk using the Internet because of the card's duplex mode capability which allows both parties to talk at the same time.
Just for these four reasons:


Cost
Openness
Performance
Good Driver Support
I recommend Linux as the Enterprise Solution for companies.

First runner-up Tim at Netcom also gave a detailed and thoughtful response:


Linux is a strong contender under certain simple conditions.
The support staff is able to work with "almost-there" software.
Basically, Linux needs serious work on hardware detection and driver management. While I find the Linux boxes I'm supporting to be generally far more reliable than the Windows 9x boxes, the Linux installs were fraught with issues unique to each box linked by the common thread that "This should be happening automatically." In addition, very few pieces of software are available for Linux in a "box-ready" format (load and play). Most require the support staff to configure the source code for the hardware and software platform, compile and occasionally repeat the first step until the compiler stops complaining. Many systems administrators feel their job is to maintain system uptime and network connectivity, not debugging user application code.
Out of band management is not an issue.
While PC users are accustomed to being on the console to troubleshoot, UNIX workstation users have the benefit of configuring their machines to set a serial port as console. A UNIX sysadmin can then TELNET to a terminal server and do almost everything she or he wants to were there an actual keyboard/monitor attached to the system. This is the difference between fixing a problem from home and a long drive to the office to reboot some machine that won't accept a TELNET.
Physical access to the machine is controlled.
On any "stock" Red Hat box booting with LILO, a user with physical access to the keyboard, can ?crash the xserver back to the logged in user session, in spite of the presence of a screenlock (xscreensaver-lock, in this case) ?reboot the machine without the root password by pressing the tried and true [Ctrl] [Alt] [Delete]
?attain root status by typing Linux single at the LILO: prompt.
Note that steps can be taken to stop any and all of the above, but require support staff to learn the intrinsics of either the config files or the source code. An operating system for a machine in an exposed environment should not be so vulnerable under a standard install. Lest I seem completely disparaging regarding Linux, let me point out its strengths.
Server Availability.
Linux servers and workstations in "friendly" environments are up and providing services for months or years at a stretch. Additionally, server software and some system settings can be reconfigured without having to reboot the server.
Old-School Feel.
Many old-school sysadmins learned on UNIX systems. Linux allows them to migrate their skills, rather than develop new ones relying on GUI administration tools. UNIX shell scripting is a powerful tool that many cross-platform sysadmins miss on GUI-only or GUI-oriented operating systems.
Peer-Reviewed Software.
Since most of the software available for Linux is in the form of source code, errors and program deficiencies are usually spotted early. In addition, with access to the offending code, people finding these issues can offer suggestions on how to remedy them. I'm sure the reader will have his or her own list of Linux's strongest strengths and most damning weaknesses. I can only share my opinions.

Second Runner Up Jason L. Browne offers pros and cons:


There are numerous reasons to choose Linux over other OSes and there are a few reasons I feel not to. Here they go :
Use Linux because:

The operating system is extremely stable, runs on just about every platform.
Cost! Free for download ($79 for the full RedHat 6.0 version with manuals and extra software!! Compare that to a ten user Windows NT Server license. Utilities (out of the box web/mail/telnet/ftp/samba server?other OSes charge for this, some come with it) Support. It's free i.e. newsgroups, forums, and companies are starting to support Linux. How-tos and FAQs give the guts of everything as compared to some general help in Windows NT. True flavors of UNIX have main pages and that is a plus for them. Variety of applications that have been, and will be developed by programmers WORLDWIDE. You get the source code which gives you the ability to customize the source itself for application specific stuff. Security. Personal opinion on Apache Web Server is that it is more secure than IIS.
Don't use Linux because:

Non-GUI interface from the start?must introduce users to the command line so they can start X. Mounting and Unmounting of drives before placing CD-ROM or floppy in is inconvenient for users (GNOME touted to fix this). Not many proficient Linux support employees out there (certifications are now available for Red Hat) as compared to Microsoft. Some hardware flat out won't work with Linux until you have someone develop it or make it yourself. Conclusion (personal): I would closely look at Linux as a VERY viable solution for a server, but not yet for the PC. Of course, you could always use a Windows NT Terminal Server with Metaframe 1.8 and let Linux clients use the Linux Citrix Client to access Windows NT Server to run Microsoft applications and still have the stability of Linux on their desktop!! Sometimes there are just too many options to consider.

La liga que a mi me aparece es la siguiente:

http://www.techrepublic.com/article.jhtml?id=/article/r00119990731mik99.htm

Pero igual y no la puedas abrir sino estas dado de alta en ese sitio pero igual pruebala.

De hecho en ese sitio hacen muchos comparativos entre Linux y NT ademas de dar topicos sobre cada sistema operativo.

Espero te sirva la informacion.


From: "Carlos Daniel Olivas" <carlosdob en hotmail com>
Reply-To: linux en pepe net mx
To: linux en pepe net mx
Subject: [Sop.Tec.LinuxPPP] Servidor en linux
Date: Thu, 11 Nov 1999 09:23:46 MST

Hola:

Soy estudiante de informatica, en mazatlan, sin. Unos compañeros y yo queremos presentar una comparacion del funcionamiento de diferentes sistemas operativos, principalmente nos interesa linux Vs NT, si alguno conoce un buen link que nos explique como podemos levantar un servidor de internet y archivos bajo linux por favor mandenos la respuesta.

De antemano GRACIAS.


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
----------------------------------------------------------------
Lista de soporte de LinuxPPP
Para entrar en ella enviar un mensaje a majordomo en pepe net mx
que diga subscribe en el subject o en el cuerpo del mensaje.
Para salir de ella enviar un mensaje a majordomo en pepe net mx
que diga unsubscribe en el subject o en el cuerpo del mensaje.
Reglas de la lista en http://pepe.net.mx/reglas.html

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
----------------------------------------------------------------
Lista de soporte de LinuxPPP
Para entrar en ella enviar un mensaje a majordomo en pepe net mx
que diga subscribe en el subject o en el cuerpo del mensaje.
Para salir de ella enviar un mensaje a majordomo en pepe net mx
que diga unsubscribe en el subject o en el cuerpo del mensaje.
Reglas de la lista en http://pepe.net.mx/reglas.html



[Hilos de Discusión] [Fecha] [Tema] [Autor]