| ★ wanayoo — archive 1999 http://www.linux.com/linux@work/integration/ | Nouvelle recherche | Portail wanayoo |
| THEMES.ORG · GEOCRAWLER · NEWSFORGE · FRESHMEAT | My OSDN · JOBS · PARTNERS · AFFILIATES |
|
| Feedback / Printable | Thu, Aug 24 |
|
Powered by GNU/Debian
|
|
|
Main . Advisory Board . Chat . Desktops . Development . FirstStep . Games . Download . Hardware . Jobs . Links . LinuxGram . Linux.com Live! . Linux User Groups . Multimedia . News . Support . Tuneup . O'Reilly |
|
|
Linux@work
Contributed by Derek & Tori Wildstar It is no secret that companies all over the world are beginning to see and desire the benefits of the Linux operating system. Conversion to Linux is a volatile discussion topic in many workplaces today. It is, indeed, a very difficult decision for executives. Linux, which had previously been considered an "underground" operating system, is now being touted by technical media. However, it is also being chastised at much the same rate. How does one decide which operating system is best suited to a corporation's needs? This is an arduous question complicated by several economic and technical factors. The decision-making process is often clouded by fear, uncertainty, and doubt. The intent of this article is to provide you with adequate information upon which you will be able to make an informed decision about an option you may not have thought possible: INTEGRATION. By incorporating Linux into your existing IT infrastructure, you will be able to personally measure the benefits and downfalls of operating systems. You will be able to weigh your options based on your company's needs and the performance of your own systems. Integration can help you to take the guesswork out of this crucial question. Basic Information Depending on your level of technical knowledge, you may find it helpful to read a bit of basic Linux information before you decide whether or not you'd like to integrate Linux into your existing network. Two very important resources are the "Linux FAQ" (for answers to Frequently Asked Questions) and "What is Linux?". You may also wish to research "LinuxBusiness.com" for information on companies who are currently deploying Linux solutions. Once you are sure that you would like to try to integrate Linux into your existing network, you will need to decide on a distribution. The " Overview of Linux Distributions" is an invaluable resource to anyone who is considering the implementation of Linux. Hardware Linux will run on any machine with a 386DX (or later) processor, but for a suitable "real-world" server, we recommend a processor with the equivalent power of a Pentium 166. The machine should have at least 48MB of RAM. Keep in mind that it is difficult to make hardware generalizations without knowing the type of server you will be implementing - and without knowing which distribution you have chosen. There have been many accusations made with regard to Linux hardware support - or a lack thereof. You will find that many of these accusations of Linux hardware incompatibilities are highly exaggerated. You should be able to find the answer to any questions regarding hardware compatibility at the " Linux Hardware Compatibility HOWTO" by Patrick Reijnen. Linux has already been ported to Sparc, Motorola, Compaq (formerly Digital), hand-held systems and many others. You may wish to read this well known list of "Current ports of the Linux OS" for more information on CPUs that can run Linux. The Process of Integration The method of integration depends on system specifics. The process will differ depending on the types of systems being integrated and the purpose of the network. We cannot possibly explain every possible option, but we hope to provide you with general examples that will help you to decide what integration will entail and how coexistence and interoperability can work for you. Depending on your situation, integration might involve setting up and/or configuring the following:
Securing your workstation or server is the most important step of the whole setup process. Keeping your machine secure is an ongoing process. It involves turning off services that are unused and keeping up-to-date with the latest package releases. Naturally, you will also want to be sure that every user has selected a good password. "Good," in this case, can be defined as a password that does not contain any dictionary words and contains mixed-case alphabetical characters and numerical characters. These general security tips should apply to any system - and a Linux system is certainly not an exception. One should never overestimate the security of a computer. Since most corporate networks are set up using TCP/IP, we will concentrate on configuring Linux to use it. TCP/IP is an acronym for "Transmission Control Protocol/Internet Protocol." A protocol is a supported (i.e. agreed upon) format for the transmission of data between two devices. TCP/IP is often considered the "standard" protocol for transmitting data over networks. Using TCP/IP involves:
DNS is an important part of the network configuration. DNS is the "Domain Name System" and is sometimes described as an "Internet phone book". It provides a way for a computer to match a domain name with an IP (Internet Protocol) address. In other words, it enables a system to look up the addresses of other hosts on the network so it knows whom it is "talking" to and who is attempting to connect to it. Creation of user accounts is an integral part of server and workstation setup. The root (superuser) account should only be used when the privileges are needed for system maintenance. The Network Information System; formerly known as the "Yellow Pages"*, allows a system administrator to maintain a central collection of files with account, filesystem, host and other information. This allows changes to be propagated to many systems with minimal time and effort on the system administrator's part. NFS, the Network File System, allows sharing of files and directories with other UNIX machines, such as SunOS and Solaris*, SGI IRIX*, HP-UX and many others. The NFS protocol maintains the same permissions and ownerships of the files on both the server and clients, so that file security is maintained. Kerberos is an encrypted authentication protocol that allows users access to a system based on an authenticated ticket, without transmitting a plaintext password over the network. This prevents a would-be cracker from "sniffing" the password over a network connection. The Secure Shell protocol is an excellent replacement for telnet and ftp. It offers full end-to-end data encryption, which makes it an ideal solution for companies and individuals who deal with sensitive or private information. Ssh differs from kerberos because it uses the existing system authentication mechanisms, as opposed to the admin having to dedicate a server and create a database. Ssh contains builtin support for many authentication methods, including shadow, kerberos, SecurID, and TIS. It should be relatively easy for experienced system administrators to incorporate additional authentication methods as well. An SMTP (Simple Mail Transfer Protocol) server is required if a linux server is to act as an electronic mail gateway or relay. If users simply read mail on the machine, SMTP isn't required. Users can utilize IMAP (the Internet Message Access Protocol) or POP3 (Post Office Protocol) to retrieve their messages from the server. IMAP and POP3 are both server-to-client mail transports. They both accomplish the same goal in different ways. Samba is a package that allows Windows machines to print and share files with Linux or UNIX machines using native Windows file sharing. Users can map to a samba share on your Linux server the same way they would map to a network drive on a Windows NT server or workstation. A Few Examples of Integration
We plan to add more examples in the weeks to come. Please check back for updates. If you have any comments, questions, or suggestions, feel free to let us know. |
| ||||||||||||||||
| Community: | berlin + Geeks404 + Gimp + Helix Code + Stampede GNU/Linux |
| Find out about our hardworking staff | ©1999, 2000 Linux.com. Legal statement |