Website hosting mac, affordable, php5, plesk - linux experts blog

The Hardware Determining Your Hardware During the process of installation, Red Hat Linux may need some extra help to determine the exact hardware composition of your computer. To help it out, it is a good idea to make a note of the details on the following checklist, before you begin the installation: Keyboard type: The Red Hat Linux installation defaults to a standard US English 105-key keyboard. Unless you are using a language-specific keyboard like those used in many European and East Asian countries, you don’t have to worry about this detail. Mouse type: Red Hat Linux supports two-button and three-button mice, as well as wheel-mice and the cordless variety. It’s worth noting the exact make and nature of your mouse. Red Hat Linux also supports tablets; to verify that your make of tablet is compatible with Red Hat Linux, check the Hardware Compatibility List. Hard disk size: Make a note of the size of the hard disk that you’ll be installing Red Hat Linux onto. If the installation process fails to detect the hard disk size correctly, it might point to an underlying hardware problem. Also note that a Personal Desktop installation will require around 1.8GB of hard disk space to cater for the programs loaded during installation. If you plan to install other applications, then you will need more. Video (graphics) card: Note the chipset of the video card and the amount of RAM. While the Red Hat X-server configuration program can usually probe and detect the video card, it sometimes fails. If it does fail, you’ll need to tell Red Hat Linux the name of your video card chipset. Note that the video RAM is sometimes also displayed on the computer screen during boot up of the machine. Note If you can’t find the name of your video card chipset in the Hardware Compatability List (see below), don’t worry. Note that this means only that the GUI of Red Hat Linux is affected. Generally, if you intend to use the computer only as a server system, you’re recommended not to install any GUI - this is for reasons of resource load and security. If you do want a GUI, you’ll still be able to configure your machine to use the VESA interface for running the X-server. The VESA interface standard is supported by most of the commonly available video cards. Monitor: If you have an unusual monitor model, then the configuration of the GUI X Server software (during the installation process) might not detect it. Therefore, it’s worth noting information regarding your monitor. You’ll need the horizontal and vertical sync rates, which can generally be found either in the monitor manual or at the monitor manufacturer’s web site. Sound card: While the installation tries to detect the sound card, it sometimes doesn’t succeed. Therefore, it’s good to note the name of the sound card chipset in advance. Network card: During installation, Red Hat Linux tries to detect the network interface card (NIC) and load the appropriate software driver automatically. You should note the name of the chipset of the NIC in advance of installation, just in case the installation process fails to determine it. How do you get hold of this information? Well, if you have the technical specification documents that were supplied with your computer, then you’ll find the information in there. If not, then the machine’s existing operating system will probably offer some way of browsing the hardware being used. For example: In Windows 2000, you can find out about existing hardware via Start | Settings | Control Panel | System (select the Hardware tab, and click the Device Manager button). In other Linux systems, you can find out about existing hardware through via various menu options of the GUI. For example, try the options in Programs | Settings or Main Menu | System Tools, depending on which version of Linux you’re using. 15

Hint: This post is supported by Gama besplatan domen provider

