LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

1. trying to get rid of all the quotes. 

2. Addedin credit.
3. Needs to have a lot of editing to make it shorter as there is a lot of repeats which make it more confusing
This commit is contained in:
dude 2004-04-22 03:41:22 +00:00
parent ab4b90047f
commit b7cb93c41c
1 changed files with 148 additions and 84 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

232
LDP/howto/docbook/Win+BSD+Linux-Install-HOWTO.xml
View File

@ -14,6 +14,11 @@ Windows+BSD+Linux Installation Guide</title>
<address><email>subhasish_ghosh([A][T])linuxwaves[DOT]com</email></address>
</affiliation>
</author>
<othercredit role='converter'>
<firstname>Gerardo</firstname>
<surname>Arnaez</surname>
<contrib>Coversion from html to Docbook xml 4.2</contrib>
</othercredit>
</authorgroup>
<revhistory>
<revision>
@ -120,7 +125,7 @@ I would like to thank all the following people and projects without the help and
<para>Tabatha Persad (tabatha at merlinmonroe dot com), Linux Documentation Project Review Coordinator, for technical reviews and for answering my million queries.</para>
</listitem>
<listitem>
<para>Michael K. Johnson (johnsonm at redhat dot com), for the excerpt from his "Linux Information Sheet" at the TLDP site, mentioned in Chapter 1 of this guide on Linux.</para>
<para>Michael K. Johnson (johnsonm at redhat dot com), for the excerpt from his <quote>Linux Information Sheet</quote> at the TLDP site, mentioned in Chapter 1 of this guide on Linux.</para>
</listitem>
<listitem>
<para>Microsoft Corporation for using important information on Microsoft tools and technologies mentioned in Chapter 2 of the guide.</para>
@ -158,12 +163,12 @@ Although the information given in this document is believed to be correct, the a
<para>
Copyright (c) 2003, Subhasish Ghosh</para>
<para>
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is located at www.gnu.org/copyleft/fdl.html, in the section entitled "GNU Free Documentation License".</para>
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is located at www.gnu.org/copyleft/fdl.html, in the section entitled <quote>GNU Free Documentation License</quote>.</para>
</section>
<section>
<title>About the Author</title>
<para>
Subhasish "savvy" Ghosh has been working with GNU/Linux and FreeBSD (and more recently OpenBSD, NetBSD, Sun Solaris and other UNIX-variant) operating systems for the past 7 years or so since schooldays. Currently, aged 22, Ghosh is an engineering student at the Moscow Power Engineering Institute (Technical University) at Moscow, Russian Federation; specializing in the field of "Informatics and Computer Science engineering". He is a Microsoft Certified Professional (MCP), MCSD, MCP Certified on NT 4.0; additionally has a host of other GNU/Linux and computer-industry related certifications. His web page can be accessed at http://groups.msn.com/Linuxdump.</para>
Subhasish <quote>savvy</quote> Ghosh has been working with GNU/Linux and FreeBSD (and more recently OpenBSD, NetBSD, Sun Solaris and other UNIX-variant) operating systems for the past 7 years or so since schooldays. Currently, aged 22, Ghosh is an engineering student at the Moscow Power Engineering Institute (Technical University) at Moscow, Russian Federation; specializing in the field of <quote>Informatics and Computer Science engineering</quote>. He is a Microsoft Certified Professional (MCP), MCSD, MCP Certified on NT 4.0; additionally has a host of other GNU/Linux and computer-industry related certifications. His web page can be accessed at http://groups.msn.com/Linuxdump.</para>
</section>
</chapter>
<chapter>
@ -172,7 +177,7 @@ Subhasish "savvy" Ghosh has been working with GNU/Linux and FreeBSD (and more re
Readers have questions. Thus, this FAQ section has been included for answering some of the most obvious questions from the reader's point of view. All readers are requested to read through this section for finding answers to their personal questions.</para>
<para>
After reading through this FAQ entirely, if the reader feels that
he/she still has a "question" or two to ask, please feel free to drop
he/she still has a <quote>question</quote> or two to ask, please feel free to drop
a line at subhasish_ghosh@linuxwaves.com.</para>
<qandaset>
@ -186,10 +191,10 @@ a line at subhasish_ghosh@linuxwaves.com.</para>
</qandaentry>
<qandaentry>
<question>
<para>Why have you used "3" operating systems for this guide?</para>
<para>Why have you used three operating systems for this guide?</para>
</question>
<answer>
<para>The current scenario is such that Microsoft Windows operating systems rule the desktops, with GNU/Linux distributions and *BSD releases (FreeBSD/OpenBSD/NetBSD) competing for "total world domination" in the server markets, thus, I thought it would be the absolute best to include all of them in this guide. The first OS is a Microsoft Windows OS, the second one belonging to the *BSD family and the last one a commonly used GNU/Linux distribution (Red Hat). Thus, the number of OSes ended up with "3".</para>
<para>The current scenario is such that Microsoft Windows operating systems rule the desktops, with GNU/Linux distributions and *BSD releases (FreeBSD/OpenBSD/NetBSD) competing for <quote>total world domination</quote> in the server markets, thus, I thought it would be the absolute best to include all of them in this guide. The first OS is a Microsoft Windows OS, the second one belonging to the *BSD family and the last one a commonly used GNU/Linux distribution (Red Hat). Thus, the number of OSes ended up with three.</para>
</answer>
</qandaentry>
<qandaentry>
@ -198,15 +203,15 @@ a line at subhasish_ghosh@linuxwaves.com.</para>
</question>
<answer>
<para>
I assure everyone that I tested each and every step mentioned in this guide on my personal computer systems. Later they were tested successfully on other computers with varying configurations as well. My computer has a 266.87 MHz Intel Pentium 2 processor, 64MB Physical DIMM RAM, a single 20.0 GB Maxtor IDE HDD and other usual accessories which runs Microsoft Windows 98 (SE), FreeBSD 5.1-RELEASE and Red Hat Linux 8.0. The other one with pretty much the same configuration runs FreeBSD 4.8-RELEASE, OpenBSD 3.2-RELEASE and Red Hat Linux 8.0. The general rule of the thumb is: "Better the resources, better the performance of the computer".</para>
I assure everyone that I tested each and every step mentioned in this guide on my personal computer systems. Later they were tested successfully on other computers with varying configurations as well. My computer has a 266.87 MHz Intel Pentium 2 processor, 64MB Physical DIMM RAM, a single 20.0 GB Maxtor IDE HDD and other usual accessories which runs Microsoft Windows 98 (SE), FreeBSD 5.1-RELEASE and Red Hat Linux 8.0. The other one with pretty much the same configuration runs FreeBSD 4.8-RELEASE, OpenBSD 3.2-RELEASE and Red Hat Linux 8.0. The general rule of the thumb is: <quote>Better the resources, better the performance of the computer.</quote></para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>All your installations are "CD-ROM" based installation types. What about "Ethernet", "FTP", "HTTP", "NFS" installation types?</para>
<para>All your installations are CD-ROM based installation types. What about Ethernet, FTP, HTTP, NFS installation types?</para>
</question>
<answer>
<para>I decided to keep the guide as simple as possible. And since most of us usually use CDs from local CD-ROMs for installing operating systems, I have assumed that the reader undertakes a CD-ROM based installation for installing the covered operating systems. Moreover, this guide is intended for all types of users, ranging from intermediate Linux users to the experienced Unix experts. Since, NFS, HTTP, FTP and other such installation types usually require networks with servers running, which is impossible for an ordinary home-user to access, I have only covered the CD-ROM based installation types. Sorry for the inconvenience caused to the "network" lovers.</para>
<para>I decided to keep the guide as simple as possible. And since most of us usually use CDs from local CD-ROMs for installing operating systems, I have assumed that the reader undertakes a CD-ROM based installation for installing the covered operating systems. Moreover, this guide is intended for all types of users, ranging from intermediate Linux users to the experienced Unix experts. Since, NFS, HTTP, FTP and other such installation types usually require networks with servers running, which is impossible for an ordinary home-user to access, I have only covered the CD-ROM based installation types. Sorry for the inconvenience caused to the network lovers.</para>
</answer>
</qandaentry>
<qandaentry>
@ -216,7 +221,12 @@ Why would anyone ever need to run 3 operating systems on the same hard disk of a
</question>
<answer>
<para>
For lots of reasons. Fun, for learning new installing and booting methodologies, for gaining inside knowledge of "multi-booting", partitioning schemes, boot loaders and so on, or simply because you just cannot afford 2 separate 40.0 GB hard disk drives for the 3 different operating systems you want to tinker with. As for me, I guess the last reason "suits" the best.</para>
For lots of reasons. Fun, for learning new installing and
booting methodologies, for gaining inside knowledge of
multi-booting, partitioning schemes, boot loaders and so on,
or simply because you just cannot afford 2 separate 40.0 GB
hard disk drives for the 3 different operating systems you
want to tinker with. As for me, I guess the last reason suits the best.</para>
<para>
Lastly, if you do want, you can always install and configure your computer system with 3 varying operating systems installed in 2 separate hard disks.</para>
</answer>
@ -228,7 +238,7 @@ Why Red Hat? Why NOT Debian GNU/Linux, Slackware, Caldera, SuSE, TurboLinux and
</question>
<answer>
<para>
Since most of my past Linux projects and work in general had been related to the Red Hat Linux distribution; continually installing, configuring and administering Red Hat Linux personal desktops and workstations. Currently, Red Hat Linux is "the" leading Linux solutions provider in the world, with big corporate real-time systems being implemented using the Red Hat operating system software. Moreover, Red Hat documentation and support are easy to find. Thus, Red Hat Linux has been chosen. The other distributions, namely Debian GNU/Linux, Slackware and Mandrake are good, and I will probably add more sections covering other Linux distributions later.</para>
Since most of my past Linux projects and work in general had been related to the Red Hat Linux distribution; continually installing, configuring and administering Red Hat Linux personal desktops and workstations. Currently, Red Hat Linux is <emphasis>the</emphasis> leading Linux solutions provider in the world, with big corporate real-time systems being implemented using the Red Hat operating system software. Moreover, Red Hat documentation and support are easy to find. Thus, Red Hat Linux has been chosen. The other distributions, namely Debian GNU/Linux, Slackware and Mandrake are good, and I will probably add more sections covering other Linux distributions later.</para>
</answer>
</qandaentry>
<qandaentry>
@ -238,7 +248,7 @@ Why FreeBSD, OpenBSD and NetBSD operating systems? Why not BSD/OS, Darwin, Irix,
</question>
<answer>
<para>
I personally have networking and source-code hacking experience on FreeBSD and OpenBSD boxes. And, more recently have access to NetBSD 1.6.1 and Sun Microsystems' SunOS operating system in the Solaris Operating Environment. I do "not" have any experience working with Irix, Ultrix, Minix, HP-UX, IBM-AIX, Darwin and others. Thus, FreeBSD, OpenBSD and NetBSD have been chosen.</para>
I personally have networking and source-code hacking experience on FreeBSD and OpenBSD boxes. And, more recently have access to NetBSD 1.6.1 and Sun Microsystems' SunOS operating system in the Solaris Operating Environment. I do <emphasis>not</emphasis> have any experience working with Irix, Ultrix, Minix, HP-UX, IBM-AIX, Darwin and others. Thus, FreeBSD, OpenBSD and NetBSD have been chosen.</para>
</answer>
</qandaentry>
<qandaentry>
@ -258,7 +268,7 @@ I installed 3 operating systems in my computer as you have illustrated in this g
</question>
<answer>
<para>
Well, first my "deepest" condolences on your data-loss and for all this apparent mess. I would love to take all the responsibility, but as it is, I have enough problems of my own to handle. Thus, I am "not" ready to take the responsibility for anything that goes wrong anywhere. At the least, I can say, that all the steps and methods mentioned in this guide have been tested thoroughly on a number of systems with varying configurations, and no problems have been noted so far.</para>
Well, first my deepest condolences on your data-loss and for all this apparent mess. I would love to take all the responsibility, but as it is, I have enough problems of my own to handle. Thus, I am not ready to take the responsibility for anything that goes wrong anywhere. At the least, I can say, that all the steps and methods mentioned in this guide have been tested thoroughly on a number of systems with varying configurations, and no problems have been noted so far.</para>
</answer>
</qandaentry>
<qandaentry>
@ -268,7 +278,7 @@ You used the GNU GRUB for booting all the 3 operating systems. May I know the re
</question>
<answer>
<para>
As known to everyone, boot loaders play a very vital role while configuring multiple-booting systems where you can use any suitable boot loader which is capable of booting multiple operating systems. I chose GRUB in this guide for three specific reasons: 1) GNU GRUB is the "default" boot loader in Red Hat distribution releases currently. 2) As mentioned in the 'Release Notes' of Red Hat Linux 8.0, the use of LILO is deprecated and the package would be removed from one of its future releases. 3) GRUB is a very powerful (x86) PC-compatible boot loader which supports a number of operating systems "directly" and other proprietary ones too via "chain-loading" for booting them. Thus, GRUB is used instead of other boot loaders.</para>
As known to everyone, boot loaders play a very vital role while configuring multiple-booting systems where you can use any suitable boot loader which is capable of booting multiple operating systems. I chose GRUB in this guide for three specific reasons: 1) GNU GRUB is the <emphasis>default</emphasis> boot loader in Red Hat distribution releases currently. 2) As mentioned in the 'Release Notes' of Red Hat Linux 8.0, the use of LILO is deprecated and the package would be removed from one of its future releases. 3) GRUB is a very powerful (x86) PC-compatible boot loader which supports a number of operating systems directly and other proprietary ones too via chain-loading for booting them. Thus, GRUB is used instead of other boot loaders.</para>
</answer>
</qandaentry>
<qandaentry>
@ -278,7 +288,7 @@ I have older Red Hat, FreeBSD and OpenBSD distributions and/or releases. Will th
</question>
<answer>
<para>
I am sure they would with a few modifications at places. All steps mentioned should behave in a normal manner if you are using Kernel 2.2.x or higher (for Linux). For FreeBSD users, if you are using not earlier than 4.X-RELEASES, there should not be any problems whatsoever. Just take a deep breath, and start doing as given in this guide. If in case, at some place it does "not" work, make sure you are using the right step and commands etc. Most times, it is human error rather than computer-related error which lets big servers and networks down. Always remember this!</para>
I am sure they would with a few modifications at places. All steps mentioned should behave in a normal manner if you are using Kernel 2.2.x or higher (for Linux). For FreeBSD users, if you are using not earlier than 4.X-RELEASES, there should not be any problems whatsoever. Just take a deep breath, and start doing as given in this guide. If in case, at some place it does not work, make sure you are using the right step and commands etc. Most times, it is human error rather than computer-related error which lets big servers and networks down. Always remember this!</para>
</answer>
</qandaentry>
<qandaentry>
@ -288,7 +298,7 @@ I would like to have access to good resources on Linux and FreeBSD. Could you su
</question>
<answer>
<para>
Yes, definitely I could. There is a lot of very good technical information on all the "open-source" operating systems out there on the Internet. For Linux, make sure you often visit http://www.linuxgazette.com, http://www.linuxfocus.org, http://www.linux.com and a host of others. Besides, "The Linux Documentation Project" (TLDP) provides excellent resources on all topics related to GNU/Linux. As for printed books, these are some of my absolute favorites: Red Hat Linux 8.0 Bible, Understanding the Linux Kernel, Modern Operating Systems, Linux Kernel Programming, The FreeBSD Handbook at http://www.freebsd.org, The Design of the UNIX Operating System, The Design and Implementation of the 4.4BSD Operating System. That would be enough for the time-being!</para>
Yes, definitely I could. There is a lot of very good technical information on all the open-source operating systems out there on the Internet. For Linux, make sure you often visit http://www.linuxgazette.com, http://www.linuxfocus.org, http://www.linux.com and a host of others. Besides, The Linux Documentation Project (TLDP) provides excellent resources on all topics related to GNU/Linux. As for printed books, these are some of my absolute favorites: Red Hat Linux 8.0 Bible, Understanding the Linux Kernel, Modern Operating Systems, Linux Kernel Programming, The FreeBSD Handbook at http://www.freebsd.org, The Design of the UNIX Operating System, The Design and Implementation of the 4.4BSD Operating System. That would be enough for the time-being!</para>
</answer>
</qandaentry>
<qandaentry>
@ -304,17 +314,17 @@ I have a few suggestions, new ideas and exciting comments. Can I send them to yo
<qandaentry>
<question>
<para>
I have "installation-specific" questions/queries or something "failed" or "this quite didn't work"? Can I send these reports to you?</para>
I have <emphasis>installation-specific</emphasis> questions/queries or something <emphasis>failed</emphasis> or <emphasis>this quite didn't work?</emphasis> Can I send these reports to you?</para>
</question>
<answer>
<para>
Of course do. But please be patient, cause I am busy with lots of things at my university; tests, exams, assignments, dating my "infinitely patient FreeBSD-compatible rock-stable girlfriend", maintaining this guide, other Linux assignments etc. So, I cannot promise to get back to you immediately. I need some time solving your problems.</para>
Of course do. But please be patient, cause I am busy with lots of things at my university; tests, exams, assignments, dating my <quote>infinitely patient FreeBSD-compatible rock-stable girlfriend</quote>, maintaining this guide, other Linux assignments etc. So, I cannot promise to get back to you immediately. I need some time solving your problems.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Will you be updating this guide from time to time? Will "my" problems be listed here?</para>
Will you be updating this guide from time to time? Will <emphasis>my</emphasis> problems be listed here?</para>
</question>
<answer>
<para>
@ -344,11 +354,11 @@ Does this guide have any newest version on the Internet?</para>
<qandaentry>
<question>
<para>
(For people of Russia) We love Microsoft Windows, FreeBSD and OpenBSD operating systems. But "why" have you NOT used the common Russian GNU/Linux distributions? I mean "ASP Linux", "Black Cat Linux", "ALT Linux" and others?</para>
(For people of Russia) We love Microsoft Windows, FreeBSD and OpenBSD operating systems. But Why have you NOT used the common Russian GNU/Linux distributions? I mean ASP Linux, Black Cat Linux, ALT Linux and others?</para>
</question>
<answer>
<para>
All the above-mentioned GNU/Linux distributions are basically Red Hat-based Linux distributions. They heavily rely on Red Hat for package installation procedures, Kernel hacking, Kernel updates etc. I have used ASP Linux 7.2 myself, and though it does offer a few new and exciting features, but I personally prefer working with Red Hat Linux. I have "no" experience using Black Cat and ALT GNU/Linux distributions.</para>
All the above-mentioned GNU/Linux distributions are basically Red Hat-based Linux distributions. They heavily rely on Red Hat for package installation procedures, Kernel hacking, Kernel updates etc. I have used ASP Linux 7.2 myself, and though it does offer a few new and exciting features, but I personally prefer working with Red Hat Linux. I have no experience using Black Cat and ALT GNU/Linux distributions.</para>
</answer>
</qandaentry>
</qandaset>
@ -357,7 +367,7 @@ Does this guide have any newest version on the Internet?</para>
<title>
Organization</title>
<para>
The content of this guide has been split into 7 distinct sections called "Chapters" as illustrated below for ease of searching and reading on behalf of the reader. The reader is expected to choose any one Microsoft Windows operating system from the list mentioned in Chapter 2, thus the other sections regarding Microsoft Windows operating systems could be skipped "without" any risk at all. After the reader has chosen which Microsoft operating system to install, he/she can proceed with the installation, then proceed with the FreeBSD/OpenBSD/NetBSD and Linux installations sequentially.</para>
The content of this guide has been split into 7 distinct sections for ease of searching and reading on behalf of the reader. The reader is expected to choose any one Microsoft Windows operating system from the list mentioned in Chapter 2, thus the other sections regarding Microsoft Windows operating systems could be skipped without any risk at all. After the reader has chosen which Microsoft operating system to install, he/she can proceed with the installation, then proceed with the FreeBSD/OpenBSD/NetBSD and Linux installations sequentially.</para>
<para>
Chapter 1: The first Chapter, About the operating systems covers a brief discussion on Windows operating system family (I chose to speak a few words on Microsoft Windows XP Professional), Linux, FreeBSD, OpenBSD and NetBSD operating systems. General information on each operating system, legal stuff etc. is discussed. For more official and exhaustive information, refer to the official web-sites of the products and projects listed there.</para>
<para>
@ -365,7 +375,7 @@ Chapter 2: The second Chapter, Installing Microsoft Windows covers the installat
<para>
Chapter 3: The third Chapter, Installing FreeBSD 5.1-RELEASE covers topics required for installing and configuring FreeBSD 5.1-RELEASE with the already existing Microsoft Windows operating system. If the reader chooses to install OpenBSD 3.2-RELEASE instead of FreeBSD 5.1-RELEASE, he/she may skip this chapter and proceed to the next chapter.</para>
<warning>
<para>WARNING: Since both FreeBSD and OpenBSD operating systems are POSIX compliant BSD-derivatives, both use the same BSD-style hard disk partitioning and labeling schemes, and both have the same set of commands when viewed from the user-level. Thus, partitioning and filesystems naming covered in FreeBSD section will not be repeated in the next chapter. If it so happens that you are a complete OpenBSD newbie or the term "OpenBSD" sounds like a Greek mythology character, it is best for you to go through all the information in this chapter and install and configure FreeBSD. The OpenBSD installation, though simple and neat, is a text-based installation procedure completely and assumes a sound knowledge of hardware, BSD-style hard disk slicing and labeling schemes. Messing up at any one stage, messes up the entire installation and may even render the Microsoft Windows operating system (installed initially) totally inaccessible. Experience has taught me to keep proper backup when doing such installations. Do not send problem reports later. You have been warned!</para>
<para>WARNING: Since both FreeBSD and OpenBSD operating systems are POSIX compliant BSD-derivatives, both use the same BSD-style hard disk partitioning and labeling schemes, and both have the same set of commands when viewed from the user-level. Thus, partitioning and filesystems naming covered in FreeBSD section will not be repeated in the next chapter. If it so happens that you are a complete OpenBSD newbie or the term <quote>OpenBSD</quote> sounds like a Greek mythology character, it is best for you to go through all the information in this chapter and install and configure FreeBSD. The OpenBSD installation, though simple and neat, is a text-based installation procedure completely and assumes a sound knowledge of hardware, BSD-style hard disk slicing and labeling schemes. Messing up at any one stage, messes up the entire installation and may even render the Microsoft Windows operating system (installed initially) totally inaccessible. Experience has taught me to keep proper backup when doing such installations. Do not send problem reports later. You have been warned!</para>
</warning>
<para>
Chapter 4: The fourth Chapter, Installing OpenBSD 3.2-RELEASE covers topics required for installing and configuring OpenBSD 3.2-RELEASE with the already existing Microsoft Windows operating system. If the reader chooses to install FreeBSD 5.1-RELEASE instead of OpenBSD 3.2-RELEASE, he/she may skip this chapter and take a peek into the earlier chapter. Partitioning and essential booting process details etc. is discussed herein.</para>
@ -386,7 +396,7 @@ the Linux/FreeBSD/OpenBSD/NetBSD or in general terms, the Open-Source
community.</para>
<section>
<title> Microsoft Windows</title>
<para> Microsoft Corp. has a long (yet fatally weak and buggy) list of operating systems, targets ranging from the mild and feeble home-user to the truly multi-tasking, multi-processing, multi-programming, fault-tolerant, hack-resilient real-time systems; from MS Windows 95 to the most recently launched Microsoft Windows Server 2003. The reader is free to choose any operating system according to his/her own personal taste and/or targeted environment. I personally do "not" consider Microsoft Windows 2000 family of operating systems (Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server and Windows 2000 DataCenter server) a very good choice for "corporate" environments. If the PASSME theme of Software engineering is considered, where PASSME = Performance, Availability, Scalability, Security, Maintainability and Extensibility features of any software under scrutiny; Microsoft Windows 2000 servers (and operating systems, in general) are rated much lower than UNIX SVR4, *BSDs, Sun Solaris, Linux and any of the other commercial variants of UNIX like IBM-AIX, HP-UX, Digital UNIX, Tru64 UNIX, SGI-Irix and so on.</para>
<para> Microsoft Corp. has a long (yet fatally weak and buggy) list of operating systems, targets ranging from the mild and feeble home-user to the truly multi-tasking, multi-processing, multi-programming, fault-tolerant, hack-resilient real-time systems; from MS Windows 95 to the most recently launched Microsoft Windows Server 2003. The reader is free to choose any operating system according to his/her own personal taste and/or targeted environment. I personally do <emphasis>not</emphasis> consider Microsoft Windows 2000 family of operating systems (Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server and Windows 2000 DataCenter server) a very good choice for corporate environments. If the PASSME theme of Software engineering is considered, where PASSME = Performance, Availability, Scalability, Security, Maintainability and Extensibility features of any software under scrutiny; Microsoft Windows 2000 servers (and operating systems, in general) are rated much lower than UNIX SVR4, *BSDs, Sun Solaris, Linux and any of the other commercial variants of UNIX like IBM-AIX, HP-UX, Digital UNIX, Tru64 UNIX, SGI-Irix and so on.</para>
</section>
<section>
@ -397,8 +407,10 @@ community.</para>
kernel, originally written by Linus Benedict Torvalds, is a
UNIX-clone, which is POSIX compliant and was initially targeted
towards the Intel x86 architecture. As rightly mentioned in the
"Linux Information Sheet" by Michael K. Johnson at
http://www.tldp.org, "...Linux is a completely free
<emphasis>Linux Information Sheet</emphasis> by Michael K. Johnson at
http://www.tldp.org, <blockquote>
<para>
"...Linux is a completely free
reimplementation of the POSIX specification, with SYSV and BSD
extensions (which means it looks like Unix, but does not come
from the same source code base), which is available in both
@ -406,33 +418,47 @@ community.</para>
Torvalds ; and other contributors, and is freely redistributable
under the terms of the GNU General Public License (GPL). A copy
of the GPL is included with the Linux source; you can also get a
copy from ftp://prep.ai.mit.edu/pub/gnu/COPYING...". </para>
copy from ftp://prep.ai.mit.edu/pub/gnu/COPYING...".</para>
</blockquote></para>
<para>
Readers must note the fact that though many Linux users worldwide refer to the GNU/Linux operating system simply as "Linux", it is more appropriate to refer to the operating system as a GNU/Linux system and when talking about the kernel in particular just to call it Linux. Moreover, a very popular misconception amongst new Linux users is: "Hey! Linux is UNIX!". No, absolutely "not". Once again, readers must note: The Linux kernel is a UNIX-clone, in other words a reimplementation of the UNIX-Kernel, but it is not UNIX itself. On the other hand, the BSDs, FreeBSD and OpenBSD for example, are not kernels merely. They are more closer to the real UNIX (AT&amp;Ts Official Release UNIX SVR4). They represent an entire operating system with a whole set of applications, tools, user utilities, shells, games, documentation, developer utilities, system and user-level binaries and full source code for the operating systems.</para>
Readers must note the fact that though many Linux users worldwide refer to the GNU/Linux operating system simply as <emphasis>Linux,</emphasis> it is more appropriate to refer to the operating system as a GNU/Linux system and when talking about the kernel in particular just to call it Linux. Moreover, a very popular misconception amongst new Linux users is: <quote>Hey! Linux is UNIX!.</quote> No, absolutely not. Once again, readers must note: The Linux kernel is a UNIX-clone, in other words a reimplementation of the UNIX-Kernel, but it is not UNIX itself. On the other hand, the BSDs, FreeBSD and OpenBSD for example, are not kernels merely. They are more closer to the real UNIX (AT&amp;Ts Official Release UNIX SVR4). They represent an entire operating system with a whole set of applications, tools, user utilities, shells, games, documentation, developer utilities, system and user-level binaries and full source code for the operating systems.</para>
</section>
<section>
<title>*BSD's</title>
<section>
<title>FreeBSD</title>
<para>
FreeBSD which stands for the Free version of Berkeley Software Distribution operating system software (though all the BSDs out there are "open-source" or "free" in nature except BSD/OS) is technically speaking, the most powerful, professional quality and advanced UNIX-compatible operating system software on earth today. FreeBSD is originally based on 4.4BSD-Lite (with a minor inclusion from the 4.4BSD-Lite2 code base too), developed at the University of California, Berkeley, under the authorization of the Computer Systems Research Group (CSRG), Computer Science Division, Department of Electrical Engineering and Computer Science at Berkeley. FreeBSD operating system (just like a Linux distribution) comes with a whole set of packages, including user applications, tools, user utilities, shells, games, documentation, developer utilities, system and user-level binaries and full source code for the operating systems. The FreeBSD Project web-site can be accessed at: http://www.freebsd.org.</para>
FreeBSD which stands for the Free version of Berkeley Software
Distribution operating system software (though all the BSDs out there
are <emphasis>open-source</emphasis> or <emphasis>free</emphasis> in nature except BSD/OS) is technically speaking, the most powerful, professional quality and advanced UNIX-compatible operating system software on earth today. FreeBSD is originally based on 4.4BSD-Lite (with a minor inclusion from the 4.4BSD-Lite2 code base too), developed at the University of California, Berkeley, under the authorization of the Computer Systems Research Group (CSRG), Computer Science Division, Department of Electrical Engineering and Computer Science at Berkeley. FreeBSD operating system (just like a Linux distribution) comes with a whole set of packages, including user applications, tools, user utilities, shells, games, documentation, developer utilities, system and user-level binaries and full source code for the operating systems. The FreeBSD Project web-site can be accessed at: http://www.freebsd.org.</para>
<para>
Recently, a lot of media spotlight has put the GNU/Linux system (more specifically the Linux Kernel) in a stardom status. Some rate Linux as the best ever written UNIX-clone that would spell disaster for UNIX and other UNIX-clones and UNIX-compatibles out there in the market. But in reality it is not so. Readers must note: Just as the power of an automobile comes from the quality of the engine running under it's hood, similarly features like stability, reliability, extensibility and robustness of an operating system software comes from the internal structure of the Kernel or the core of that corresponding operating system. I personally feel that both the Linux and the FreeBSD Kernel are great works of creativity and tremendous effort and just a user-level or technical comparison between the two is meaningless. Situations where memory is a scarcity and moreover gets crunched and stressed upon real hard, the Linux Kernel breaks down. FreeBSD with it's highly optimized and advanced VM/Swap system comes to the rescue! On the other hand, under given situations, Linux may outperform FreeBSD by a mile. The significant point for readers to note and remember is that the Linux Kernel favors simplicity over highly optimized and dynamic yet more complex code whereas the FreeBSD Kernel optimizes performance by introducing more complex code and heavily optimizing the code base by rearranging and rewriting some of the more important internal algorithms and data structures from time to time.</para>
<para>
A complete and exhaustive discussion on Linux and FreeBSD Kernels is beyond the scope of this guide. If readers find it interesting, they may search the Internet for more Linux and/or FreeBSD specific information. I would suggest the readers to read "Understanding the Linux Kernel" by Bovet and Cesati for getting more in-depth information on the inner-workings of the Linux Kernel, "The Design and Implementation of the 4.4BSD Operating System" for FreeBSD/OpenBSD and so on, and "The Design of the UNIX Operating System" by M. Bach for UNIX SVR4 internals.</para>
A complete and exhaustive discussion on Linux and FreeBSD Kernels is
beyond the scope of this guide. If readers find it interesting, they
may search the Internet for more Linux and/or FreeBSD specific
information. I would suggest the readers to read <quote>Understanding
the Linux Kernel</quote> by Bovet and Cesati for getting more in-depth information on the inner-workings of the Linux Kernel, <quote>The Design and Implementation of the 4.4BSD Operating System</quote> for FreeBSD/OpenBSD and so on, and <quote>The Design of the UNIX Operating System</quote> by M. Bach for UNIX SVR4 internals.</para>
</section>
<section>
<title>
OpenBSD</title>
<para>
The BSD family, other than the dominant big-brother FreeBSD, also consists of OpenBSD, NetBSD, BSD/OS and Darwin operating systems. OpenBSD is a fully functional, multi-platform UNIX-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. The OpenBSD team strives to achieve what is called "a secure by default" status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This "secure by default" goal is achieved by taking a proactive stance on security. FreeBSD -RELEASES target stability and reliability under the most adverse of conditions whereas OpenBSD -RELEASES target optimum security in corporate environments. The OpenBSD operating system software has been labeled "the proactively secure Unix-like operating system". The OpenBSD Kernel is heavily optimized with security features thereby providing customers with utmost secure and hack-resilient real-time systems. The OpenBSD Project web-site can be accessed at: http://www.openbsd.org.</para>
The BSD family, other than the dominant big-brother FreeBSD, also
consists of OpenBSD, NetBSD, BSD/OS and Darwin operating
systems. OpenBSD is a fully functional, multi-platform UNIX-like
Operating System based on Berkeley Networking Release 2 (Net/2) and
4.4BSD-Lite. The OpenBSD team strives to achieve what is called
<quote>a secure by default</quote> status. This means that an OpenBSD
user should feel safe that their newly installed machine will not be
compromised. This <quote>secure by default</quote> goal is achieved by taking a proactive stance on security. FreeBSD -RELEASES target stability and reliability under the most adverse of conditions whereas OpenBSD -RELEASES target optimum security in corporate environments. The OpenBSD operating system software has been labeled <quote>the proactively secure Unix-like operating system.</quote> The OpenBSD Kernel is heavily optimized with security features thereby providing customers with utmost secure and hack-resilient real-time systems. The OpenBSD Project web-site can be accessed at: http://www.openbsd.org.</para>
<para>
The OpenBSD operating system software has integrated strong cryptography into the base system. A fully functional IPsec (Internet Protocol Security) implementation is provided as well as support for common protocols such as SSL (Secure Sockets Layer) and SSH (Secure Shell). Network filtering and monitoring tools such as packet filtering, NAT (Network Address Translation), and bridging are also included. For high performance demands, support for hardware cryptography has also been added to the base system. OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it.</para>
</section>
<section>
<title>
NetBSD</title>
<para> The NetBSD kernel focuses on clean design and well architected solutions. NetBSD supports a massive range of hardware platforms from a single source tree, including simultaneous release across all platforms, and continues to attract users and experienced developers despite lack of media exposure and commercial backing - all thanks to attention to code quality. The NetBSD operating system kernel targets "portability" and tries to run on as many platforms as possible. The NetBSD Project web-site can be accessed at: http://www.netbsd.org</para>
<para> The NetBSD kernel focuses on clean design and well architected solutions. NetBSD supports a massive range of hardware platforms from a single source tree, including simultaneous release across all platforms, and continues to attract users and experienced developers despite lack of media exposure and commercial backing - all thanks to attention to code quality. The NetBSD operating system kernel targets <emphasis>portability</emphasis> and tries to run on as many platforms as possible. The NetBSD Project web-site can be accessed at: http://www.netbsd.org</para>
</section>
<section>
<title>Addtional reading for *BSD's</title>
@ -444,7 +470,7 @@ For a comparative study between FreeBSD, Linux and Microsoft Windows 2000, check
<section>
<title>Target Audience</title>
<para>
The following table exhibits the main "target" of every operating system covered in this guide:</para>
The following table exhibits the main target of every operating system covered in this guide:</para>
<para>
Windows: Ask Mr. Gates himself... Difficult to guess!</para>
<para>
@ -463,7 +489,7 @@ NetBSD NetBSD targets portability. To run on as many platforms as possible is i
Installing Microsoft Windows</title>
<section>
<title></title>
<para>I have used a Microsoft Windows operating system as the "first" operating system on my computer. I have MS Windows 98 (SE) installed on my computer. The reader may choose any one of the Microsoft operating systems mentioned below in the listed form. Suppose, you would like to use Microsoft Windows 98 (SE) as your first operating system too. Then read the information given in Section B: Installing MS Windows 98 (SE) and after doing likewise as mentioned in that section, proceed forward with installing FreeBSD 5.1-RELEASE or OpenBSD 3.2-RELEASE or NetBSD 1.6.1.</para>
<para>I have used a Microsoft Windows operating system as the first operating system on my computer. I have MS Windows 98 (SE) installed on my computer. The reader may choose any one of the Microsoft operating systems mentioned below in the listed form. Suppose, you would like to use Microsoft Windows 98 (SE) as your first operating system too. Then read the information given in Section B: Installing MS Windows 98 (SE) and after doing likewise as mentioned in that section, proceed forward with installing FreeBSD 5.1-RELEASE or OpenBSD 3.2-RELEASE or NetBSD 1.6.1.</para>
<para>
Thus, we have the following sections:</para>
<itemizedlist>
@ -511,7 +537,7 @@ The material mentioned below applies to Microsoft Windows 95, Microsoft Windows
<para>
Before you install your operating system, you must first create a primary partition on the hard disk (disk 1) on your computer, and then format a filesystem on that partition. The Fdisk tool is an MS-DOS-based tool that you can use to prepare (partition) a hard disk. You can use the Fdisk tool to create, change, delete, or display current partitions on the hard disk, and then each allocated space on the hard disk (primary partition, extended partition, or logical drive) is assigned a drive letter. Disk 1 may contain one extended partition, and a second hard disk may contain a primary or extended partition. An extended partition may contain one or more logical MS-DOS drives.</para>
<para>
After you have used the Fdisk tool to partition the hard disk, you can use the Format tool to format those partitions with a filesystem. The filesystem File Allocation Table (FAT) allows the hard disk to accept, store and retrieve data. Windows 95, Windows 98 (SE), Windows Millennium (ME) and Windows 2000 support the FAT16 and FAT32 filesystems. When you run the Fdisk tool on a hard disk that is larger than 512 megabytes (MB), you are prompted to choose one of the following file systems: FAT16 or FAT32. The FAT16 filesystem has a maximum of 2 gigabytes (GB) for each allocated space or drive letter. For example, if you use the FAT16 filesystem and have a 6-GB hard disk, you can have three drive letters (C, D, and E), each with 2 GB of allocated space. As for the FAT32 filesystem, it supports drives that are up to 2 terabytes in size and stores files on smaller sections of the hard disk than the FAT16 filesystem does. This results in more free space on the hard disk. Please note that the FAT32 filesystem does not support drives that are smaller than 512 MB. When you run the "fdisk" and "format" commands, the Master Boot Record (MBR) and file allocation tables are created. The MBR and file allocation tables store the necessary disk geometry that allows hard disk to accept, store, and retrieve data.</para>
After you have used the Fdisk tool to partition the hard disk, you can use the Format tool to format those partitions with a filesystem. The filesystem File Allocation Table (FAT) allows the hard disk to accept, store and retrieve data. Windows 95, Windows 98 (SE), Windows Millennium (ME) and Windows 2000 support the FAT16 and FAT32 filesystems. When you run the Fdisk tool on a hard disk that is larger than 512 megabytes (MB), you are prompted to choose one of the following file systems: FAT16 or FAT32. The FAT16 filesystem has a maximum of 2 gigabytes (GB) for each allocated space or drive letter. For example, if you use the FAT16 filesystem and have a 6-GB hard disk, you can have three drive letters (C, D, and E), each with 2 GB of allocated space. As for the FAT32 filesystem, it supports drives that are up to 2 terabytes in size and stores files on smaller sections of the hard disk than the FAT16 filesystem does. This results in more free space on the hard disk. Please note that the FAT32 filesystem does not support drives that are smaller than 512 MB. When you run the <application>fdisk</application> and <application>format</application> commands, the Master Boot Record (MBR) and file allocation tables are created. The MBR and file allocation tables store the necessary disk geometry that allows hard disk to accept, store, and retrieve data.</para>
<para>
Please note that I have assumed that you own a computer system which can run without glitches and that you have access to a bootable Microsoft Windows CD-ROM. If you do run into problems booting from the CD-ROM or using Start-up disks, please consult your hardware manufacturer to obtain the CD-ROM device driver(s). For partitioning a master hard disk, you have to run the fdisk command. First insert the Startup disk in the floppy disk drive, restart your computer, and then use one of the following methods, depending on your operating system.</para>
<section>
@ -558,10 +584,19 @@ If you want to customize the size of the partitions (drive letters) on the hard
</section>
<section>
<title>Format Partition</title>
<para>After you create the partitions, you must format the partitions for accessing and using them. If you are using a Windows 95 Startup disk, a command prompt is displayed and you can skip to step 2. If you are using a Windows 98 Second Edition or a Windows ME Startup disk, select the Start computer without CD-ROM support menu option when the Windows 98 Startup menu is displayed. When a command prompt is displayed, type "format c:", and then press enter This command formats drive C (or your "active" drive). For all other partitions, type format drive: (where drive is the letter of the partition that you want to format).</para>
<para>After you create the partitions, you must format the
partitions for accessing and using them. If you are using a
Windows 95 Startup disk, a command prompt is displayed and you
can skip to step 2. If you are using a Windows 98 Second
Edition or a Windows ME Startup disk, select the Start
computer without CD-ROM support menu option when the Windows
98 Startup menu is displayed. When a command prompt is
displayed, type
<screen>format c:"</screen>
, and then press enter This command formats drive C (or your <emphasis>active</emphasis> drive). For all other partitions, type format drive: (where drive is the letter of the partition that you want to format).</para>
<warning>
<para>
Readers must note that I speak about "partitioning a hard disk" using Microsoft fdisk utility in general here in this section in order to provide the absolute newbies with general information on how to partition and format a new hard disk drive.</para>
Readers must note that I speak about <emphasis>partitioning a hard disk</emphasis> using Microsoft fdisk utility in general here in this section in order to provide the absolute newbies with general information on how to partition and format a new hard disk drive.</para>
</warning>
</section>
</section>
@ -582,8 +617,9 @@ During a new installation of Windows NT, 2000 or XP, you may have to choose whic
<para>
NTFS: The NT file system (NTFS) is used with the Windows NT, Windows 2000, and Windows XP operating systems. NTFS provides enhanced reliability, stability, and security, and supports large hard disks of up to 2 terabytes (TB).</para>
<para>
But very "important" information: The conversion to NTFS is one-way only; if you convert your FAT or FAT32 file system to NTFS you cannot convert your hard disk back to FAT later.</para>
<warning>
<para>But very "important" information: The conversion to NTFS is one-way only; if you convert your FAT or FAT32 file system to NTFS you cannot convert your hard disk back to FAT later.</para>
</warning>
<para>
If you are not sure which file system to use, I would suggest using FAT32. If you want to change your file system, here are a few recommendations:</para>
<itemizedlist>
@ -615,8 +651,8 @@ After creating this Primary Partition (suppose say, of 999MB), we do not (I repe
<para>
Thus, before we finally move on to the next section where we install
and configure FreeBSD 5.1-RELEASE or OpenBSD 3.2-RELEASE or NetBSD
1.6.1, I would like to round-off this chapter with a "Partition
check". I have the following partition table on my computer after this
1.6.1, I would like to round-off this chapter with a Partition
check. I have the following partition table on my computer after this
step (as observed from Microsoft fdisk):</para>
<screen>
Display Partition Information Partition
@ -630,17 +666,27 @@ C:1 A PRI DOS WIN 1000 FAT32 5%
<chapter>
<title>
Installing FreeBSD 5.1-RELEASE</title>
<para>This Chapter focuses on installing FreeBSD 5.1-RELEASE and multi-booting the system so that it can coexist successfully with the already existing Windows operating system on the computer. Like the Windows installation, it too focuses on a CD-ROM based installation. Experts may proceed as usual without help, as for the newbies out there, make sure you check out the Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X at the "The FreeBSD Documentation Project" at http://www.freebsd.org. For a step-by-step FreeBSD Installation procedure with screenshots, please refer to Chapter2 : Installing FreeBSD of the FreeBSD Handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html. These and other documentation available on the FreeBSD Project homepage provides exhaustive and extensive coverage of all aspects related to the FreeBSD software. Make sure you grab as much information as you can from this site before proceeding with this guide.</para>
<para>This Chapter focuses on installing FreeBSD 5.1-RELEASE and multi-booting the system so that it can coexist successfully with the already existing Windows operating system on the computer. Like the Windows installation, it too focuses on a CD-ROM based installation. Experts may proceed as usual without help, as for the newbies out there, make sure you check out the Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X at the The FreeBSD Documentation Project at http://www.freebsd.org. For a step-by-step FreeBSD Installation procedure with screenshots, please refer to Chapter2 : Installing FreeBSD of the FreeBSD Handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html. These and other documentation available on the FreeBSD Project homepage provides exhaustive and extensive coverage of all aspects related to the FreeBSD software. Make sure you grab as much information as you can from this site before proceeding with this guide.</para>
<para>Readers must note that at the time of writing, 2 parallel branches of the FreeBSD operating system exist. The latest -STABLE release is the FreeBSD 4.9-RELEASE while the latest -CURRENT release is the FreeBSD 5.1-RELEASE. In this Chapter, we would discuss some theoretical aspects of installing FreeBSD 5.1-RELEASE, disk partitioning (better known as slicing in FreeBSD terminology) and then move on to the actual installation itself.
</para>
<section>
<title>Slicing in FreeBSD</title>
<para>
Before installing FreeBSD, it would be a good idea to take a brief tour of what FreeBSD calls "slicing". If you already know this stuff, feel free to skip this part and read the section entitled "Summary of Installation Steps".</para>
<para>The FreeBSD operating system partitions (a hard disk) and labels partitions according to a particular chosen scheme which is similar to other BSD-based UNIX systems such as NetBSD, OpenBSD, Ultrix, Digital Unix and SunOS. Let us see how the FreeBSD software "slices" your hard disk and then "creates partitions in it" for use. Each partition-that-contains-a-filesystem is stored in what FreeBSD calls a "slice". Slice is FreeBSD's term for what were earlier called partitions. Slices are numbered, starting at 1, through to 4 (In Windows terminology, they would be called "primary partitions", starting at 1, through to 4). Thus, the reader must note that "a primary partition" in Windows refers to a "slice" in FreeBSD terminology, and "an extended partition containing logical disk drives in it" is simply called as "partitions" in FreeBSD. A logical disk drive within an extended partition may also be called as "a logical slice inside a physical slice" in FreeBSD. It may appear a bit awkward at times, but the sooner the reader gets used to these terms, the better!</para>
Before installing FreeBSD, it would be a good idea to take a brief tour of what FreeBSD calls <quote>slicing.</quote> If you already know this stuff, feel free to skip this part and read the section entitled <quote>Summary of Installation Steps.</quote></para>
<para>The FreeBSD operating system partitions (a hard disk) and
labels partitions according to a particular chosen scheme which
is similar to other BSD-based UNIX systems such as NetBSD,
OpenBSD, Ultrix, Digital Unix and SunOS. Let us see how the
FreeBSD software slices your hard disk and then creates
partitions in it for use. Each
partition-that-contains-a-filesystem is stored in what FreeBSD
calls a <emphasis>slice.</emphasis> Slice is FreeBSD's term for what were earlier called partitions. Slices are numbered, starting at 1, through to 4 (In Windows terminology, they would be called <emphasis>primary partitions</emphasis>, starting at 1, through to 4). Thus, the reader must note that <emphasis>a primary partition</emphasis> in Windows refers to a <emphasis>slice</emphasis> in FreeBSD terminology, and <emphasis>an extended partition containing logical disk drives in it</emphasis> is simply called as <emphasis>partitions</emphasis> in FreeBSD. A logical disk drive within an extended partition may also be called as <emphasis>a logical slice inside a physical slice</emphasis> in FreeBSD. It may appear a bit awkward at times, but the sooner the reader gets used to these terms, the better!</para>
<para>
Now, the important part. There exists a few operating systems which can boot even if their corresponding boot files are stored within a logical disk drive of an extended partition. For FreeBSD, this mechanism does "not" work. FreeBSD necessarily needs one of the slices (that is the 4 entries in the partition table on your computer's hard drive, which in Windows terminology would be called as a "primary partition"). It then uses a program called "disklabel" for making upto eight partitions in this slice. Readers must note a very significant fact: You "cannot" install FreeBSD in an extended partition made by Linux (or DOS).</para>
Now, the important part. There exists a few operating systems which can boot even if their corresponding boot files are stored within a logical disk drive of an extended partition. For FreeBSD, this mechanism does not work. FreeBSD necessarily needs one of the slices (that is the 4 entries in the partition table on your computer's hard drive, which in Windows terminology would be called as a <emphasis>primary partition</emphasis>). It then uses a program called <application>disklabel</application> for making upto eight partitions in this slice. <warning>
<para>
Readers must note a very significant fact: You "cannot" install FreeBSD in an extended partition made by Linux (or DOS).</para>
</warning>
<para>
FreeBSD labels hard disks and partitions as follows:
<itemizedlist>
@ -657,7 +703,7 @@ FreeBSD labels hard disks and partitions as follows:
<para>Fourth IDE hard disk (Secondary Slave) - /dev/ad3</para>
</listitem>
</itemizedlist>
where, /dev is the directory under the root ("/") directory in FreeBSD which contains all the device special files associated with devices. I assume readers are using a FreeBSD 4.X-RELEASE or later. IDE hard disks are named as wd* before FreeBSD 4.0-RELEASE.</para>
where, /dev is the directory under the root (/) directory in FreeBSD which contains all the device special files associated with devices. I assume readers are using a FreeBSD 4.X-RELEASE or later. IDE hard disks are named as wd* before FreeBSD 4.0-RELEASE.</para>
<para>
What about SCSI drives? Well, FreeBSD labels that too!
@ -677,7 +723,7 @@ Third SCSI hard disk (Secondary Master) - /dev/da2</para>
<para>Fourth SCSI hard disk (Secondary Slave) - /dev/da3</para>
</listitem>
</itemizedlist>
where, /dev is the directory under the root ("/") directory in FreeBSD which contains all the device files associated with devices.</para>
where, /dev is the directory under the root (/) directory in FreeBSD which contains all the device files associated with devices.</para>
<para>
Now, let us talk about the partitioning scheme under FreeBSD. It is just like in Linux, only the way the partitions are named is different. In FreeBSD, we first consider a particular hard disk, whether IDE or SCSI. Then, we consider the partitions on it. For example, the partitions on an IDE drive are named in the following way (/dev/ad0 is used as an example):<itemizedlist>
<listitem>
@ -724,7 +770,7 @@ Second primary partition - /dev/ad0s2</para>
</itemizedlist>
</listitem>
</itemizedlist>
where, ad0s2a refers to the "first partition (a) on the second slice (s2) on the first IDE disk (ad0)". In the above example, /dev/ad0s1 is the slice containing FAT32 filesystem and /dev/ad0s2 is the second slice on the hard disk drive under scrutiny. Readers must note that FreeBSD labels slices from /dev/ad0s1 onwards to /dev/ad0s4, with a maximum of 8 possible logical slices named as a, b, c, d, e, f, g and h. In this example, the "logical slices" a, b, e and f have their corresponding mount points in FreeBSD.</para>
where, ad0s2a refers to the first partition (a) on the second slice (s2) on the first IDE disk (ad0). In the above example, /dev/ad0s1 is the slice containing FAT32 filesystem and /dev/ad0s2 is the second slice on the hard disk drive under scrutiny. Readers must note that FreeBSD labels slices from /dev/ad0s1 onwards to /dev/ad0s4, with a maximum of 8 possible logical slices named as a, b, c, d, e, f, g and h. In this example, the logical slices a, b, e and f have their corresponding mount points in FreeBSD.</para>
<para>
Here, the mount points are as follows:<itemizedlist>
<listitem>
@ -740,21 +786,21 @@ Here, the mount points are as follows:<itemizedlist>
<para>f = /usr</para>
</listitem>
</itemizedlist>
For more exhaustive information, please refer to the "FreeBSD Handbook".</para>
For more exhaustive information, please refer to the FreeBSD Handbook.</para>
</section>
<section>
<title>Filesystems in FreeBSD</title>
<para>
Microsoft Windows operating systems use FAT16, FAT32, NTFS 4.0 and NTFS 5.0 filesystems for storing and retrieving data. The recently released NTFS 5.0 is implemented in all of the Windows 2000 operating systems. The Linux Kernel uses the "Third Extended native filesystem", denoted as ext3fs. Linux also supported the ext (now obsolete and no longer supported) and ext2 filesystems. The "Second Extended filesystem" (ext2fs) is an advanced hierarchical filesystem developed for the Linux operating system, which included advanced features like a maximum file size of 2.0 GB, a maximum file name length of 255 characters and support for three time/date stamps. They are the date of creation, date of last modification and date of last access. The "Third Extended filesystem" has all these features, and additionally it implements IBM's "journaled file system architecture" (JFS) functionality. The JFS architecture ensures the integrity of data stored on a hard disk in the event of an unplanned shutdown, such as one caused by a power outage. A journaled filesystem maintains a log of all read and write events; this log enables the disk to be restored to its last stable state and additionally allows incompletely written data to be restored to the maximum possible extent.</para>
Microsoft Windows operating systems use FAT16, FAT32, NTFS 4.0 and NTFS 5.0 filesystems for storing and retrieving data. The recently released NTFS 5.0 is implemented in all of the Windows 2000 operating systems. The Linux Kernel uses the Third Extended native filesystem, denoted as ext3fs. Linux also supported the ext (now obsolete and no longer supported) and ext2 filesystems. The Second Extended filesystem (ext2fs) is an advanced hierarchical filesystem developed for the Linux operating system, which included advanced features like a maximum file size of 2.0 GB, a maximum file name length of 255 characters and support for three time/date stamps. They are the date of creation, date of last modification and date of last access. The Third Extended filesystem has all these features, and additionally it implements IBM's journaled file system architecture (JFS) functionality. The JFS architecture ensures the integrity of data stored on a hard disk in the event of an unplanned shutdown, such as one caused by a power outage. A journaled filesystem maintains a log of all read and write events; this log enables the disk to be restored to its last stable state and additionally allows incompletely written data to be restored to the maximum possible extent.</para>
<para>
The FreeBSD operating system basically uses the UNIX File System (UFS) architecture for its underlying filesystem. The University of Berkeley made more advancements to it referred to as the "Berkeley Improvements" or "Berkeley Extensions". This filesystem, currently used by FreeBSD as its native filesystem is often called the "Fast Filesystem" or FFS, because access reads and writes to data stored in FFS is very fast. The architecture is a little more complex than Linux's ext2fs. It offers a better way to insure filesystem data integrity, mainly with the "softupdates" option. This option decreases synchronous I/O and increases asynchronous I/O because writes to a UFS filesystem are not synced on a sector basis but according to the filesystem structure. This ensures that the filesystem is always coherent between two updates.</para>
The FreeBSD operating system basically uses the UNIX File System (UFS) architecture for its underlying filesystem. The University of Berkeley made more advancements to it referred to as the Berkeley Improvements or Berkeley Extensions. This filesystem, currently used by FreeBSD as its native filesystem is often called the <emphasis>Fast Filesystem</emphasis> or FFS, because access reads and writes to data stored in FFS is very fast. The architecture is a little more complex than Linux's ext2fs. It offers a better way to insure filesystem data integrity, mainly with the softupdates option. This option decreases synchronous I/O and increases asynchronous I/O because writes to a UFS filesystem are not synced on a sector basis but according to the filesystem structure. This ensures that the filesystem is always coherent between two updates.</para>
<para>
The FreeBSD filesystem also supports file flags, which can stop a would-be intruder dead in his or her tracks. There are several flags that you can add to a file such as the immutable flag. The immutable (schg) flag would not allow any alteration to the file or directory unless you remove it. Other available flags are append only (sappnd), cannot delete (sunlnk), and archive (arch). When you combine these with the kernel security level option, you have a very impenetrable system. In short, the FreeBSD Kernel uses UFS = UFS+FFS+Softupdates+dirpref+dirhash functionality for storing and retrieving data on disks. </para>
</section>
<section>
<title>Summary of Installation Steps</title>
<para>
The partitioning scheme and filesystems covered in FreeBSD, its time for us to move on to the actual FreeBSD installation. For a complete step-by-step coverage of FreeBSD installation, please consult the installation guide available on the FreeBSD Project web site. As in the previous Chapter, here also, I would be mentioning only the significant steps for the installation. Use these steps to install FreeBSD on your computer and configure it for "multi-booting":<orderedlist>
The partitioning scheme and filesystems covered in FreeBSD, its time for us to move on to the actual FreeBSD installation. For a complete step-by-step coverage of FreeBSD installation, please consult the installation guide available on the FreeBSD Project web site. As in the previous Chapter, here also, I would be mentioning only the significant steps for the installation. Use these steps to install FreeBSD on your computer and configure it for multi-booting:<orderedlist>
<listitem>
<para>We have a computer running a Microsoft Windows operating system. On my PC, it is Windows 98 (SE). I put a bootable FreeBSD 5.1-RELEASE CD-ROM in the CD-ROM drive and reboot the system.</para>
</listitem>
@ -775,25 +821,29 @@ Select the unused space and create 2 approximately equal partitions. Thus, 2 sli
The next screen allows you to install a boot manager. Since Microsoft Windows 98 (SE) overwrites the Master Boot Record (MBR) rendering any other operating system unbootable, you should choose to install the FreeBSD boot manager in the MBR of your hard disk. I have installed FreeBSD alongside another operating system on the same hard disk, and I want FreeBSD to boot the other operating system when I start the computer. That is the reason, I installed the FreeBSD boot manager into the MBR. Once done, we enter the Sysinstall Disklabel Editor.</para>
</listitem>
<listitem>
<para>The Sysinstall Disklabel Editor represents the already existing Windows FAT32 partition. Readers must note that FreeBSD names this partition as a FreeBSD slice but without an appropriate "mount point". Here, I would create the logical partitions for the FreeBSD slice (which is /dev/ad0s2).</para>
<para>The Sysinstall Disklabel Editor represents the already existing Windows FAT32 partition. Readers must note that FreeBSD names this partition as a FreeBSD slice but without an appropriate mount point. Here, I would create the logical partitions for the FreeBSD slice (which is /dev/ad0s2).</para>
</listitem>
<listitem>
<para>On my PC, the Windows FAT32 partition is named /dev/ad0s1 (C: in DOS). In other words, it is the first slice on the IDE hard disk of my computer. Disklabel can automatically create partitions for you and assign them default sizes if you press the key A. Depending on the size of the disk (and purpose of installing FreeBSD), the defaults may or may not be appropriate. For me, it works most of the time! To quote from the FreeBSD Handbook, "...Beginning with FreeBSD 4.5, the default partitioning assigns the /tmp directory its own partition instead of being part of the / partition. This helps avoid filling the / partition with temporary files...". This is an important consideration if you have a lot of temporary files to deal with. I create a /, swap, /usr, /var and other usual partitions in my FreeBSD slice (named as /dev/ad0s2).</para>
<para>On my PC, the Windows FAT32 partition is named /dev/ad0s1 (C: in DOS). In other words, it is the first slice on the IDE hard disk of my computer. Disklabel can automatically create partitions for you and assign them default sizes if you press the key A. Depending on the size of the disk (and purpose of installing FreeBSD), the defaults may or may not be appropriate. For me, it works most of the time! To quote from the FreeBSD Handbook, <blockquote>
<para>
...Beginning with FreeBSD 4.5, the default partitioning assigns the /tmp directory its own partition instead of being part of the / partition. This helps avoid filling the / partition with temporary files...".</para>
</blockquote>
This is an important consideration if you have a lot of temporary files to deal with. I create a /, swap, /usr, /var and other usual partitions in my FreeBSD slice (named as /dev/ad0s2).</para>
</listitem>
<listitem>
<para>Once the slices created and partitions within the FreeBSD slice set and done, we proceed to choose what to install on the system. Depending on the intended use and resources at your disposal, you must make the correct choice of what to install and what not to install. For example, Mr. A wants to check out FreeBSD 5.1-RELEASE for fun! Well, a "Minimal Install" is the best choice for him. It saves him both time and hard disk space. His brother, Mr. B is a hot-shot Kernel Developer. He wants access to documentation, full system binaries and the Kernel source code. He would go in for a "Kern-Developer" canned distribution set. And if you have enough resources at your disposal or if it so happens you do not want to use the pkg_add tool to install packages later or from the ports collection manually, well, as it so happens, you can always go in for the "All" install option. This would install everything on the system. Thus, we see that the predefined options range from installing the smallest possible configuration (Minimal) to everything (All). Those who are new to UNIX and/or FreeBSD should almost certainly select one of these canned options. Readers must note: If a graphical user interface (GUI) is desired then a distribution set that is preceded by an X should be chosen. The configuration of XFree86 and selection of a default desktop is part of the post-installation steps.</para>
<para>Once the slices created and partitions within the FreeBSD slice set and done, we proceed to choose what to install on the system. Depending on the intended use and resources at your disposal, you must make the correct choice of what to install and what not to install. For example, Mr. A wants to check out FreeBSD 5.1-RELEASE for fun! Well, a Minimal Install is the best choice for him. It saves him both time and hard disk space. His brother, Mr. B is a hot-shot Kernel Developer. He wants access to documentation, full system binaries and the Kernel source code. He would go in for a Kern-Developer canned distribution set. And if you have enough resources at your disposal or if it so happens you do not want to use the pkg_add tool to install packages later or from the ports collection manually, well, as it so happens, you can always go in for the <emphasis>All</emphasis> install option. This would install everything on the system. Thus, we see that the predefined options range from installing the smallest possible configuration (Minimal) to everything (All). Those who are new to UNIX and/or FreeBSD should almost certainly select one of these canned options. Readers must note: If a graphical user interface (GUI) is desired then a distribution set that is preceded by an X should be chosen. The configuration of XFree86 and selection of a default desktop is part of the post-installation steps.</para>
</listitem>
<listitem>
<para>Next, choose the installation media from the list of available choices. I guess you are doing a Local CD/DVD-ROM installation just like me! Using the arrow keys highlight "Install from a FreeBSD CD/DVD", and press Enter to proceed with the installation. If it so happens that you want to undertake a different kind of installation, choose the appropriate option and follow the steps.</para>
<para>Next, choose the installation media from the list of available choices. I guess you are doing a Local CD/DVD-ROM installation just like me! Using the arrow keys highlight <emphasis>Install from a FreeBSD CD/DVD</emphasis>, and press Enter to proceed with the installation. If it so happens that you want to undertake a different kind of installation, choose the appropriate option and follow the steps.</para>
</listitem>
<listitem>
<para>Next appears the "Committing to the Installation" screen. You would be asked whether you are sure of installing FreeBSD on this system or not. Select [ Yes ] and press enter to proceed. The installation can now proceed if desired. Readers must note: This is absolutely the last chance for aborting the installation to prevent changes to the hard disk.</para>
<para>Next appears the <emphasis>Committing to the Installation</emphasis> screen. You would be asked whether you are sure of installing FreeBSD on this system or not. Select [ Yes ] and press enter to proceed. The installation can now proceed if desired. Readers must note: This is absolutely the last chance for aborting the installation to prevent changes to the hard disk.</para>
</listitem>
<listitem>
<para>The installation time will vary according to the distribution chosen, installation media used, and the speed of the computer. There will be a series of messages displayed indicating the status. The installation is complete when the following message is displayed: "Congratulations! You now have FreeBSD installed on your system....".</para>
<para>The installation time will vary according to the distribution chosen, installation media used, and the speed of the computer. There will be a series of messages displayed indicating the status. The installation is complete when the following message is displayed: <screen>Congratulations! You now have FreeBSD installed on your system....".</screen></para>
</listitem>
<listitem>
<para>Next comes the post-installation steps. It usually involves chores as "Network Device Configuration", "Configure Gateway", "Configure Internet Services", "Anonymous FTP", "NFS Server", "NFS Client", setting up a "Security Profile", "System Console Settings", "Setting The Time Zone", "Adding Users and Groups" and so on. For an exhaustive covering of each and every step along with helpful screenshots, please refer to the FreeBSD Handbook at http://www.freebsd.org.</para>
<para>Next comes the post-installation steps. It usually involves chores as Network Device Configuration, Configure Gateway, Configure Internet Services, Anonymous FTP, NFS Server, NFS Client, setting up a Security Profile, System Console Settings, Setting The Time Zone, Adding Users and Groups and so on. For an exhaustive covering of each and every step along with helpful screenshots, please refer to the FreeBSD Handbook at http://www.freebsd.org.</para>
</listitem>
<listitem>
<para>Once you have completed the post-installation steps, exit the /stand/sysinstall system installer utility, take out the CD-ROM, and reboot the system. When your computer reboots, since you have installed the FreeBSD boot loader into the MBR of your hard disk, you would normally get a following prompt on your screen. It displays something like: F1 DOS, F2 FreeBSD, F3 Linux; each one in a separate line. The Default: F1 is also shown. FreeBSD uses a 3-stage bootstrap by default, and this is actually the preceding bootblock, named /boot/boot0, which lives on the MBR, the special part of the disk that the system bootstrap looks for and runs, and it simply shows a list of possible slices to boot from.</para>
@ -802,7 +852,7 @@ The next screen allows you to install a boot manager. Since Microsoft Windows 98
<para>Press F1 to boot into Microsoft Windows. On my computer, I successfully booted into Windows 98 (SE). So far so good! I rebooted and pressed F2 this time, and I successfully booted into FreeBSD as well. Bingo! You already have a dual-boot system which uses the FreeBSD boot loader to boot 2 operating systems.</para>
</listitem>
<listitem>
<para>Depending on the configuration of your computer, you will receive bootup messages on your screen when you boot into FreeBSD for the first time. Though the messages scroll off the screen rather fast for you to read anything productive, you can always read it later by using the "/sbin/dmesg | more" command. Finally, you will arrive at the login prompt. Login using the username/password you set during installation. Readers must note: The Linux slice is not ready yet, cause we have not defined the mount points of the root (/) directory and swap filesystem as well. So, for doing this and more, we proceed to the chapter, Chapter 6: Installing Red Hat Linux 8.0 (Psyche). Readers must note that if you have already installed FreeBSD, you can skip the next 2 chapters and proceed with the Linux installation directly.</para>
<para>Depending on the configuration of your computer, you will receive bootup messages on your screen when you boot into FreeBSD for the first time. Though the messages scroll off the screen rather fast for you to read anything productive, you can always read it later by using the <screen>/sbin/dmesg | more</screen> command. Finally, you will arrive at the login prompt. Login using the username/password you set during installation. Readers must note: The Linux slice is not ready yet, cause we have not defined the mount points of the root (/) directory and swap filesystem as well. So, for doing this and more, we proceed to the chapter, Chapter 6: Installing Red Hat Linux 8.0 (Psyche). Readers must note that if you have already installed FreeBSD, you can skip the next 2 chapters and proceed with the Linux installation directly.</para>
</listitem>
</orderedlist></para>
</section>
@ -811,32 +861,39 @@ The next screen allows you to install a boot manager. Since Microsoft Windows 98
<title>
Installing OpenBSD 3.2-RELEASE</title>
<para>
This Chapter focuses on installing OpenBSD 3.2-RELEASE and multi-booting the system so that it can coexist successfully with the already existing Windows operating system on the computer. Like the Windows and FreeBSD installation, it too focuses on a CD-ROM based installation. Experts may proceed as usual without help, as for the newbies out there, make sure you check out the Frequently Asked Questions for OpenBSD on the "The OpenBSD Project homepage" at http://www.openbsd.org. For a step-by-step OpenBSD Installation procedure with screenshots, please refer to the "Installing OpenBSD" Online manual at the OpenBSD Project homepage. These and other documentation available on the OpenBSD 3.2-RELEASE CD-ROM provides exhaustive and extensive coverage of all aspects related to OpenBSD. Make sure you grab as much information as you can before proceeding with this guide.</para>
This Chapter focuses on installing OpenBSD 3.2-RELEASE and multi-booting the system so that it can coexist successfully with the already existing Windows operating system on the computer. Like the Windows and FreeBSD installation, it too focuses on a CD-ROM based installation. Experts may proceed as usual without help, as for the newbies out there, make sure you check out the Frequently Asked Questions for OpenBSD on the The OpenBSD Project homepage at http://www.openbsd.org. For a step-by-step OpenBSD Installation procedure with screenshots, please refer to the <quote>Installing OpenBSD</quote> Online manual at the OpenBSD Project homepage. These and other documentation available on the OpenBSD 3.2-RELEASE CD-ROM provides exhaustive and extensive coverage of all aspects related to OpenBSD. Make sure you grab as much information as you can before proceeding with this guide.</para>
<para>
Since both FreeBSD and OpenBSD operating systems are BSD-derivatives, UNIX-related information present in the /usr/share/doc directory on both systems provide very high-quality technical information on how to install, use and customize a UNIX-system. If you are not yet a FreeBSD/OpenBSD wizard, my humble and honest advice would be to read the "Unix User's Supplementary Documents (USD)", "Unix System Manager's Manual (SMM)" and the "Unix Programmer's Supplementary Documents (PSD)" on these systems.</para>
Since both FreeBSD and OpenBSD operating systems are BSD-derivatives, UNIX-related information present in the /usr/share/doc directory on both systems provide very high-quality technical information on how to install, use and customize a UNIX-system. If you are not yet a FreeBSD/OpenBSD wizard, my humble and honest advice would be to read the Unix User's Supplementary Documents (USD), Unix System Manager's Manual (SMM) and the Unix Programmer's Supplementary Documents (PSD) on these systems.</para>
<para>
Note: I assume, the reader executing this Chapter possesses a sound knowledge of BSD-style hard disk partitioning and labeling schemes, device naming conventions and so on. If in case you have no idea at all of what I am talking about or of OpenBSD in general, I strongly suggest you to go back to the earlier section and read through its entire contents. Though the material is FreeBSD specific, most of it apply to OpenBSD as well since OpenBSD like any other BSD out there follows the "slicing" scheme.</para>
Note: I assume, the reader executing this Chapter possesses a sound knowledge of BSD-style hard disk partitioning and labeling schemes, device naming conventions and so on. If in case you have no idea at all of what I am talking about or of OpenBSD in general, I strongly suggest you to go back to the earlier section and read through its entire contents. Though the material is FreeBSD specific, most of it apply to OpenBSD as well since OpenBSD like any other BSD out there follows the slicing scheme.</para>
<para>
A few significant points to remember: In Linux, an entry like /dev/hda1 refers to a partition which in FreeBSD is likely to be labeled /dev/ad0s1. The OpenBSD counterpart would be /dev/wd0a for the first hard disk drive, /dev/wd1a for the second hard disk drive and so on. OpenBSD disklabel allows up to 16 partitions. It can detect and represent all primary partitions that exist on the hard disk. OpenBSD disklabel though sees all partitions within an extended partition but it does not list the extended partition container. Readers must note that OpenBSD reserves the c: partition which represents the entire hard disk, i: through p: are reserved for partitions belonging to other operating systems other than OpenBSD (for example Windows or Linux partitions), with a:, b: and d: - h: available for OpenBSD specific partitions. Thus the word "partition", without qualification, usually refers to a UNIX disk area on which a filesystem will be mounted.</para>
A few significant points to remember: In Linux, an entry like /dev/hda1 refers to a partition which in FreeBSD is likely to be labeled /dev/ad0s1. The OpenBSD counterpart would be /dev/wd0a for the first hard disk drive, /dev/wd1a for the second hard disk drive and so on. OpenBSD disklabel allows up to 16 partitions. It can detect and represent all primary partitions that exist on the hard disk. OpenBSD disklabel though sees all partitions within an extended partition but it does not list the extended partition container. Readers must note that OpenBSD reserves the c: partition which represents the entire hard disk, i: through p: are reserved for partitions belonging to other operating systems other than OpenBSD (for example Windows or Linux partitions), with a:, b: and d: - h: available for OpenBSD specific partitions. Thus the word <emphasis>partition</emphasis>, without qualification, usually refers to a UNIX disk area on which a filesystem will be mounted.</para>
<section>
<title>Summary of Installation Steps</title>
<para>
For a complete step-by-step coverage of OpenBSD installation, please consult the "Installing OpenBSD Manual" available on the OpenBSD Project web site. As in the previous Chapter, here also, I would be mentioning only the significant steps for the installation. Use these steps to install OpenBSD on your computer and configure it for "multi-booting":</para>
For a complete step-by-step coverage of OpenBSD installation, please consult the <emphasis>Installing OpenBSD Manual</emphasis> available on the OpenBSD Project web site. As in the previous Chapter, here also, I would be mentioning only the significant steps for the installation. Use these steps to install OpenBSD on your computer and configure it for multi-booting:</para>
<orderedlist>
<listitem>
<para>We have a computer running a Microsoft Windows operating system. On my PC, it is Windows 98 (SE). I put a bootable OpenBSD 3.2-RELEASE CD-ROM in the CD-ROM drive and reboot the system.</para>
</listitem>
<listitem>
<para>The computer boots, reads the CD-ROM, displays the usual hardware probing messages on the screen and presents you with an interactive text-based installation program. Readers must note: There are several ways to install OpenBSD onto a disk. The easiest way, should your computer support it, is to boot off the CD-ROM. Otherwise, you can boot from a 3.5" 1.44MB floppy disk. You should now be ready to install OpenBSD.</para>
<para>The computer boots, reads the CD-ROM, displays the
usual hardware probing messages on the screen and presents
you with an interactive text-based installation
program. Readers must note: There are several ways to
install OpenBSD onto a disk. The easiest way, should your
computer support it, is to boot off the CD-ROM. Otherwise,
you can boot from a 3.5 inch 1.44MB floppy disk. You should now be ready to install OpenBSD.</para>
</listitem>
<listitem>
<para> Read the questions that appear on the screen and answer them accordingly. Think twice before committing to the installation. If any question has a default answer, it will be displayed in brackets ("[ ]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you will have to begin the installation process again from scratch.</para>
<para> Read the questions that appear on the screen and answer them accordingly. Think twice before committing to the installation. If any question has a default answer, it will be displayed in brackets ([ ]) after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you will have to begin the installation process again from scratch.</para>
</listitem>
<listitem>
<para>You will next be asked for your terminal type. You should just hit return to select the default (vt220). vt220 refers to "Console" rather than serial/dial-up or network/pseudo terminals.</para>
<para>You will next be asked for your terminal type. You should just hit return to select the default (vt220). vt220 refers to Console rather than serial/dial-up or network/pseudo terminals.</para>
</listitem>
<listitem>
<para>After entering the terminal type you will be asked whether you wish to do an "(I)nstall" or an "(U)pgrade". Enter 'I' for a fresh install or 'U' to upgrade an existing installation.</para>
<para>After entering the terminal type you will be asked
whether you wish to do an <screen>(I)nstall" or an "(U)pgrade</screen>. Enter 'I' for a fresh install or 'U' to upgrade an existing installation.</para>
</listitem>
<listitem>
<para> You will be presented with a welcome message and asked if you really wish to install (or upgrade). Assuming you answered yes, the install program will then tell you which disks of that type it can install on, and ask you which it should use. Check whether OpenBSD correctly assigns the corresponding device file to your hard disk or not. OpenBSD assigned my first IDE hard disk a label /dev/wd0.</para>
@ -845,7 +902,7 @@ For a complete step-by-step coverage of OpenBSD installation, please consult the
<para>Then, select a [no] and press enter, when OpenBSD asks you whether you want to assign the whole hard disk for installing OpenBSD or not. I select a no here, cause I am preparing a multi-boot system that would run 3 operating systems!</para>
</listitem>
<listitem>
<para>Proceed with the installation as usual till you reach the OpenBSD fdisk. If fdisk is being invoked on your behalf, it will start by displaying the current partitions defined and then allow you to modify this information, add new partitions and change which partition to boot from by default. Here, I have to create a slice with "Partition ID#": A6 that would be used later for installing OpenBSD 3.2. Readers must note: FreeBSD partition ID is A5 and is different from OpenBSD partition ID A6. So while creating the slice, the ID should be A6 and not A5.</para>
<para>Proceed with the installation as usual till you reach the OpenBSD fdisk. If fdisk is being invoked on your behalf, it will start by displaying the current partitions defined and then allow you to modify this information, add new partitions and change which partition to boot from by default. Here, I have to create a slice with <quote>Partition ID#</quote>: A6 that would be used later for installing OpenBSD 3.2. Readers must note: FreeBSD partition ID is A5 and is different from OpenBSD partition ID A6. So while creating the slice, the ID should be A6 and not A5.</para>
</listitem>
<listitem>
<para>I had an output like this on my screen after I successfully created my OpenBSD slice.</para>
@ -860,31 +917,32 @@ Starting Ending LBA Info:
</listitem>
<listitem>
<para>
Try to understand the geometry. It represents the actual physical geometry or arrangement of my hard disk. The number of sectors available are given. The 2 sections containing the "Starting" and "Ending" C (cylinder), H (heads) and S (sectors) are also given. I started out with the first slice with ID: 0B only available. The information under LBA Info shows me that it is a Microsoft Windows 95 FAT32 filesystem partition. Hey! that is the one I created when I installed Microsoft Windows 98 (SE) in it.</para>
Try to understand the geometry. It represents the actual physical geometry or arrangement of my hard disk. The number of sectors available are given. The 2 sections containing the <quote>Starting</quote> and <quote>Ending</quote> C (cylinder), H (heads) and S (sectors) are also given. I started out with the first slice with ID: 0B only available. The information under LBA Info shows me that it is a Microsoft Windows 95 FAT32 filesystem partition. Hey! that is the one I created when I installed Microsoft Windows 98 (SE) in it.</para>
</listitem>
<listitem>
<para>I then create a new slice, with filesystem ID#: A6 to represent an OpenBSD slice, mention the "Starting" and "Ending" cylinders, heads and sectors and finally (very important) set the slice bootable by setting the appropriate flag from the command line. This is shown by the asterisk (*) before the starting of the second slice (#1:) is represented as (*#1:). It tells the MBR code to execute the OpenBSD boot loader cause it will in turn boot my other operating system.</para>
<para>I then create a new slice, with filesystem ID#: A6 to represent an OpenBSD slice, mention the Starting and Ending cylinders, heads and sectors and finally (very important) set the slice bootable by setting the appropriate flag from the command line. This is shown by the asterisk (*) before the starting of the second slice (#1:) is represented as (*#1:). It tells the MBR code to execute the OpenBSD boot loader cause it will in turn boot my other operating system.</para>
</listitem>
<listitem>
<para>Enter a "quit" and not an "exit" on the command line and exit the OpenBSD fdisk partition editor. Readers must note: Typing "quit" means to exit the editor saving the changes and "exit" means to exit the editor without saving any changes. So, we do a "quit", not an "exit".</para>
<para>Enter a <emphasis>quit</emphasis> and not an <emphasis>exit</emphasis> on the command line and exit the OpenBSD fdisk partition editor. <important>
<para>DO A <emphasis>quit</emphasis>, not an <emphasis>exit</emphasis>.</para>
</listitem>
<listitem>
<para>Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an interactive editor allowing you to do this. I create a swap of about a few thousand bytes, and provide the rest to the "a" partition i.e. to the "root" directory on the filesystem. The install program will now label your disk and ask which filesystems should be created on which partitions. It will automatically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a filesystem created on. </para>
<para>Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an interactive editor allowing you to do this. I create a swap of about a few thousand bytes, and provide the rest to the <quote>a</quote> partition i.e. to the root directory on the filesystem. The install program will now label your disk and ask which filesystems should be created on which partitions. It will automatically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a filesystem created on. </para>
</listitem>
<listitem>
<para>After all your filesystems have been created, the install program will give you an opportunity to configure the network. Next, you are prompted to configure your network interfaces, default route and IP address of the primary name server to and the host table.</para>
</listitem>
<listitem>
<para>Once all these done, you will be able to extract the distribution sets onto your system. When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "cd0". Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition "a".</para>
<para>Once all these done, you will be able to extract the distribution sets onto your system. When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be cd0. Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition <quote>a</quote>.</para>
</listitem>
<listitem>
<para>Next you will have to identify the filesystem type that has been used to create the distribution on the CD-ROM, this can be either FFS or ISO CD9660. The OpenBSD CD distribution uses the CD9660 format.</para>
</listitem>
<listitem>
<para>You will also have to provide the relative path to the directory on the CD which holds the distribution, for the i386 this is "3.2/i386".</para>
<para>You will also have to provide the relative path to the directory on the CD which holds the distribution, for the i386 this is 3.2/i386.</para>
</listitem>
<listitem>
<para>When all the selected distribution sets has been extracted, you will be allowed to select which time zone your system will be using, all the device nodes needed by the installed system will be created for you and the filesystems will be unmounted. For this to work properly, it is expected that you have installed at least the "base32", "etc32", and "bsd" distribution sets. </para>
<para>When all the selected distribution sets has been extracted, you will be allowed to select which time zone your system will be using, all the device nodes needed by the installed system will be created for you and the filesystems will be unmounted. For this to work properly, it is expected that you have installed at least the base32, etc32, and bsd distribution sets. </para>
</listitem>
<listitem>
<para>A message will appear on your screen telling you that OpenBSD 3.2 operating system has been successfully installed on your computer. Type in halt to halt the system and reboot.</para>
@ -893,7 +951,7 @@ Try to understand the geometry. It represents the actual physical geometry or ar
<para>When I reboot for the first time, I get the following prompt on the screen: F1 DOS, F2 BSD each in one line. I press the F1 functional key to boot into Windows 98 (SE) and check whether everything is working perfectly or not. As it so happens, it does! Then I reboot and this time, I press F2, which logs me into OpenBSD 3.2. </para>
</listitem>
<listitem>
<para>Depending on the configuration of your computer, you will receive bootup messages on your screen when you boot into OpenBSD for the first time. Though the messages scroll off the screen rather fast for you to read anything productive, you can always read it later by using the "/sbin/dmesg | more" command. Finally, you will arrive at the login prompt. Login using the username/password you set during installation. Check if everything is in place or not and try exploring the new system.</para>
<para>Depending on the configuration of your computer, you will receive bootup messages on your screen when you boot into OpenBSD for the first time. Though the messages scroll off the screen rather fast for you to read anything productive, you can always read it later by using the <screen>/sbin/dmesg | more</screen> command. Finally, you will arrive at the login prompt. Login using the username/password you set during installation. Check if everything is in place or not and try exploring the new system.</para>
</listitem>
<listitem>
<para>We still have Linux to install and configure. So, for doing this and more, we proceed to the next chapter, Chapter 6: Installing Red Hat Linux 8.0 (Psyche).</para>
@ -912,31 +970,37 @@ Try to understand the geometry. It represents the actual physical geometry or ar
<section>
<title>Summary of Installation Steps</title>
<para>
For a complete step-by-step coverage of NetBSD installation, please consult the documentation available on the NetBSD Project web site. As in the previous Chapter, here also, I would be mentioning only the significant steps for the installation. Use these steps to install NetBSD on your computer and configure it for "multi-booting":<orderedlist>
For a complete step-by-step coverage of NetBSD installation, please consult the documentation available on the NetBSD Project web site. As in the previous Chapter, here also, I would be mentioning only the significant steps for the installation. Use these steps to install NetBSD on your computer and configure it for multi-booting:<orderedlist>
<listitem>
<para>We have a computer running a Microsoft Windows operating system. On my PC, it is Windows 98 (SE). I put a bootable NetBSD 1.6.1 CD-ROM in the CD-ROM drive and reboot the system.</para>
</listitem>
<listitem>
<para>The computer boots, reads the CD-ROM, displays the usual hardware probing messages on the screen and presents you with an installation program. Readers must note: There are several ways to install NetBSD onto a disk. The easiest way, should your computer support it, is to boot off the CD-ROM. Otherwise, you can boot from a 3.5" 1.44MB floppy disk. You should now be ready to install NetBSD. </para>
<para>The computer boots, reads the CD-ROM, displays the
usual hardware probing messages on the screen and presents
you with an installation program. Readers must note: There
are several ways to install NetBSD onto a disk. The
easiest way, should your computer support it, is to boot
off the CD-ROM. Otherwise, you can boot from a 3.5 inch 1.44MB floppy disk. You should now be ready to install NetBSD. </para>
</listitem>
<listitem>
<para> 3. The blue-colored NetBSD 1.6.1 Installation Tool is called sysinst. At the very beginning, you receive a "Welcome to sysinst" screen. Select the option "Install NetBSD to hard disk" and press enter.</para>
<para> 3. The blue-colored NetBSD 1.6.1 Installation Tool is called sysinst. At the very beginning, you receive a <screen>Welcome to sysinst</screen> Select the option <screen>Install NetBSD to hard disk</screen> and press enter.</para>
</listitem>
<listitem>
<para> 4. This presents you a confirmation screen, select "Yes" and press enter.</para>
<para> 4. This presents you a confirmation screen, select Yes and press enter.</para>
</listitem>
<listitem>
<para> 5. Your hard disk is detected and NetBSD labels it correspondingly. On my PC, my first IDE HDD gets labeled as wd0. Hit enter to continue.</para>
</listitem>
<listitem>
<para> 6. Next appears the "Disk Geometry" screen where your hard disk geometry is matched with the BIOS geometry. If sysinst was unable to uniquely match the disk you chose with a disk known to the BIOS, then you have to set the disk geometry by hand. In my case, the disk matches the following BIOS disk:</para>
<para> 6. Next appears the Disk Geometry screen where your hard disk geometry is matched with the BIOS geometry. If sysinst was unable to uniquely match the disk you chose with a disk known to the BIOS, then you have to set the disk geometry by hand. In my case, the disk matches the following BIOS disk:</para>
<screen>
BIOS# cylinders heads sectors
0 1023 255 63
</screen>
</listitem>
<listitem>
<para> 7. Thus I select, "This is the correct geometry" and press enter. Next comes the screen where you have to make the choice that you would like to multi-boot your system and not dangerously-dedicate your system. Select "Use only part of the disk" instead of "Use the entire disk" and press enter.</para>
<para> 7. Thus I select, <screen>This is the
correct geometry</screen> and press enter. Next comes the screen where you have to make the choice that you would like to multi-boot your system and not dangerously-dedicate your system. Select <screen>Use only part of the disk</screen> instead of <screen>Use the entire disk and press enter.</para>
</listitem>
<listitem>
<para> 8. Proceed to choose the "size unit to use". I chose "Megabytes" as my size specifier.</para>