nightmorph 07/03/31 04:35:16
Modified: hb-install-alpha-bootloader.xml
hb-install-alpha-kernel.xml
hb-install-alpha-medium.xml
Log:
alpha done
Revision Changes Path
1.2
xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml?rev=1.2&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml?rev=1.2&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml?r1=1.1&r2=1.2
Index: hb-install-alpha-bootloader.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-alpha-bootloader.xml 19 Mar 2007 20:37:28 -0000 1.1
+++ hb-install-alpha-bootloader.xml 31 Mar 2007 04:35:16 -0000 1.2
@@ -4,11 +4,11 @@
<!-- 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/2007.0/hb-install-alpha-bootloader.xml,v
1.1 2007/03/19 20:37:28 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml,v
1.2 2007/03/31 04:35:16 nightmorph Exp $ -->
<sections>
-<version>7.0</version>
+<version>8.0</version>
<date>2006-08-30</date>
<section>
1.2
xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml?rev=1.2&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml?rev=1.2&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml?r1=1.1&r2=1.2
Index: hb-install-alpha-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-alpha-kernel.xml 19 Mar 2007 20:37:28 -0000 1.1
+++ hb-install-alpha-kernel.xml 31 Mar 2007 04:35:16 -0000 1.2
@@ -4,11 +4,11 @@
<!-- 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/2007.0/hb-install-alpha-kernel.xml,v
1.1 2007/03/19 20:37:28 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml,v
1.2 2007/03/31 04:35:16 nightmorph Exp $ -->
<sections>
-<version>7.2</version>
+<version>8.0</version>
<date>2007-03-12</date>
<section>
@@ -17,8 +17,8 @@
<p>
You first need to select your timezone so that your system knows where it is
-located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
-it to <path>/etc/localtime</path>. Please avoid the
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8.
</p>
@@ -26,7 +26,8 @@
<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
</pre>
</body>
@@ -46,36 +47,37 @@
</p>
<p>
-For alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel
source).
+For alpha-based systems we have <c>gentoo-sources</c> (the default 2.6 kernel
+source).
</p>
<pre caption="Installing a kernel source">
-# <i>emerge vanilla-sources</i>
+# <i>emerge gentoo-sources</i>
</pre>
<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>vanilla-sources-2.6.16.19</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
+Your version may be different, so keep this in mind.
</p>
<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux ->
linux-2.6.16.19
+lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux ->
linux-<keyval id="kernel-version"/>
</pre>
<p>
-Now it is time to configure and compile your kernel source. You
-can use <c>genkernel</c> for this, which will build a generic kernel as used
-by the Installation CD. We explain the "manual" configuration first though, as
it is
+Now it is time to configure and compile your kernel source. You can use
+<c>genkernel</c> for this, which will build a generic kernel as used by the
+Installation CD. We explain the "manual" configuration first though, as it is
the best way to optimize your environment.
</p>
<p>
If you want to manually configure your kernel, continue now with <uri
-link="#manual">Default: Manual Configuration</uri>. If you want to use
-<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
+link="#manual">Default: Manual Configuration</uri>. If you want to use
+<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
genkernel</uri> instead.
</p>
@@ -131,25 +133,18 @@
<pre caption="Selecting experimental code/drivers">
Code maturity level options --->
[*] Prompt for development and/or incomplete code/drivers
+General setup --->
+ [*] Support for hot-pluggable devices
</pre>
<p>
Now go to <c>File Systems</c> and select support for the filesystems you use.
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
-able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc
-file system</c>, (<c>/dev file system</c> + <c>Automatically mount at boot</c>
only for 2.4 kernel):
+able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
+file system</c>.
</p>
<pre caption="Selecting necessary file systems">
-<comment>(With a 2.4.x kernel)</comment>
-File systems --->
- [*] Virtual memory file system support (former shm fs)
- [*] /proc file system support
- [*] /dev file system support (EXPERIMENTAL)
- [*] Automatically mount at boot
- [ ] /dev/pts file system for Unix98 PTYs
-
-<comment>(With a 2.6.x kernel)</comment>
File systems --->
Pseudo Filesystems --->
[*] /proc file system support
@@ -169,13 +164,6 @@
</p>
<pre caption="Selecting PPPoE necessary drivers">
-<comment>(With a 2.4.x kernel)</comment>
-Network device support --->
- <*> PPP (point-to-point protocol) support
- <*> PPP support for async serial ports
- <*> PPP support for sync tty ports
-
-<comment>(With a 2.6.x kernel)</comment>
Device Drivers --->
Networking support --->
<*> PPP (point-to-point protocol) support
@@ -269,13 +257,7 @@
</p>
<pre caption="Compiling the kernel">
-<comment>(For 2.4 kernel)</comment>
-# <i>make dep && make vmlinux modules modules_install</i>
-
-<comment>(For 2.6 kernel)</comment>
# <i>make && make modules_install</i>
-
-<comment>(For all kernels)</comment>
# <i>make boot</i>
</pre>
@@ -307,14 +289,15 @@
</p>
<p>
-Now that your kernel source tree is installed, it's now time to compile your
-kernel by using our <c>genkernel</c> script to automatically build a kernel
for
-you. <c>genkernel</c> works by configuring a kernel nearly identically to the
-way our Installation CD kernel is configured. This means that when you use
-<c>genkernel</c> to build your kernel, your system will generally detect all
-your hardware at boot-time, just like our Installation CD does. Because
genkernel
-doesn't require any manual kernel configuration, it is an ideal solution for
-those users who may not be comfortable compiling their own kernels.
+Now that your kernel source tree is installed, it's now time to compile your
+kernel by using our <c>genkernel</c> script to automatically build a kernel for
+you. <c>genkernel</c> works by configuring a kernel nearly identically to the
+way our Installation CD kernel is configured. This means that when you use
+<c>genkernel</c> to build your kernel, your system will generally detect all
+your hardware at boot-time, just like our Installation CD does. Because
+genkernel doesn't require any manual kernel configuration, it is an ideal
+solution for those users who may not be comfortable compiling their own
+kernels.
</p>
<p>
@@ -339,42 +322,17 @@
</p>
<pre caption="Running genkernel">
-* Gentoo Linux Genkernel; Version 3.4.0
-* Running with options: all
-
-* Linux Kernel 2.6.16.19 for alpha...
-* kernel: >> Running mrproper...
# <i>genkernel all</i>
-<comment>(Output removed to increase readability)</comment>
-* Kernel compiled successfully!
-*
-* Required Kernel Parameters:
-* real_root=/dev/$ROOT
-*
-* Where $ROOT is the device node for your root partition as the
-* one specified in /etc/fstab
-*
-* If you require Genkernel's hardware detection features; you MUST
-* tell your bootloader to use the provided INITRAMFS file. Otherwise;
-* substitute the root argument for the real_root argument if you are
-* not planning to use the initrd...
-
-* WARNING... WARNING... WARNING...
-* Additional kernel cmdline arguments that *may* be required to boot
properly...
-* Do NOT report kernel bugs as genkernel bugs unless your bug
-* is about the default genkernel configuration...
-*
-* Make sure you have the latest genkernel before reporting bugs.
</pre>
<p>
-Once <c>genkernel</c> completes, a kernel, full set of modules and
-<e>initial root disk</e> (initrd) will be created. We will use the kernel
-and initrd when configuring a boot loader later in this document. Write
-down the names of the kernel and initrd as you will need it when writing
-the bootloader configuration file. The initrd will be started immediately
after
-booting to perform hardware autodetection (just like on the Installation CD)
before
-your "real" system starts up.
+Once <c>genkernel</c> completes, a kernel, full set of modules and <e>initial
+root disk</e> (initrd) will be created. We will use the kernel and initrd when
+configuring a boot loader later in this document. Write down the names of the
+kernel and initrd as you will need it when writing the bootloader configuration
+file. The initrd will be started immediately after booting to perform hardware
+autodetection (just like on the Installation CD) before your "real" system
+starts up.
</p>
<pre caption="Checking the created kernel image name and initrd">
@@ -386,55 +344,13 @@
<section id="kernel_modules">
<title>Installing Separate Kernel Modules</title>
<subsection>
-<title>Installing Extra Modules</title>
-<body>
-
-<p>
-If appropriate, you should emerge ebuilds for any additional hardware that is
-on your system. Here is a list of kernel-related ebuilds that you could emerge:
-</p>
-
-<table>
-<tcolumn width="1in"/>
-<tcolumn width="4in"/>
-<tcolumn width="2in"/>
-<tr>
- <th>Ebuild</th>
- <th>Purpose</th>
- <th>Command</th>
-</tr>
-<tr>
- <ti>x11-drm</ti>
- <ti>
- Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and
- other cards for xorg-x11. Please check the <c>IUSE_VIDEO_CARDS</c> variable
- in the <path>/usr/portage/x11-base/x11-drm</path> ebuilds to see what you
- need to fill in as <c>yourcard</c>.
- </ti>
- <ti><c>VIDEO_CARDS="yourcard" emerge x11-drm</c></ti>
-</tr>
-</table>
-
-<p>
-Beware though, some of these ebuilds might deal with big dependencies. To
verify
-what packages will be installed by emerging an ebuild, use <c>emerge
---pretend</c>. For instance, for the <c>x11-drm</c> package:
-</p>
-
-<pre caption="View full installation package listing">
-# <i>emerge --pretend x11-drm</i>
-</pre>
-
-</body>
-</subsection>
-<subsection>
<title>Configuring the Modules</title>
<body>
<p>
-You should list the modules you want automatically loaded in
-<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>).
-You can add extra options to the modules too if you want.
+You should list the modules you want automatically loaded in
+<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
+the modules too if you want.
</p>
<p>
@@ -449,16 +365,14 @@
<p>
For instance, to automatically load the <c>3c59x.o</c> module, edit the
-<path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module
-name in it.
+<path>kernel-2.6</path> file and enter the module name in it.
</p>
-<pre caption="Editing /etc/modules.autoload.d/kernel-2.4">
-<comment>(Example for 2.4 kernels)</comment>
-# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i>
+<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
+# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
</pre>
-<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
+<pre caption="/etc/modules.autoload.d/kernel-2.6">
3c59x
</pre>
1.3
xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml?rev=1.3&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml?rev=1.3&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml?r1=1.2&r2=1.3
Index: hb-install-alpha-medium.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hb-install-alpha-medium.xml 20 Mar 2007 05:31:13 -0000 1.2
+++ hb-install-alpha-medium.xml 31 Mar 2007 04:35:16 -0000 1.3
@@ -4,11 +4,11 @@
<!-- 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/2007.0/hb-install-alpha-medium.xml,v
1.2 2007/03/20 05:31:13 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml,v
1.3 2007/03/31 04:35:16 nightmorph Exp $ -->
<sections>
-<version>7.0</version>
+<version>8.0</version>
<date>2006-08-30</date>
<section>
@@ -109,6 +109,26 @@
</body>
</subsection>
+<subsection>
+<title>Other CDs</title>
+<body>
+
+<p>
+You might find a Package CD on one of our mirrors. This CD is not an
+Installation CD but an additional resource that can be exploited during a
+networkless installation. It contains prebuilt packages (also known as the GRP
+set) that allow you to easily and quickly install additional applications
+(such as OpenOffice.org, KDE, GNOME, ...) immediately after the networkless
+Gentoo installation.
+</p>
+
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage3 tarball you use.
+</p>
+
+</body>
+</subsection>
</section>
<!-- STOP -->
<section>
@@ -119,8 +139,8 @@
<p>
You can download the Universal Installation CD from one of our <uri
-link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in
-the <path>releases/alpha/2007.0/installcd</path> directory.
+link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in
the
+<path><keyval id="release-dir"/>installcd</path> directory.
</p>
<p>
@@ -190,17 +210,17 @@
<p>
When your Alpha is powered on, the first thing that gets started is the
firmware. It is loosely synonymous with the BIOS software on PC systems. There
-are two types of firmware on Alpha systems: SRM (<e>Systems Reference
+are two types of firmware on Alpha systems: SRM (<e>Systems Reference
Manual</e>) and ARC (<e>Advanced Risc Console</e>).
</p>
<p>
SRM is based on the Alpha Console Subsystem specification, which provides an
operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. ARC
-is based on the Advanced RISC Computing (ARC) specification, which provides
-an operating environment for Windows NT. You can find a
-<uri link="http://www.alphalinux.org/faq/SRM-HOWTO/";>detailed guide</uri> on
-using SRM over at the Alpha Linux website.
+is based on the Advanced RISC Computing (ARC) specification, which provides an
+operating environment for Windows NT. You can find a <uri
+link="http://www.alphalinux.org/faq/SRM-HOWTO/";>detailed guide</uri> on using
+SRM over at the Alpha Linux website.
</p>
<p>
@@ -212,20 +232,13 @@
</p>
<p>
-Now to boot an Alpha Installation CD, put the CD-ROM in the tray and reboot
the system.
-You can use SRM to boot the Installation CD. If you cannot do that, you will
have to use
-<c>MILO</c>. If you don't have <c>MILO</c> installed already, use one of the
-precompiled <c>MILO</c> images available on <uri
+Now to boot an Alpha Installation CD, put the CD-ROM in the tray and reboot the
+system. You can use SRM to boot the Installation CD. If you cannot do that,
you
+will have to use <c>MILO</c>. If you don't have <c>MILO</c> installed already,
+use one of the precompiled <c>MILO</c> images available on <uri
link="http://dev.gentoo.org/~taviso/milo/";>taviso's homepage</uri>.
</p>
-<p>
-This release also includes two entries for people who want to use a serial
-console during the installation, possibly boxes with no keyboard and screen
-attached. One allows you to boot 2.6 using the serial console and the other
will
-do the same with our 2.4 kernel.
-</p>
-
<pre caption="Booting a CD-ROM using SRM">
<comment>(List available hardware drives)</comment>
>>> <i>show device</i>
@@ -233,25 +246,16 @@
<comment>(...)</comment>
<comment>(Substitute dkb0 with your CD-ROM drive device)</comment>
>>> <i>boot dkb0 -flags 0</i>
-<comment>(To boot the 2.4 kernel instead of the default 2.6 kernel
use:)</comment>
->>> <i>boot dkb -flags 1</i>
+
<comment>(If you need serial console support)</comment>
-<comment>(To boot the 2.6 kernel with serial console support use:)</comment>
>>> <i>boot dkb0 -flags 2</i>
-<comment>(To boot the 2.4 kernel with serial console support use:)</comment>
->>> <i>boot dkb0 -flags 3</i>
</pre>
<pre caption="Booting a CD-ROM using MILO">
<comment>(Substitute hdb with your CD-ROM drive device)</comment>
MILO> <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz
root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i>
-<comment>(To boot the 2.4 kernel instead of the default 2.6 kernel
use:)</comment>
-MILO> <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz
root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i>
<comment>(If you need serial console support)</comment>
-<comment>(To boot the 2.6 kernel with serial console support use:)</comment>
MILO> <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz
root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs console=ttyS0</i>
-<comment>(To boot the 2.4 kernel with serial console support use:)</comment>
-MILO> <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz
root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs console=ttyS0
cdroot</i>
</pre>
<p>
@@ -272,11 +276,11 @@
<p>
When the Installation CD boots, it tries to detect all your hardware devices
and
-loads the appropriate kernel modules to support your hardware. In the
-vast majority of cases, it does a very good job. However, in some cases (the
-SPARC Installation CDs don't even do autodetection), 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.
+loads the appropriate kernel modules 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. If the PCI auto-detection missed some of
+your system's hardware, you will have to load the appropriate kernel modules
+manually.
</p>
<p>
@@ -288,14 +292,6 @@
# <i>modprobe 8139too</i>
</pre>
-<p>
-If you need PCMCIA support, you should start the <c>pcmcia</c> init script:
-</p>
-
-<pre caption="Starting the PCMCIA init script">
-# <i>/etc/init.d/pcmcia start</i>
-</pre>
-
</body>
</subsection>
<subsection>
--
[email protected] mailing list