Preparing for the Installation Preparing for the Installation While the installation process is quite straightforward, it is important that you do a little bit of preparation to ensure that the installation process goes as intended. Of course, you’ll need the necessary installation disks to install the system; but it’s also worth looking over your hardware too. In this section, we’ll examine both software and hardware aspects of preparation. The Software Of course, to begin you need to have the necessary software for the job. The Red Hat Linux 9 distribution can be obtained from a number of sources. Here are a couple of options: The Publisher’s Edition CD set included with this book. This includes all the CDs that you need for the installation process itself. In this chapter, we’ll look at installation using the CDs that are included in this pack. The official retail box set. This includes all the CDs that you need for the installation process itself. It also includes other CDs that contain the source code for all the packaged software, and a CD that contains Red Hat-supplied documentation. Much of the software on these disks can be freely copied and distributed, but only the customer who bought the CD is entitled to official technical support from Red Hat. The box set also includes an array of bonus software packaged by Red Hat, as well as some proprietary software that may not be freely distributed. The downloadable CD images. In the true spirit of Open Source (http://www.opensource.org), Red Hat also makes all the installation CDs downloadable for free public use. While the contents of the downloadable CD images are identical to those in the official box set, users of these CD images are not entitled to official technical support from Red Hat. These CD images can be obtained from any of Red Hat’s various mirror web sites. You can find a list of mirror FTP and HTTP sites at http://www.redhat.com/download/mirror.html. Alternatively, you can obtain the CD images from VA Linux’s extensive Sourceforge download mirror servers, at http://download.sourceforge.net/pub/mirrors/redhat. When you have the CD images, you can write them onto CD recordable disks (be sure to tell your CD-burning software that you’re burning CD images), and then you can use the CDs for installation. The Personal Desktop configuration of Red Hat Linux that is downloaded or in the boxed set requires all three binary installation CD disks during the installation. Moreover, as you begin to explore some of the many applications supplied with the Red Hat Linux 9 distribution, you’ll need these disks for installing the applications themselves. Therefore, it’s worth keeping all the three binary CD disks in your possession. The Hardware Before you start the installation, it’s a good idea to make a note of the hardware details of the machine you plan to use for your Linux installation. These details can help you to get the most out of the installation process, and even in detecting problems in the hardware configuration itself - problems that can prevent Red Hat Linux from installing correctly. 14

Hint: This post is supported by Gama besplatan domen provider

Chapter 1: Installing Red Hat Linux 9 Overview Installing an operating system is often a long, drawn-out process that requires a lot of upfront planning. Installation of traditional Unix-based operating systems seems to have been particularly painful in the past, requiring even experienced administrators to fret about partitions and drivers. Early versions of Linux were no different in this respect. The first version of Linux, back in 1993, could be booted up only using Minix (another Unix-like operating system). That version of Linux could support only the Finnish keyboard because the author of Linux didn’t have access to a US keyboard! However, since then Linux has grown by leaps and bounds. Each of the major distributions has put a lot of thought and effort into the Linux installation process, and today installing Linux for desktop use is, in common talk, a no-brainer. Red Hat, in particular, has caught the attention of the public, breaking away from the standard tradition of distributing disk images and pioneering the concept of distributing software in the form of packages. (Right now, the Red Hat Package Manager - RPM - is a standard in distribution of pre-compiled software packages in the Linux world, and we’ll learn more about the RPM in Chapter 4.) Red Hat has also been improving Linux usability and features in that most daunting area of any operating system - installation. The latest version of Red Hat Linux, version 9, is truly the most user-friendly ever, with extensive inputs from professional usability experts and a ravishing new look to attract even the most hardened of technophobes. The Red Hat Linux distribution offers four different configurations, and your choice will depend on how you plan to use the operating system: Personal desktop: This configuration is targeted at users who are new to Linux, or those who like to use Linux for day-to-day applications like office productivity tools and Internet browsing. This is the option we’ll install in this chapter. Workstation: This configuration is targeted at developers or system administrators. It provides various tools for software development and system management. Server: This configuration is mainly intended for systems that will not be used directly, but are primarily for offering network-based services like e-mail, file sharing, network connectivity, and web resources. Custom: This configuration is for experienced users who want more control over exactly what is installed onto their systems. The user can select which packages are to be installed and how the hard disks are to be used, and has control over various other configuration options that are pre-selected in the other three configurations. In this chapter, we are going to take a look at getting a Personal Desktop installation in place on a new computer. We are going to look at each step of the installation and the decisions that you would have to take at various stages of the installation to get a working Red Hat desktop in place. By the end of the chapter, you will have a desktop up and running that you will be able to use right away for your daily needs like Internet browsing, e-mail, and office productivity tools. 13
Note: If you are looking for cheapest and affordable webspace to host and run your servlet application check Astra servlet hosting services

Errata At p2p.wrox.com you will find a number of different lists that will help you, not only while you read this book, but also as you develop your own applications. To subscribe to a mailing list just follow this these steps: 1. Go to http://p2p.wrox.com/ and choose the appropriate category from the left menu bar. 2. Click on the mailing list you wish to join. 3. Follow the instructions to subscribe and fill in your e-mail address and password. 4. Reply to the confirmation e-mail you receive. 5. Use the subscription manager to join more lists and set your mail preferences. 12
Note: If you are looking for cheapest and affordable webspace to host and run your servlet application check Astra servlet hosting services

Errata updates and debugging. Therefore all the source code used in this book is available for download at http://www.wrox.com. Once you’ve logged on to the web site, simply locate the title (either through our Search facility or by using one of the title lists). Then click on the Download Code link on the book’s detail page and you can obtain all the source code. The files that are available for download from our site have been archived using both Linux’s File Roller archiving software and WinZip. When you have saved the attachments to a folder on your hard drive, you need to extract the files using a decompression program such as File Roller, WinZip, or PKUnzip. When you extract the files, the code is usually extracted into chapter folders. When you start the extraction process, ensure that you’ve selected the Use folder names under Extract to options (or their equivalents). Errata We have made every effort to make sure that there are no errors in the text or in the code. However, no one is perfect and mistakes do occur. If you find an error in this book, like a spelling mistake or a faulty piece of code, we would be very grateful to hear about it. By sending in errata, you may save another reader hours of frustration, and of course, you will be helping us provide even higher quality information. Simply e-mail the information to ; we’ll check the information, and (if appropriate) we’ll post a message to the errata pages, and use it in subsequent editions of the book. To find the errata page for this book, go to http://www.wrox.com/, and locate the title through our Search facility or title list. Then, on the book details page, click on the Book Errata link. On this page you will be able to view all the errata that has been submitted and checked through by editorial. You can also click the Submit Errata link on this page, to notify us of any errata that you have found. Technical Support If you would like to make a direct query about a problem in the book, you need to e-mail . A typical e-mail should include the following things: In the Subject field, tell us the book name, the last four digits of the ISBN (3784 for this book), and the number of the page on which the problem occurs. In the body of the message, tell us your name, contact information, and the problem. We won’t send you junk mail. We need these details to save your time and ours. Important Note that the Wrox support process can only offer support to issues that are directly pertinent to the content of our published title. Support for questions that fall outside the scope of normal book support is provided via the community lists of our http://p2p.wrox.com/ forum. p2p.wrox.com For author and peer discussion, join the P2P mailing lists. Our unique system provides programmer to programmer contact on mailing lists, forums, and newsgroups, all in addition to our one-to-one e-mail support system. Wrox authors and editors and other industry experts are present on our mailing lists. 11
Note: If you are looking for cheap and reliable provider to host and run your servlet application check Vision servlet hosting services

Customer Support to show a more substantial block of code (such as a script, or part of a script), then we display it like this: echo -n Deleting temporary files… rm -f *.tmp Sometimes, you will see code in a mixture of gray and white backgrounds, like this: echo -n Deleting temporary files… rm -f *.tmp echo Done. In cases like this, we use the gray shading to draw attention to a particular section of the code - perhaps because it is new code, or it is particularly important to this part of the discussion. We also use this style to show output that is displayed in the console window. We show commands typed at the command line, and their output, like this: $ cat bookdetail.txt Title: Beginning Red Hat Linux ISBN: 1861-00847-3 Authors: Bhattacharya, Gundavaram, Mamone, de Mauro, Sharma, Thomas, Whiting Commands that must be executed as root are shown with a # prompt, like this: # make install Advice, hints, and background information comes in an indented, italicized font like this. Important Important pieces of information (that you really shouldn’t ignore) come in boxes like this! Bulleted lists appear indented, with each new bullet marked as follows: Important words are in a bold type font. Words that appear on the screen, or in menus like the File or Window, are in a similar font to the one you would see in a Linux or Windows graphical user interface. Keys that you press on the keyboard, like Ctrl+C and Enter, are in italics. Customer Support We offer source code for download, errata, and technical support from our web site, http://www.wrox.com. In addition you can join mailing lists for author and peer discussion at p2p.wrox.com. Source Code and Updates As you work through the examples in this book, you may choose either to type in all the code by hand, or to use the source code that accompanies the book. Many readers prefer the former, because it’s a good way to get familiar with the coding techniques that are being used. Whether you want to type the code in or not, it’s useful to have a copy of the source code handy. If you like to type in the code, you can use our source code to check the results you should be getting - they should be your first stop if you think you might have typed in an error. By contrast, if you don’t like typing, then you’ll definitely need to download the source code from our web site! Either way, the source code will help you with 10
Note: If you are looking for cheap and reliable provider to host and run your servlet application check Vision servlet hosting services

Conventions in This Book respond accordingly. Now we examine the shell more closely, and look at combining commands into a script, defining the input to (and output from) a script, and how to build logical structures into scripts, get them to run in specific circumstances, and manage multiple tasks at the same time. Chapter 7 presents a detailed explanation of the Linux file system. We’ll talk about how to manage your files and directories, and how to use the shell to generate and manipulate the output from predefined or custom scripts. We’ll also talk about how Linux allows you to access the file systems of remote and detachable devices such as networked file systems, floppy disks, CD drives, and handheld devices, using a process known as mounting. Chapter 8 takes a closer look at user accounts and user groups, and how to manage them. This includes a discussion of permissions and privileges, and provides just enough on the basics of security to prepare us for Chapter 9. Chapter 9 describes how you might configure your Linux machine to provide services to other machines on a network. In particular, we’ll examine how to set your machine up as an FTP server, a web server, a file server, a printer server, a mail server, or a DHCP server. Chapter 10 covers some advanced administration topics. We’ll see how to analyze system log files, and use them to track down problems with the system. We’ll talk about backups and archives. We’ll expand on the discussion of tarballs in Chapter 4, to see how to install new applications from source code. We’ll also explore how to customize and recompile the Linux kernel - the heart of the operating system. Chapter 11 demonstrates how we can use scripting (and specifically, the Perl programming language) to automate the common task of managing the log files. The chapter presents a good handful of simple but useful Perl applications, with just enough explanation of the code to give you an idea of how each one works. If you’ve never used Perl before, then this chapter will help you to appreciate its power, flexibility, and potential - and it will also provide the inspiration to get you using Perl to work with your Linux operating system. Chapter 12 is all about security. Security is a complex topic; this chapter provides an introduction to a number of security-based topics as they relate to Red Hat Linux. Its purpose is to raise your awareness of the various issues you need to consider, problems you might encounter, and solutions and preventative measures to can employ to combat them. It describes how to secure your machine using a firewall, and how to get all the latest information about critical software updates by registering with the Red Hat Network Alert service. Chapter 13 presents a survey of some of the many other applications supported by Red Hat Linux 9, focusing in particular on system administration software and application development software. We’ll also take a closer look at some of the different open source licenses out there. At http://www.wrox.com, you’ll find a bonus chapter that explores in more detail the inner workings of the SysAdmin system administration program mentioned in Chapter 13. The SysAdmin application is written in Perl, and the complete source code for this application is available at http://www.wrox.com - allowing you both to install and use it to manage your own Linux machine, and to explore and experiment with the code for yourself. Conventions in This Book We have used certain layout and font styles in this book that are designed to help you to differentiate between the different kinds of information. Here are examples of the styles that are used, with an explanation of what they mean. As you’d expect, we present code in two different ways: in-line code and displayed code. When we need to mention keywords and other coding specifics within the text (for example, in discussion relating to an if … else construct or the GDI+ Graphics class) we use the single-width font as shown in this sentence. If we want 9
Note: If you are looking for good and quality webspace to host and run your java application check Actions java hosting services

What Is Covered in This Book? The following matrix demonstrates which versions are suited to which scenarios: Home Small Business Medium Business Large Business Enterprise Other Personal Professional Advanced Server Itanium Note For simplicity, the Enterprise entry in the table is a consolidation of different versions available from Red Hat; these are branded as AS, ES, & WS. For more information on these, take a look at http://www.redhat.com/software/rhel/. You’ll notice that we’ve used ticks to indicate where a version is suitable for a particular scenario, but we haven’t placed any crosses in the table. This is quite deliberate: if you’re the kind of power user who has a home network and wishes to use some of the advanced features offered only by the Advanced Server edition, then why not? The beauty of Linux is that it’s open and doesn’t demand anywhere near the hardware requirements expected of other operating systems. So that old machine you had hidden under your desk, destined for the rubbish heap, may be of use after all - dig it out, install Red Hat Linux 9, and use it as a web server or printer server! What Is Covered in This Book? Each chapter in this book builds upon the knowledge developed in earlier chapters, so that there’s a natural path through the book from beginning to end. As you gain confidence and begin to explore Linux further, you’ll also find that this arrangement of topics should help you use the book as a reference. Here’s a brief description of the chapters in this book: Chapter 1 takes you through the process of installing the operating system. It explains how to prepare for the installation, so that you don’t get any nasty surprises halfway through. It also explains each step of the installation process, so you know what it’s doing, and helps you to get exactly what you want from the installation. Chapter 2 introduces the basics of Linux. This chapter takes a tour of the desktop interface, so you can see exactly how to start using Linux. It also explains some fundamental topics that will help you to get the most out of your Linux machine - user accounts, the Linux file system, hardware configuration, and managing your machine’s resources. Chapter 3 discusses how to configure your Linux machine to connect to the Internet, or to a local area network, so that you can start to send and receive e-mails and use the Internet. Chapter 4 introduces the concept of packages. In order to use the components and applications that are supported by Red Hat Linux, we must first install the packages that contain them. This chapter will explain how to go about installing new packages, upgrading packages, and removing any packages that you don’t need. There are also many applications out there that are not available in package form, so we’ll also have a look at another common format - tarballs. In Chapter 5 we’ll start to explore the many applications that we can use on Linux to perform our everyday tasks - things like web browsers, office applications, and MP3 players. This chapter introduces just a small proportion of the bewildering array of applications that come with Red Hat Linux 9, and explains where you can find more! Chapter 6 tackles the notion of the shell. In fact, you will have been using the shell already in the first five chapters of the book, to type commands and execute them, so that Linux can run them and 8
Note: If you are looking for good and quality webspace to host and run your java application check Actions java hosting services

What Is Red Hat Linux 9? In addition to the numerous security applications (such as firewalls) available, many Linux distributions are specifically created with a view to providing a highly secure environment. Examples include the Immunix OS (http://www.immunix.com - a commercially available hardened Linux) and Bastille Linux (http://www.bastille-linux.org - a hardening script that can be run on your Linux machine after installation). Standards and support: Linux’s compliance with both Unix standards allows it to interoperate with a number of different operating systems and file systems. Linux can talk to Netware, Macintosh, and Windows networks with ease. GNU software support: There is a wide variety of software freely available through the GNU project - including development software, office applications, system administration tools, and so on. The OpenOffice suite of applications is one such example and is covered in more detail in Chapter 5. You’ll come across others over the course of this book, and we survey a selection of open source applications in Chapter 13. GUI support: If you like to communicate with your operating system through a nice graphical user interface (GUI) with windows, panels, and menus, then Linux will satisfy you. Whether you’re using the GUI to increase productivity or just for fun, you can choose from a number of GUIs, including Bluecurve, KDE, and GNOME. Moreover, Linux does not force you to use the operating system GUI, and for those who are prepared to explore the command line interface (CLI) the benefits include greater flexibility and lower overheads. It’s for this reason that many server administrators in serious production environments eschew the GUI in favor of better flexibility and performance. Cost: Linux is freely available - what more can you say?! And if you’re a business customer, the healthy vendor competition makes for very reasonable support contract prices. What Is Red Hat Linux 9? As we’ve already mentioned, a number of organizations have created distributions of Linux. Typically, a Linux distribution includes a specific version of the Linux kernel, a collection of components and applications, an installation program (the type of thing more commonly associated with the Windows platform), and often some kind of support arrangement. One of the most popular distributions comes from Red Hat Inc. - indeed, depending on which of the independent studies market reports you read, Red Hat currently holds more than 50% of the Linux vendor market. Red Hat Linux comes in a variety of different versions, including: Personal Edition (currently at version 9) Professional Edition (currently at version 9) Advanced Server (currently at version 2.1) Itanium (64-bit processor - currently at version 7.2) Each version contains features appropriate to certain scenarios; these are: Small office or home Small or medium business Enterprise or corporate applications 7
Note: If you are looking for best quality webspace to host and run your tomcat application check Vision tomcat hosting services

Why Choose Linux? It doesn’t exactly sound like the kind of system you use for your home accounts, does it? However, there is one very significant thing about the release of this software: it was released under the GNU General Public License, which allowed the source code to be distributed freely to anyone who wanted it, and also allowed these people to extend it at will. Very quickly, communities of interested programmers and testers took Linus’s original code, and extended it in all manner of ways. They expanded the range of hardware configurations on which Linux could run, they swelled the range of software written for Linux, and they improved the stability of the whole Linux system. This support and development has continued right up to the present day, spreading worldwide and encompassing whole communities of developers. Of course, this phenomenon, and its potential, has been noticed in the commercial sector, and now Linux has a healthy complement of commercial vendors achieving the seemingly impossible - doing business by selling a product that is essentially free! Of course, in order to do this, these organizations (which include SuSe, Debian, Mandrake, Red Hat, and so on) have been required to innovate and add value to the basic Linux package. The various distributions, packages, and add-ons created by these organizations have matured alongside the basic Linux operating system itself. The latest Red Hat Linux release - version 9 - is a perfect example of this innovation. While it’s available for free download, Red Hat also sells the package in a variety of forms. For home users there’s a boxed set of CDs containing the Linux operating system, a huge assortment of open source productivity software, Red Hat’s patented Bluecurve interface, and a Demo subscription to Red Hat Network - the vendor’s support, updating, and information network. For corporate users the deal is much the same, but with the emphasis placed more firmly upon support. Finally, through the combined efforts of both individual developer communities and distribution vendors, there are now Linux versions available that can compete on a level playing field with proprietary software such as Microsoft Windows. This means that Linux is a serious contender both on your home PC and in large-scale production situations. Why Choose Linux? Why might you choose Linux for your operating system, rather than one of its competitors? Here are a few points you might like to consider: Size and speed: A basic Linux installation can consume as little as 475MB of hard disk space and will run quite happily on as little as 6432MB of RAM. Compare this to Unix (which often requires more than 500MB) or Microsoft Windows 2000 (which recommends a minimum 2GB hard disk and 128MB RAM). The difference is due to the efficiency of the Linux operating system and (most of) the applications that run on it. Security: One significant reason for Linux’s excellent reputation as a secure environment is that its source code is completely accessible, and continues to be viewed by many pairs of eyes. Linux’s open source standpoint means that people other than the vendor can check for incomplete or tampered source code. The more people that study Linux’s source code, the more bugs (and security flaws) can be spotted. Of course, that’s only half the story - the other half is that the infrastructure is in place for easy bug-reporting, discussion, and bug-fixing. The result of all this is that more of the bugs get spotted more quickly, and they’re fixed faster. 6
Note: If you are looking for best quality webspace to host and run your tomcat application check Vision tomcat hosting services