* [gentoo-doc-cvs] cvs commit: hb-install-x86-about.xml
@ 2006-02-09 19:17 Shyam Mani
0 siblings, 0 replies; 3+ messages in thread
From: Shyam Mani @ 2006-02-09 19:17 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 06/02/09 19:17:28
Modified: xml/htdocs/doc/en/handbook/draft/2006.0 hb-install-about.xml
Added: xml/htdocs/doc/en/handbook/draft/2006.0
hb-install-x86-about.xml
Log:
Split install-about to be x86 specific
Revision Changes Path
1.2 +4 -5 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: hb-install-about.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-about.xml 1 Feb 2006 18:38:17 -0000 1.1
+++ hb-install-about.xml 9 Feb 2006 19:17:28 -0000 1.2
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.2 2006/02/09 19:17:28 fox2mike Exp $ -->
<sections>
@@ -263,10 +263,9 @@
<ul>
<li>
- The <b>x86</b> architecture (x86, athlon-xp, pentium3, pentium4)
- Note: The x86 packages (packages-x86-2006.0.iso) are available on
- our mirrors, while pentium3, pentium4 and athlon-xp are only available
- via bittorrent.
+ The <b>i686</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro,
+ pentium2, pentium3, pentium4 and pentium-m)
+ Note: The i686 packages are available on the Installer LiveCD.
</li>
<li>
The <b>amd64</b> architecture (amd64)
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: hb-install-x86-about.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml,v 1.1 2006/02/09 19:17:28 fox2mike Exp $ -->
<sections>
<version>5.0</version>
<date>2005-08-08</date>
<section>
<title>Introduction</title>
<subsection>
<title>Welcome!</title>
<body>
<p>
First of all, <e>welcome</e> to Gentoo. You are about to enter the world
of choices and performance. Gentoo is all about choices. When
installing Gentoo, this is made clear to you several times -- you can
choose how much you want to compile yourself, how to install Gentoo,
what system logger you want, etc.
</p>
<p>
Gentoo is a fast, modern metadistribution with a clean and flexible
design. Gentoo is built around free software and doesn't hide from its
users what is beneath the hood. Portage, the package maintenance system
which Gentoo uses, is written in Python, meaning you can easily view and
modify the source code. Gentoo's packaging system uses source code
(although support for precompiled packages is included too) and
configuring Gentoo happens through regular textfiles. In other words,
openness everywhere.
</p>
<p>
It is very important that you understand that <e>choices</e> are what
makes Gentoo run. We try not to force you onto anything you don't like.
If you feel like we do, please <uri
link="http://bugs.gentoo.org">bugreport</uri> it.
</p>
</body>
</subsection>
<subsection>
<title>How is the Installation Structured?</title>
<body>
<p>
The Gentoo Installation can be seen as a 10-step procedure,
corresponding to chapters 2 - 11. Every step results in
a certain state:
</p>
<ul>
<li>
After step 1, you are in a working environment ready to install Gentoo
</li>
<li>
After step 2, your internet connection is prepared in case you need it (this
is however optional)
</li>
<li>
After step 3, your hard disks are initialized to house your Gentoo
installation
</li>
<li>
After step 4, your installation environment is prepared and you are
ready to chroot into the new environment
</li>
<li>
After step 5, core packages, which are the same on all Gentoo
installations, are installed
</li>
<li>
After step 6, you have compiled your Linux kernel
</li>
<li>
After step 7, you have written most of your Gentoo system
configuration files
</li>
<li>
After step 8, necessary system tools (which you can choose from a nice
list) are installed
</li>
<li>
After step 9, your choice of bootloader has been installed and
configured and you are logged in into your new Gentoo installation
</li>
<li>
After step 10, your Gentoo Linux environment is ready to be explored
</li>
</ul>
<p>
When you are given a certain choice, we try our best to explain what the pros
and cons are. We will continue then with a default
choice, identified by "Default: " in the title. The other
possibilities are marked by "Alternative: ". Do <e>not</e>
think that the default is what we recommend. It is however what we
believe most users will use.
</p>
<p>
Sometimes you can pursue an optional step. Such steps are marked as
"Optional: " and are therefore not needed to install Gentoo.
However, some optional steps are dependant on a previous decision you
made. We will inform you when this happens, both when you make the
decision, and right before the optional step is described.
</p>
</body>
</subsection>
<subsection>
<title>What are my Options?</title>
<body>
<p>
You can install Gentoo in many different ways. You can download and install from
one of our Installation CDs, from an existing distribution,
from a bootable CD (such as Knoppix), from a netbooted environment, from a
rescue floppy, etc.
</p>
<p>
This document covers the installation using the Installer LiveCD, a
bootable CD that contains everything you need to get Gentoo Linux up and
running.
</p>
<p>
This installation approach however does not immediately use the latest version
of the available packages; if you want this you should check out the
Installation Instructions inside our <uri
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>.
</p>
<p>
For help on the other installation approaches,
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation
Guide</uri>. We also provide a <uri
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips &
Tricks</uri> document that might be useful to read as well. If you feel that
the current installation instructions are too elaborate, feel free to use our
Quick Installation Guide available from our <uri
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture
has such a document available.
</p>
</body>
</subsection>
<subsection>
<title>Troubles?</title>
<body>
<p>
If you find a problem in the installation (or in the installation
documentation), please check the errata from our <uri
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>,
visit our <uri link="http://bugs.gentoo.org">bugtracking
system</uri> and check if the bug is known. If not, please create a bugreport
for it so we can take care of it. Do not be afraid of the developers who are
assigned to (your) bugs -- they generally don't eat people.
</p>
<p>
Note though that, although the document you are now reading is
architecture-specific, it will contain references to other architectures as
well. This is due to the fact that large parts of the Gentoo Handbook use source
code that is common for all architectures (to avoid duplication of efforts and
starvation of development resources). We will try to keep this to a minimum
to avoid confusion.
</p>
<p>
If you are uncertain if the problem is a user-problem (some error you
made despite having read the documentation carefully) or a
software-problem (some error we made despite having tested the
installation/documentation carefully) you are free to join #gentoo on
irc.freenode.net. Of course, you are welcome otherwise too :)
</p>
<p>
If you have a question regarding Gentoo, check out our <uri
link="/doc/en/faq.xml">Frequently Asked
Questions</uri>, available from the <uri
link="/doc/en/">Gentoo Documentation</uri>. You can
also view the <uri
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of
us are freaks who sit on IRC :-)
</p>
</body>
</subsection>
</section>
<section>
<title>Fast Installation using the Gentoo Reference Platform</title>
<subsection>
<title>What is the Gentoo Reference Platform?</title>
<body>
<p>
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of
prebuilt packages users (that means you!) can install during the installation
of Gentoo to speed up the installation process. The GRP consists of all
packages required to have a fully functional Gentoo installation. They are not
just the ones you need to have a base installation up to speed in no time, but
all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...)
are available as GRP packages too.
</p>
<p>
However, these prebuilt packages aren't maintained during the lifetime of the
Gentoo distribution. They are snapshots released at every Gentoo release and
make it possible to have a functional environment in a short amount of time. You
can then upgrade your system in the background while working in your Gentoo
environment.
</p>
</body>
</subsection>
<subsection>
<title>How Portage Handles GRP Packages</title>
<body>
<p>
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all
information about a package, such as its description, homepage, sourcecode URLs,
compilation instructions, dependencies, etc.) - must be synchronised with the
GRP set: the versions of the available ebuilds and their accompanying GRP
packages must match.
</p>
<p>
For this reason you can only benefit from the GRP packages Gentoo provides while
performing the current installation approach. GRP is not available for those
interested in performing an installation using the latest versions of all
available packages.
</p>
</body>
</subsection>
<subsection>
<title>Is GRP Available?</title>
<body>
<p>
Not all architectures provide GRP packages. That doesn't mean GRP isn't
supported on the other architectures, but it means that we don't have the
resources to build and test the GRP packages.
</p>
<p>
At present we provide GRP packages for the following architectures:
</p>
<ul>
<li>
The <b>i686</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro,
pentium2, pentium3, pentium4 and pentium-m)
Note: The i686 packages are available on the Installer LiveCD.
</li>
<li>
The <b>amd64</b> architecture (amd64)
</li>
<li>
The <b>sparc</b> architecture (sparc64)
</li>
<li>
The <b>ppc</b> architecture (G3, G4, G5)
</li>
<li>
The <b>alpha</b> architecture
</li>
</ul>
<p>
If your architecture (or subarchitecture) isn't on this list, you are not
able to opt for a GRP installation.
</p>
<p>
Now that this introduction is over, let's continue with <uri
link="?part=1&chap=2">Booting the Installer LiveCD</uri>.
</p>
</body>
</subsection>
</section>
</sections>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-doc-cvs] cvs commit: hb-install-x86-about.xml
@ 2006-02-10 17:12 Shyam Mani
0 siblings, 0 replies; 3+ messages in thread
From: Shyam Mani @ 2006-02-10 17:12 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 06/02/10 17:12:36
Removed: xml/htdocs/doc/en/handbook/draft/2006.0
hb-install-x86-about.xml
Log:
Messup
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-doc-cvs] cvs commit: hb-install-x86-about.xml
@ 2006-02-10 17:46 Shyam Mani
0 siblings, 0 replies; 3+ messages in thread
From: Shyam Mani @ 2006-02-10 17:46 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 06/02/10 17:46:25
Modified: xml/htdocs/doc/en/handbook/draft/2006.0 hb-install-about.xml
hb-install-x86-medium.xml
Added: xml/htdocs/doc/en/handbook/draft/2006.0
hb-install-x86-about.xml hb-install-x86-network.xml
Log:
More fixes for x86 + fixing my earlier messup of removing install-x86-about
Revision Changes Path
1.3 +26 -26 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: hb-install-about.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hb-install-about.xml 9 Feb 2006 19:17:28 -0000 1.2
+++ hb-install-about.xml 10 Feb 2006 17:46:25 -0000 1.3
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.2 2006/02/09 19:17:28 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.3 2006/02/10 17:46:25 fox2mike Exp $ -->
<sections>
-<version>5.0</version>
-<date>2005-08-08</date>
+<version>5.1</version>
+<date>2006-02-09</date>
<section>
<title>Introduction</title>
@@ -19,28 +19,27 @@
<p>
First of all, <e>welcome</e> to Gentoo. You are about to enter the world
-of choices and performance. Gentoo is all about choices. When
-installing Gentoo, this is made clear to you several times -- you can
-choose how much you want to compile yourself, how to install Gentoo,
-what system logger you want, etc.
+of customization and performance. When installing Gentoo, this is made clear to
+you several times -- you can choose how much you want to compile yourself, how
+to install Gentoo, what system logger you want, etc.
</p>
<p>
-Gentoo is a fast, modern metadistribution with a clean and flexible
+Gentoo is a fast, modern meta-distribution with a clean and flexible
design. Gentoo is built around free software and doesn't hide from its
users what is beneath the hood. Portage, the package maintenance system
which Gentoo uses, is written in Python, meaning you can easily view and
modify the source code. Gentoo's packaging system uses source code
(although support for precompiled packages is included too) and
-configuring Gentoo happens through regular textfiles. In other words,
+configuring Gentoo happens through regular text files. In other words,
openness everywhere.
</p>
<p>
-It is very important that you understand that <e>choices</e> are what
-makes Gentoo run. We try not to force you onto anything you don't like.
-If you feel like we do, please <uri
-link="http://bugs.gentoo.org">bugreport</uri> it.
+It is very important that you understand that <e>empowerment</e> is what makes
+Gentoo run. We try not to force anything on our users and try our best to
+empower you to make the choices you wish. If you feel a change should be made,
+please file a <uri link="http://bugs.gentoo.org">bug report</uri> about it.
</p>
</body>
@@ -126,11 +125,9 @@
</p>
<p>
-This document covers the installation using the Universal Installation CD, a
+This document covers the installation using the Installer LiveCD, a
bootable CD that contains everything you need to get Gentoo Linux up and
-running. You can optionally use one of our Package CDs as well to install a
-complete system in a matter of minutes after having installed the Gentoo base
-system.
+running.
</p>
<p>
@@ -162,8 +159,8 @@
If you find a problem in the installation (or in the installation
documentation), please check the errata from our <uri
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>,
-visit our <uri link="http://bugs.gentoo.org">bugtracking
-system</uri> and check if the bug is known. If not, please create a bugreport
+visit our <uri link="http://bugs.gentoo.org">bug tracking
+system</uri> and check if the bug is known. If not, please create a bug report
for it so we can take care of it. Do not be afraid of the developers who are
assigned to (your) bugs -- they generally don't eat people.
</p>
@@ -212,7 +209,7 @@
of Gentoo to speed up the installation process. The GRP consists of all
packages required to have a fully functional Gentoo installation. They are not
just the ones you need to have a base installation up to speed in no time, but
-all lengthier builds (such as KDE, xorg-x11, GNOME, OpenOffice, Mozilla, ...)
+all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...)
are available as GRP packages too.
</p>
@@ -263,21 +260,24 @@
<ul>
<li>
- The <b>i686</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro,
- pentium2, pentium3, pentium4 and pentium-m)
- Note: The i686 packages are available on the Installer LiveCD.
+ The <b>alpha</b> architecture (alpha)
</li>
<li>
The <b>amd64</b> architecture (amd64)
</li>
<li>
- The <b>sparc</b> architecture (sparc64)
+ The <b>hppa</b> architecture (hppa1.1, hppa2.0)
+ </li>
+ <li>
+ The <b>ppc</b> architecture (ppc32, ppc64)
</li>
<li>
- The <b>ppc</b> architecture (G3, G4, G5)
+ The <b>sparc</b> architecture (sparc64)
</li>
<li>
- The <b>alpha</b> architecture
+ The <b>x86</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro,
+ pentium2, pentium3, pentium4 and pentium-m) Note: The packages are for x86
+ and are available on the Installer LiveCD.
</li>
</ul>
1.4 +192 -54 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo
Index: hb-install-x86-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- hb-install-x86-medium.xml 9 Feb 2006 19:19:30 -0000 1.3
+++ hb-install-x86-medium.xml 10 Feb 2006 17:46:25 -0000 1.4
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v 1.3 2006/02/09 19:19:30 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v 1.4 2006/02/10 17:46:25 fox2mike Exp $ -->
<sections>
-<version>5.5</version>
-<date>2005-11-29</date>
+<version>5.6</version>
+<date>2006-02-09</date>
<section>
<title>Hardware Requirements</title>
@@ -19,7 +19,7 @@
<p>
Before we start, we first list what hardware requirements you need to
-successfully install Gentoo on your box.
+successfully install Gentoo on your box using the Installer LiveCD.
</p>
</body>
@@ -31,11 +31,11 @@
<table>
<tr>
<th>CPU</th>
- <ti>i486 or later</ti>
+ <ti>i686 or later</ti>
</tr>
<tr>
<th>Memory</th>
- <ti>64 MB</ti>
+ <ti>128 MB</ti>
</tr>
<tr>
<th>Diskspace</th>
@@ -90,11 +90,10 @@
<ul>
<li>
- The Installer LiveCD contains everything you need to install
- Gentoo. It provides a graphical environment, a graphical as well as console
- based installer which automatically carries out the installation for you,
- source code for the extra applications you need to choose from, GRP
- Packages and of course, the installation instructions for your architecture.
+ The Installer LiveCD contains everything you need to install Gentoo. It
+ provides a graphical environment, a graphical as well as console based
+ installer which automatically carries out the installation for you, and of
+ course, the installation instructions for your architecture.
</li>
<li>
The Minimal Installation CD contains only a minimal environment that allows
@@ -104,15 +103,6 @@
</li>
</ul>
-<p>
-The Gentoo Linux Installer LiveCD also provides an additional resource that you
-can exploit during the installation of your Gentoo system. It contains prebuilt
-packages (also known as the GRP set) that allow you to easily and quickly
-install additional applications (such as OpenOffice.org, GNOME, ...)
-immediately after the Gentoo installation and right before you update your
-Portage tree.
-</p>
-
</body>
</subsection>
</section>
@@ -246,30 +236,152 @@
<p>
You can also provide kernel options. They represent optional settings you can
(de)activate at will. The following list is the same as the one you receive
-when you press F2 at the bootscreen.
+when you press F2 through F7 at the bootscreen.
</p>
<pre caption="Options available to pass to your kernel of choice">
-- agpgart loads agpgart (use if you have graphic problems,lockups)
-- acpi=on loads support for ACPI firmware
-- ide=nodma force disabling of DMA for malfunctioning IDE devices
-- doscsi scan for scsi devices (breaks some ethernet cards)
-- dopcmcia starts pcmcia service for PCMCIA cdroms
-- nofirewire disables firewire modules in initrd (for firewire cdroms,etc)
-- nokeymap disables keymap selection for non-us keyboard layouts
-- docache cache the entire runtime portion of cd in RAM, allows you
- to umount /mnt/cdrom to mount another cdrom.
-- nodetect causes hwsetup/kudzu and hotplug not to run
-- nousb disables usb module load from initrd, disables hotplug
-- nodhcp dhcp does not automatically start if nic detected
-- nohotplug disables loading hotplug service
-- noapic disable apic (try if having hardware problems nics,scsi,etc)
-- noevms2 disable loading of EVMS2 modules
-- nolvm2 disable loading of LVM2 modules
-- hdx=stroke allows you to partition the whole harddrive even when your BIOS
- can't handle large harddrives
-- noload=module1[,module2[,...]]
- disable loading of specific kernel modules
+<comment>Hardware options:</comment>
+
+acpi=on This loads support for ACPI and also causes the acpid daemon to
+ be started by the CD on boot. This is only needed if your
+ system requires ACPI to function properly. This is not
+ required for Hyperthreading support.
+
+acpi=off Completely disables ACPI. This is useful on some older
+ systems, and is also a requirement for using APM. This will
+ disable any Hyperthreading support of your processor.
+
+console=X This sets up serial console access for the CD. The first
+ option is the device, usually ttyS0 on x86, followed by any
+ connection options, which are comma separated. The default
+ options are 9600,8,n,1.
+
+dmraid=X This allows for passing options to the device-mapper RAID
+ subsystem. Options should be encapsulated in quotes.
+
+doapm This loads APM driver support. This requires you to also use
+ acpi=off.
+
+dobladecenter This adds some extra pauses into the boot process for the slow
+ USB CDROM of the IBM BladeCenter.
+
+dopcmcia This loads support for PCMCIA and Cardbus hardware and also
+ causes the pcmcia cardmgr to be started by the CD on boot.
+ This is only required when booting from a PCMCIA/Cardbus device.
+
+doscsi This loads support for most SCSI controllers. This is also a
+ requirement for booting most USB devices, as they use the SCSI
+ subsystem of the kernel.
+
+hda=stroke This allows you to partition the whole hard disk even when your
+ BIOS is unable to handle large disks. This option is only used
+ on machines with an older BIOS. Replace hda with the device
+ that is requiring this option.
+
+ide=nodma This forces the disabling of DMA in the kernel and is required
+ by some IDE chipsets and also by some CDROM drives. If your
+ system is having trouble reading from your IDE CDROM, try this
+ option. This also disables the default hdparm settings from
+ being executed.
+
+noapic This disables the Advanced Programmable Interrupt Controller
+ that is present on newer motherboards. It has been known to
+ cause some problems on older hardware.
+
+nodetect This disables all of the autodetection done by the CD,
+ including device autodetection and DHCP probing. This is
+ useful for doing debugging of a failing CD or driver.
+
+nodhcp This disables DHCP probing on detected network cards. This is
+ useful on networks with only static addresses.
+
+nodmraid Disables support for device-mapper RAID, such as that used for
+ on-board IDE/SATA RAID controllers.
+
+nofirewire This disables the loading of Firewire modules. This should only
+ be necessary if your Firewire hardware is causing a problem
+ with booting the CD.
+
+nogpm This diables gpm console mouse support.
+
+nohotplug This disables the loading of the hotplug and coldplug init
+ scripts at boot. This is useful for doing debugging of a
+ failing CD or driver.
+
+nokeymap This disables the keymap selection used to select non-US
+ keyboard layouts.
+
+nolapic This disables the local APIC on Uniprocessor kernels.
+
+nosata This disables the loading of Serial ATA modules. This is
+ useful if your system is having problems with the SATA subsystem.
+
+nosmp This disables SMP, or Symmetric Multiprocessing, on SMP-enabled
+ kernels. This is useful for debugging SMP-related issues with
+ certain drivers and motherboards.
+
+nosound This disables sound support and volume setting. This is useful
+ for systems where sound support causes problems.
+
+nousb This disables the autoloading of USB modules. This is useful
+ for debugging USB issues.
+
+<comment>Volume/Device Management:</comment>
+
+dodevfs This enables the deprecated device filesystem on 2.6 systems.
+ You will also need to use noudev for this to take effect.
+ Since devfs is the only option with a 2.4 kernel, this option
+ has no effect if booting a 2.4 kernel.
+
+doevms2 This enables support for IBM's pluggable EVMS, or Enterprise
+ Volume Management System. This is not safe to use with lvm2.
+
+dolvm2 This enables support for Linux's Logical Volume Management.
+ This is not safe to use with evms2.
+
+noudev This disables udev support on 2.6 kernels. This option
+ requires that dodevfs is used. Since udev is not an option for
+ 2.4 kernels, this options has no effect if booting a 2.4
+ kernel.
+
+unionfs Enables support for Unionfs on supported CD images. This will
+ create a writable Unionfs overlay in a tmpfs, allowing you to
+ change any file on the CD.
+
+unionfs=X Enables support for Unionfs on supported CD images. This will
+ create a writable Unionfs overlay on the device you specify.
+ The device must be formatted with a filesystem recognized and
+ writable by the kernel.
+
+<comment>Other options:</comment>
+
+debug Enables debugging code. This might get messy, as it displays
+ a lot of data to the screen.
+
+docache This caches the entire runtime portion of the CD into RAM,
+ which allows you to umount /mnt/cdrom and mount another CDROM.
+ This option requires that you have at least twice as much
+ available RAM as the size of the CD.
+
+doload=X This causes the initial ramdisk to load any module listed, as
+ well as dependencies. Replace X with the module name. Multiple
+ modules can be specified by a comma-separated list.
+
+noload=X This causes the initial ramdisk to skip the loading of a
+ specific module that may be causing a problem. Syntax matches
+ that of doload.
+
+nox This causes an X-enabled LiveCD to not automatically start X,
+ but rather, to drop to the command line instead.
+
+scandelay This causes the CD to pause for 10 seconds during certain
+ portions the boot process to allow for devices that are slow to
+ initialize to be ready for use.
+
+scandelay=X This allows you to specify a given delay, in seconds, to be
+ added to certain portions of the boot process to allow for
+ devices that are slow to initialize to be ready for use.
+ Replace X with the number of seconds to pause.
</pre>
<p>
@@ -288,13 +400,24 @@
installing Gentoo on a system with a non-US keyboard, make sure you
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no
selection is made in 10 seconds the default (US keyboard) will be accepted and
-the boot process will continue. Once the boot process completes, Gnome will start
-up and you will be automatically logged in to the "Live" Gentoo Linux as
-"gentoo" in graphical mode. You will be logged in as "root", the superuser on
-the other consoles and should have a root ("#") prompt there. You can switch to
-those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6. Get back to
-the graphical desktop you started on by pressing Alt-F7.
-</p>
+the boot process will continue. Once the boot process completes, Gnome will
+start up and you will be automatically logged in to the "Live" Gentoo Linux
+system as "gentoo" in graphical mode. You will be logged in as "root", the
+superuser on the other consoles and should have a root ("#") prompt there. You
+can switch to those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6.
+Get back to the graphical desktop you started on by pressing Alt-F7. To switch
+to other consoles from within X, you must prefix the above with Ctrl. You are
+able to run commands as root from any terminal within the graphical environment
+by using the <c>sudo</c> application. You can even become root within a
+terminal to perform multiple tasks.
+</p>
+
+<pre caption="Using sudo to run applications">
+<comment>(Editing the group file)</comment>
+# <i>sudo vi /etc/group</i>
+<comment>(Becoming root for a session)</comment>
+# <i>sudo su -</i>
+</pre>
</body>
</subsection>
@@ -308,7 +431,7 @@
vast majority of cases, it does a very good job. However, in some cases, it
may not auto-load the kernel modules you need. If the PCI auto-detection
missed some of your system's hardware, you will have to load the appropriate
-kernel modules manually.
+kernel modules manually. These tasks require root access.
</p>
<p>
@@ -336,9 +459,9 @@
<p>
If you are an advanced user, you might want to tweak the IDE hard disk
-performance using <c>hdparm</c>. With the <c>-tT</c> options you can
-test the performance of your disk (execute it several times to get a
-more precise impression):
+performance using <c>hdparm</c>. You will need root access to use <c>hdparm</c>.
+With the <c>-tT</c> options you can test the performance of your disk (execute
+it several times to get a more precise impression):
</p>
<pre caption="Testing disk performance">
@@ -366,7 +489,8 @@
If you plan on giving other people access to your installation
environment or you want to chat using <c>irssi</c> without root privileges (for
security reasons), you need to create the necessary user accounts and change
-the root password.
+the root password. You need root access to change the root password and add new
+users.
</p>
<p>
@@ -374,6 +498,7 @@
</p>
<pre caption="Changing the root password">
+$ <i>sudo su -</i>
# <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
@@ -401,6 +526,18 @@
# <i>su - john</i>
</pre>
+<p>
+You can also change the password for the "gentoo" user in the graphical
+environment. This account is already suitable for use on the Internet.
+</p>
+
+<pre caption="Changing the gentoo password">
+$ <i>passwd</i>
+New password: <comment>(Enter your new password)</comment>
+Re-enter password: <comment>(Re-enter your password)</comment>
+</pre>
+
+
</body>
</subsection>
<subsection>
@@ -450,7 +587,8 @@
Gentoo installation (perhaps because those users are going to help you
install Gentoo, or even do it for you), you need to create a user
account for them and perhaps even provide them with your root password
-(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
+(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). Starting the
+SSH daemon requires root access.
</p>
<p>
1.3 +23 -21 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: hb-install-x86-network.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml,v 1.1 2006/02/10 17:46:25 fox2mike Exp $ -->
<sections>
<version>5.1</version>
<date>2006-02-09</date>
<section>
<title>Do you need Networking?</title>
<subsection>
<title>Who can do without?</title>
<body>
<p>
Generally, you don't need a working network connection to install Gentoo using
the Installer LiveCD. However, there are some circumstances where you do want
to have a working Internet connection:
</p>
<ul>
<li>
The stage3 file that is generated by the Installer LiveCD does not
match your architecture and you need to download the correct stage3 file
</li>
<li>
You need to install a specific networking application that will allow you to
connect to the Internet which isn't available on the Installer LiveCD
CD but is supported by the LiveCD (i.e. you can connect to the
Internet using the LiveCD but the necessary sources are not
available on the LiveCD)
</li>
<li>
You want remote assistance during the installation (using SSH or through
direct conversations using IRC)
</li>
</ul>
</body>
</subsection>
<subsection>
<title>Do I need Networking?</title>
<body>
<p>
The stage3 file built by the Installer LiveCD is optimized for i686 or better
machines and uses NPTL.
</p>
<p>
If you, on the other hand, want to use a stage3 file optimized for your
architecture and the LiveCD's stage3 file is not sufficient, then you will
need networking to download the appropriate stage3 file.
</p>
<p>
So, if you don't need networking, you can skip the rest of this chapter and
continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>.
Otherwise, continue with the networking configuration sections below.
</p>
</body>
</subsection>
</section>
<section>
<title>Automatic Network Detection</title>
<subsection>
<title>Maybe it just works?</title>
<body>
<p>
If your system is plugged into an Ethernet network with a DHCP server, it is
very likely that your networking configuration has already been set up
automatically for you. If so, you should be able to take advantage of the many
included network-aware commands on the Installation CD such as <c>ssh</c>,
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among
others.
</p>
<p>
If networking has been configured for you, the <c>/sbin/ifconfig</c> command
should list some network interfaces besides lo, such as eth0:
</p>
<pre caption="/sbin/ifconfig for a working network configuration">
# <i>/sbin/ifconfig</i>
<comment>(...)</comment>
eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::50:ba8f:617a/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0
TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0
collisions:1984 txqueuelen:100
RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb)
Interrupt:11 Base address:0xe800
</pre>
</body>
</subsection>
<subsection>
<title>Optional: Configure any Proxies</title>
<body>
<p>
If you access the Internet through a proxy, you might need to set up proxy
information during the installation. It is very easy to define a proxy: you just
need to define a variable which contains the proxy server information.
</p>
<p>
In most cases, you can just define the variables using the server hostname. As
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port
is <c>8080</c>.
</p>
<pre caption="Defining proxy servers">
<comment>(If the proxy filters HTTP traffic)</comment>
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i>
<comment>(If the proxy filters FTP traffic)</comment>
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i>
<comment>(If the proxy filters RSYNC traffic)</comment>
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i>
</pre>
<p>
If your proxy requires a username and password, you should use the following
syntax for the variable:
</p>
<pre caption="Adding username/password to the proxy variable">
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080
</pre>
</body>
</subsection>
<subsection>
<title>Testing the Network</title>
<body>
<p>
You may want to try pinging your ISP's DNS server (found in
<path>/etc/resolv.conf</path>) and a Web site of your choice, just to make sure
that your packets are reaching the net, DNS name resolution is working
correctly, etc.
</p>
<pre caption="Further network testing">
# <i>ping -c 3 www.yahoo.com</i>
</pre>
<p>
If you are now able to use your network, you can skip the rest of this
section and continue with <uri link="?part=1&chap=4">Preparing the
Disks</uri>. If not, read on.
</p>
</body>
</subsection>
</section>
<section>
<title>Automatic Network Configuration</title>
<subsection>
<body>
<p>
If the network doesn't work immediately, some installation media allow you to
use <c>net-setup</c> (for regular or wireless networks), <c>adsl-setup</c>
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86).
</p>
<p>
If your installation medium does not contain any of these tools or your network
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network
Configuration</uri>.
</p>
<ul>
<li>
Regular Ethernet users should continue with <uri
link="#net-setup">Default: Using net-setup</uri>
</li>
<li>
ADSL users should continue with <uri link="#rp-pppoe">Alternative:
Using RP-PPPoE</uri>
</li>
<li>
PPTP users should continue with <uri link="#pptp">Alternative:
Using PPTP</uri>
</li>
</ul>
</body>
</subsection>
<subsection id="net-setup">
<title>Default: Using net-setup</title>
<body>
<p>
The simplest way to set up networking if it didn't get configured
automatically is to run the <c>net-setup</c> script:
</p>
<pre caption="Running the net-setup script">
# <i>net-setup eth0</i>
</pre>
<p>
<c>net-setup</c> will ask you some questions about your network
environment. When all is done, you should have a working network
connection. Test your network connection as stated before. If the tests
are positive, congratulations! You are now ready to install Gentoo. Skip
the rest of this section and continue with <uri
link="?part=1&chap=4">Preparing the Disks</uri>.
</p>
<p>
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual
Network Configuration</uri>.
</p>
</body>
</subsection>
<subsection id="rp-pppoe">
<title>Alternative: Using RP-PPPoE</title>
<body>
<p>
Assuming you need PPPoE to connect to the internet, the Installation CD (any
version) has made things easy for you by including <c>rp-pppoe</c>. Use the
provided <c>adsl-setup</c> script to configure your connection. You will be
prompted for the ethernet device that is connected to your adsl modem, your
username and password, the IPs of your DNS servers and if you need a basic
firewall or not.
</p>
<pre caption="Using rp-pppoe">
# <i>adsl-setup</i>
# <i>adsl-start</i>
</pre>
<p>
If something goes wrong, double-check that you correctly typed your username and
password by looking at <path>/etc/ppp/pap-secrets</path> or
<path>/etc/ppp/chap-secrets</path> and make sure you are using the right
ethernet device. If your ethernet device doesn't exist, you will have to load
the appropriate network modules. In that case you should continue with
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to
load the appropriate network modules there.
</p>
<p>
If everything worked, continue with <uri link="?part=1&chap=4">Preparing the
Disks</uri>.
</p>
</body>
</subsection>
<subsection id="pptp">
<title>Alternative: Using PPTP</title>
<body>
<note>
PPTP support is only available for x86
</note>
<p>
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our
Installation CDs. But first you need to make sure that your configuration is
correct. Edit <path>/etc/ppp/pap-secrets</path> or
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password
combination:
</p>
<pre caption="Editing /etc/ppp/chap-secrets">
# <i>nano -w /etc/ppp/chap-secrets</i>
</pre>
<p>
Then adjust <path>/etc/ppp/options.pptp</path> if necessary:
</p>
<pre caption="Editing /etc/ppp/options.pptp">
# <i>nano -w /etc/ppp/options.pptp</i>
</pre>
<p>
When all that is done, just run <c>pptp</c> (along with the options you couldn't
set in <path>options.pptp</path>) to connect the server:
</p>
<pre caption="Connection to a dial-in server">
# <i>pptp <server ip></i>
</pre>
<p>
Now continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>.
</p>
</body>
</subsection>
</section>
<section>
<title>Manual Network Configuration</title>
<subsection>
<title>Loading the Appropriate Network Modules</title>
<body>
<p>
When the Installation CD boots, it tries to detect all your hardware devices and
loads the appropriate kernel modules (drivers) to support your hardware. In the
vast majority of cases, it does a very good job. However, in some cases,
it may not auto-load the kernel modules you need.
</p>
<p>
If <c>net-setup</c> or <c>adsl-setup</c> failed, then it is possible that
your network card wasn't found immediately. This means you may have to load
the appropriate kernel modules manually.
</p>
<p>
To find out what kernel modules we provide for networking, use
<c>ls</c>:
</p>
<pre caption="Searching for provided modules">
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i>
</pre>
<p>
If you find a driver for your network card, use <c>modprobe</c> to load
the kernel module:
</p>
<pre caption="Using modprobe to load a kernel module">
<comment>(As an example, we load the pcnet32 module)</comment>
# <i>modprobe pcnet32</i>
</pre>
<p>
To check if your network card is now detected, use <c>ifconfig</c>. A
detected network card would result in something like this:
</p>
<pre caption="Testing availability of your network card, successful">
# <i>ifconfig eth0</i>
eth0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
BROADCAST NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
</pre>
<p>
If however you receive the following error, the network card is not
detected:
</p>
<pre caption="Testing availability of your network card, failed">
# <i>ifconfig eth0</i>
eth0: error fetching interface information: Device not found
</pre>
<p>
If you have multiple network cards in your system they are named <e>eth0</e>,
<e>eth1</e>, etc. Make sure that the network card you want to use works well and
remember to use the correct naming throughout this document. We will assume that
the network card <e>eth0</e> is used.
</p>
<p>
Assuming that you now have a detected network card, you can
retry <c>net-setup</c> or <c>adsl-setup</c> again (which should work
now), but for the hardcore people amongst you we explain how to configure your
network manually.
</p>
<p>
Select one of the following sections based on your network setup:
</p>
<ul>
<li><uri link="#dhcp">Using DHCP</uri> for automatic IP retrieval</li>
<li>
<uri link="#wireless">Preparing for Wireless Access</uri> if you have a
wireless card
</li>
<li>
<uri link="#network_term">Understanding Network Terminology</uri> explains
what you need to know about networking
</li>
<li>
<uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to
set up your networking manually
</li>
</ul>
</body>
</subsection>
<subsection id="dhcp">
<title>Using DHCP</title>
<body>
<p>
DHCP (Dynamic Host Configuration Protocol) makes it possible to
automatically receive networking information (IP address, netmask,
broadcast address, gateway, nameservers etc.). This only works if you
have a DHCP server in your network (or if your provider provides a DHCP
service). To have a network interface receive this information automatically,
use <c>dhcpcd</c>:
</p>
<pre caption="Using dhcpcd">
# <i>dhcpcd eth0</i>
<comment>Some network admins require that you use the</comment>
<comment>hostname and domainname provided by the DHCP server.</comment>
<comment>In that case, use</comment>
# <i>dhcpcd -HD eth0</i>
</pre>
<p>
If this works (try pinging some internet server, like <uri
link="http://www.google.com">Google</uri>), then you are all set and
ready to continue. Skip the rest of this section and continue with <uri
link="?part=1&chap=4">Preparing the Disks</uri>.
</p>
</body>
</subsection>
<subsection id="wireless">
<title>Preparing for Wireless Access</title>
<body>
<note>
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc
Installation CDs. You can still get the extensions working otherwise
by following the instructions of the
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng
project</uri>.
</note>
<p>
If you are using a wireless (802.11) card, you may need to configure your
wireless settings before going any further. To see the current wireless settings
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show
something like:
</p>
<pre caption="Showing the current wireless settings">
# <i>iwconfig eth0</i>
eth0 IEEE 802.11-DS ESSID:"GentooNode"
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx
excessive retries:237 Invalid misc:350282 Missed beacon:84
</pre>
<note>
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to
determine the correct device name.
</note>
<p>
For most users, there are only two settings that might be important to change,
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access
Point address listed are already that of your access point and you are not using
WEP, then your wireless is working. If you need to change your ESSID, or add a
WEP key, you can issue the following commands:
</p>
<pre caption="Changing ESSID and/or adding WEP key">
<comment>(This sets the network name to "GentooNode")</comment>
# <i>iwconfig eth0 essid GentooNode</i>
<comment>(This sets a hex WEP key)</comment>
# <i>iwconfig eth0 key 1234123412341234abcd</i>
<comment>(This sets an ASCII key - prefix it with "s:")</comment>
# <i>iwconfig eth0 key s:some-password</i>
</pre>
<p>
You can then confirm your wireless settings again by using <c>iwconfig</c>.
Once you have wireless working, you can continue configuring the IP level
networking options as described in the next section (<uri
link="#network_term">Understanding Network Terminology</uri>) or use the
<c>net-setup</c> tool as described previously.
</p>
</body>
</subsection>
<subsection id="network_term">
<title>Understanding Network Terminology</title>
<body>
<note>
If you know your IP address, broadcast address, netmask and nameservers,
then you can skip this subsection and continue with <uri
link="#ifconfig_route">Using ifconfig and route</uri>.
</note>
<p>
If all of the above fails, you will have to configure your network manually.
This is not difficult at all. However, you need to be familiar with some
network terminology, as you will need it to be able to
configure your network to your satisfaction. After reading this, you
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for,
how a <e>broadcast</e> address is formed and why you need
<e>nameservers</e>.
</p>
<p>
In a network, hosts are identified by their <e>IP address</e> (Internet
Protocol address). Such an address is a combination of four numbers
between 0 and 255. Well, at least that is how we perceive it. In
reality, such an IP address consists of 32 bits (ones and zeros). Let's
view an example:
</p>
<pre caption="Example of an IP address">
IP Address (numbers): 192.168.0.2
IP Address (bits): 11000000 10101000 00000000 00000010
-------- -------- -------- --------
192 168 0 2
</pre>
<p>
Such an IP address is unique to a host as far as all accessible networks are
concerned (i.e. every host that you are able to reach must have a unique IP
address). In order to distinguish between hosts inside and outside a
network, the IP address is divided in two parts: the
<e>network</e> part and the <e>host</e> part.
</p>
<p>
The separation is written down with the <e>netmask</e>, a collection of
ones followed by a collection of zeros. The part of the IP that can be
mapped on the ones is the network-part, the other one is the host-part.
As usual, the netmask can be written down as an IP-address.
</p>
<pre caption="Example of network/host separation">
IP-address: 192 168 0 2
11000000 10101000 00000000 00000010
Netmask: 11111111 11111111 11111111 00000000
255 255 255 0
+--------------------------+--------+
Network Host
</pre>
<p>
In other words, 192.168.0.14 is still part of our example network, but
192.168.1.2 is not.
</p>
<p>
The <e>broadcast</e> address is an IP-address with the same network-part
as your network, but with only ones as host-part. Every host on your
network listens to this IP address. It is truly meant for broadcasting
packets.
</p>
<pre caption="Broadcast address">
IP-address: 192 168 0 2
11000000 10101000 00000000 00000010
Broadcast: 11000000 10101000 00000000 11111111
192 168 0 255
+--------------------------+--------+
Network Host
</pre>
<p>
To be able to surf on the internet, you must know which host shares the
Internet connection. This host is called the <e>gateway</e>. Since it is
a regular host, it has a regular IP address (for instance 192.168.0.1).
</p>
<p>
We previously stated that every host has its own IP address. To be able
to reach this host by a name (instead of an IP address) you need a
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP
address (such as <e>64.5.62.82</e>). Such a service is called a name
service. To use such a service, you must define the necessary <e>name
servers</e> in <path>/etc/resolv.conf</path>.
</p>
<p>
In some cases, your gateway also serves as nameserver. Otherwise you
will have to enter the nameservers provided by your ISP.
</p>
<p>
To summarise, you will need the following information before continuing:
</p>
<table>
<tr>
<th>Network Item</th>
<th>Example</th>
</tr>
<tr>
<ti>Your IP address</ti>
<ti>192.168.0.2</ti>
</tr>
<tr>
<ti>Netmask</ti>
<ti>255.255.255.0</ti>
</tr>
<tr>
<ti>Broadcast</ti>
<ti>192.168.0.255</ti>
</tr>
<tr>
<ti>Gateway</ti>
<ti>192.168.0.1</ti>
</tr>
<tr>
<ti>Nameserver(s)</ti>
<ti>195.130.130.5, 195.130.130.133</ti>
</tr>
</table>
</body>
</subsection>
<subsection id="ifconfig_route">
<title>Using ifconfig and route</title>
<body>
<p>
Setting up your network consists of three steps. First we assign
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to
the gateway using <c>route</c>. Then we finish up by placing the
nameserver IPs in <path>/etc/resolv.conf</path>.
</p>
<p>
To assign an IP address, you will need your IP address, broadcast
address and netmask. Then execute the following command, substituting
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your
broadcast address and <c>${NETMASK}</c> with your netmask:
</p>
<pre caption="Using ifconfig">
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i>
</pre>
<p>
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with
your gateway IP address:
</p>
<pre caption="Using route">
# <i>route add default gw ${GATEWAY}</i>
</pre>
<p>
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our
example, we use <c>nano</c>):
</p>
<pre caption="Creating /etc/resolv.conf">
# <i>nano -w /etc/resolv.conf</i>
</pre>
<p>
Now fill in your nameserver(s) using the following as a template. Make
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with
the appropriate nameserver addresses:
</p>
<pre caption="/etc/resolv.conf template">
nameserver ${NAMESERVER1}
nameserver ${NAMESERVER2}
</pre>
<p>
That's it. Now test your network by pinging some Internet server (like
<uri link="http://www.google.com">Google</uri>). If this works,
congratulations then. You are now ready to install Gentoo. Continue with <uri
link="?part=1&chap=4">Preparing the Disks</uri>.
</p>
</body>
</subsection>
</section>
</sections>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-02-10 17:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-09 19:17 [gentoo-doc-cvs] cvs commit: hb-install-x86-about.xml Shyam Mani
-- strict thread matches above, loose matches on Subject: below --
2006-02-10 17:12 Shyam Mani
2006-02-10 17:46 Shyam Mani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox