[Lunar-commits] r15735 - lunar-doc/trunk/lunar-manual
Auke Kok
sofar at lunar-linux.org
Wed Jul 13 12:04:42 UTC 2005
Author: sofar
Date: 2005-07-13 12:04:41 +0000 (Wed, 13 Jul 2005)
New Revision: 15735
Modified:
lunar-doc/trunk/lunar-manual/installation.tex
Log:
Rewritten this entire chapter, mostly 1) removing obsolete information regarding the installer 2) debunking myths about some things. Lots of small textual changes and style changes as well.
Modified: lunar-doc/trunk/lunar-manual/installation.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/installation.tex 2005-07-13 10:08:17 UTC (rev 15734)
+++ lunar-doc/trunk/lunar-manual/installation.tex 2005-07-13 12:04:41 UTC (rev 15735)
@@ -1,27 +1,24 @@
\chapter{Installation of Lunar Linux}
+
\includegraphics[scale=0.2]{./image/logo.eps}
- is a linux distribution in that it is not binary based, as are most distributions, but is instead built entirely by compiling sourcecode, using your own custom optimizations. Essentially, it installs a complete bootstrap development system on your machine, and then you tell the Lunar package manager what tools you want, and it builds the entire system by downloading current source code and locally compiling an optimized system tailored toward your specific needs.\par
+ is a linux distribution that is not binary\footnote{a "binary" is a machinecode or bytecode program that implements a program for a specific processor architecture.} based, as most distributions are, but instead is built entirely by compiling sourcecode, using your own custom optimizations. The Lunar-Linux installer essentially installs a basic development system on your machine. From there on you can install (compile) with the Lunar package manager what programs you wish to use. Lunar-Linux builds the entire system by downloading current source code from the original authors pubished location and locally compiles an optimizes the package tailored towards your specific needs.\par
-The result is a leaner, meaner, refreshingly uncluttered, and strikingly faster operating system than most linux distributions.\par
+The result is a highly specialised, clean, and often more fast and stable operating system than most linux distributions.\par
+This Chapter of the book is meant to guide you through the installation process as painlessly as possible. It assumes that you have some experience with Linux or other Unix variants, and have a general idea of what you are doing. If you are unfamiliar with such things as partitions, or have never used linux before, Lunar may not be the best introduction for you into the world of open source.\par
+Take a look at Chapter \ref{comty} to see how you can contact the community for help.\par
-This Chapter of the book is meant to guide you through the installation process as painlessly as possible. It assumes that you have some experience with linux or another Unix variant, and have a general idea of what you are doing. If you are unfamiliar with such things as partitions, or have never used linux before, Lunar may not be the best introduction for you into the world of open source.
-Take a look at Chapter \ref{comty} to see, how you can contact the community for help.
-With that said, we hope you enjoy using Lunar!\par
-
-
\section{Getting the ISO}
-The primary site for retrieving the ISO is \textit{ lunar-linux.org }. There, under \textit{Downloads} you will find links to our US, EU, and Internet2 mirrors, as well as a Bittorrent link. As of this writing, the current version of the Lunar ISO is version 1.5.0.\par
+The primary site for retrieving the ISO is \textit{ http://lunar-linux.org/ }. There, under \textit{Downloads} you will find links to our mirrors, as well as a Bittorrent\footnote{Bittorrent (\textit{http://bittorrent.org/}) is a P2P protocol well suited for distributing large files} link. As of this writing, the current version of the Lunar ISO is version 1.5.0.\par
-Locate and retrieve the file lunar-1.5.0.iso.bz2. After downloading this file, you will need to unpack the ISO using bzip2. Windows users may need a program like WinZip. Mac should unzip the file by itself. Then all that is left to do is use your favorite program to burn the ISO to a cdrom and begin the installation. \par
+Locate and retrieve the file lunar-1.5.0.iso.bz2. After downloading this file, you will need to unpack the ISO using bzip2. Windows users may need a program like WinZip or winrar. Mac users should be able to unzip the file without additional software. Then all that is left to do is use your favorite program to burn the ISO to a cdrom and begin the installation.\par
-It should be noted that this ISO and Lunar use devfs for device management. \par
+We are assuming the you are installing Lunar as your primary OS. Make sure you have a backup of any important data that you need to retain. The Lunar-Linux Project and its developers are not responsible in any way for any loss of data on your system! Lunar-Linux comes with absolutely no warranty!\par
-We are assuming the you are installing Lunar as your primary OS. Make sure you have a backup of any important data that you need to retain. The Lunar Linux Project and its developers are not responsible in any way for any loss of data on your system!\par
-For installation parallel to an other OS like Micro\$oft Windows, install it first, but leave unpatitioned space for Lunar. Refer to the bootloader section \ref{bootl} in this chapter to see, how you can integrate it to your boot menu. This way Windows will be installed on the first partition of your disk. If you install on different disks things get more complicated. You need to install the bootloader on the first disk, from which your box boots. Ask the community if you need help: Chapter \ref{comty} \par
+For installation parallel to an other OS like Micro\$oft Windows, install it first, but leave plenty of unpatitioned space for Lunar. Refer to the bootloader section \ref{bootl} in this chapter to see how you can integrate it to your boot menu. Windows should be installed on the first primary partition of your harddisk. If you install on different disks things get more complicated. You need to install the bootloader on the first disk, from which your system boots. Ask the community if you need help: Chapter \ref{comty}.\par
\section{Booting the ISO}
@@ -33,10 +30,12 @@
\caption{Boot Menu}
\end{figure}
-Upon booting the ISO, the first thing you will see are options for booting the ISO kernel, or for performing RAM tests. For people who need to load extra modules for example for IDE or SCSI devices. There is even a safe mode which will disable DMA, MTRR, RAID, LVM, USB keyboards, NTFS, HPFS, Advanced Partitions, and Firewire. For more extensive help on each point you can press \textit{ F1} to \textit{F4}.
+Upon booting the ISO, the first thing you will see are options for booting the ISO kernel, or for performing RAM tests. For people who need to load extra modules for example for IDE or SCSI devices. There is even a safe mode which will disable possibly dangerous drivers and features for DMA, MTRR, RAID, LVM, USB keyboards, NTFS, HPFS, Advanced Partitions, and Firewire. For more extensive help on each point you can press \textit{F1} to \textit{F4}.
-Most folks, however, will be just fine pressing enter at the boot prompt and loading the default kernel. The kernel will ask you for other resolutions to display the console in. Again you will run savely with just pressing \textit{space } \par
+Most folks, however, will be just fine pressing enter at the boot prompt and loading the default kernel. The kernel will ask you for other resolutions to display the console in. Again you will run savely with just pressing \textit{space}.\par
+If you have a need to load special IDE or SCSI drivers, type \textit{linux} and use the initrd menu to load more modules before continuing to the installer.\par
+
\begin{figure}
\begin{center}
\includegraphics[angle=270,width=0.8\textwidth]{./image/install2.eps}
@@ -44,13 +43,14 @@
\caption{Welcome to the Lunar Linux Installer}
\end{figure}
-After loading the kernel, you will be presented the Lunar Linux installer. It will guide you through the rest of the setup process. By pressing \textit{ I} or \textit{enter} you may read a short Introduction. The installer goes through 14 steps which can be navigated forward and backward by pressing the \textit{up} and \textit{down} button and \textit{enter}. You can navigate to the settings by pressing the \textit{left} and \textit{ right} arrow keys. Here one can shell out at any time of the installation process, as well as load more kernel modules and toggle the behaviour of the guided menu. \par
+After loading the kernel, you will be presented the Lunar Linux installer. It will guide you through the rest of the setup process. By pressing \textit{I} and \textit{enter} you can read a short Introduction and last-minute information and help on the installer. The installer goes through 14 steps which can be navigated forward and backward by pressing the \textit{up} and \textit{down} button and \textit{enter}. You can navigate to the settings by pressing the \textit{left} and \textit{right} arrow keys so that the \textit{settings} button is selected and pressing \textit{enter}. Here one can shell out at any time of the installation process, as well as load more kernel modules and adjust the behaviour of the guided menu.\par
-To come to the next step press \textit{down} and \textit{enter} at the first screen.
+To go to the next step press \textit{down} and \textit{enter} at the first screen.\par
+
\section{Customization Settings}
-We now have some customization settings to configure. You can choose keyboard map, console font and global language. \par
+The first step of the installation is to select a special language, consolefont, or keyboard map. These settings might be needed to allow you to work using a non-english keyboard or font set (think greek or russian, or dvorak keyboards).\par
\begin{figure}
\begin{center}
@@ -59,25 +59,30 @@
\caption{Localise your Lunar Linux}
\end{figure}
-When u made a selection the menu point will change its color to green. In the keyboard map choose the one apropriate for you. Most americans will need \textit{us} while germans may need \textit{de} and danish people \textit{dk}. The language setting should explain itself ;) %console font ?? wtf should one choose ? this is really cryptic for me.
+When you have made a selection the menu entry will change its color to green to signify that you already completed this part of the installer. You don't have to complete all entries to finish installation though.\par
-You will also need to choose an editor, as you are going to need one later on in the installation for setting up your lilo or grub configuration. The six choices available are \lstinline{vi}, \lstinline{joe}, \lstinline{nano}, \lstinline{e3}, \lstinline{emacs} and \lstinline{zile}. If you have never used a text editor in linux before, \lstinline{nano} is the best choice for you. If you skip the Native Language Support option, the system will install the default editor, \lstinline{nano} for you. Now press \textit{F} to get one step forward. \par
+Most americans and west-europeans don't need to change the keymap, or can use \textit{us}, while germans may need \textit{de} and danish people \textit{dk}\footnote{us, de, dk: These codes are ISO language codes, not country codes}. The language setting works the same and should explain itself. Please note that the lunar installer is not available (yet) in different languages, but any application used by the lunar installer (such as the partitioning programs) will function in the selected language.\par
+The consolefont option is usefull for people who need additional characters or have a BIOS with ugly fonts. Most people do not bother with this option and leave it blank.\par
+
+You also need to choose an editor, as you are going to need one later on in the installation for setting up your lilo or grub configuration, and many other configuration files. The choices available include \lstinline{vi}, \lstinline{joe}, \lstinline{nano}, \lstinline{e3}, \lstinline{emacs} and \lstinline{zile}. If you have never used a text editor in linux before, \lstinline{nano} is the best choice for you. If you skip the Native Language Support option, the system will install the default editor, \lstinline{nano} for you. Now press \textit{F} to get one step forward.\par
+
+
\section{Setting Up Partitions}
-The next step is to set up partitions on your hard drive. Upon selecting the \lstinline"Partition Drive" option, you will be shown a list of all the discs the kernel has detected. If we assume that you have one hard drive connected via an IDE channel, which will show up in the menu as \lstinline"disc0". After selecting the disc to partition, you are given the option of using one of three partitioning programs. They are:
+The next step is to set up partitions on your hard drive. Upon selecting the \lstinline"Partition Drive" option, you will be shown a list of all the disks the kernel has detected. If we assume that you have one hard drive connected via an IDE channel, which will show up in the menu as \lstinline"/dev/hda". After selecting the disc to partition, you are given the option of using one of three partitioning programs. They are:\par
\begin{itemize}
\item \lstinline{cfdisk} -- A menu driven partitioner, and very easy to use. If you are unfamiliar with various partitioning programs, this is the best option for you.
-\item \lstinline{fdisk} -- Text based partitioner that requires a little more know-how than cfdisk. More experienced users will probably use this program. However new users should not be daunted, as it does have help offered at every step. You can leave by pressing \textit{q }and \textit{enter}
-\item \lstinline{parted} -- Text based partitioner that is good for advanced users. Parted is excellent for resizing current partitions on your hard disk, however be forewarned that resizing partitions is an excellent way to hose your entire disc.
+\item \lstinline{fdisk} -- Text based partitioner that requires a little more know-how than cfdisk. Experienced users will probably use this program. However new users should not be daunted, as it does have help offered at every step. You can leave by pressing \textit{q} and \textit{enter}.
+\item \lstinline{parted} -- Text based partitioner that is good for advanced users. Parted is excellent for resizing current partitions on your hard disk, however you should be warned that resizing partitions is an excellent way to destroy your entire disc.
\end{itemize}
-For our example, we have one 40GB IDE drive and we'll set up six partitions; /, /boot, /home, /usr, /var, and a swap partition. It's a good idea to keep certain directories, such as /var and /usr on separate partitions, as this can save you a lot of headache in the future incase your disk ever completely fails on you and you need to recover data (god forbid!). Also, when you have a separate /boot partition as we have in our example, you need to have your partitioning program mark that partion as active or bootable. In our example, if we were using \lstinline{fdisk}, you would press "a" at the command line, and then select part1 as the active partition.\par
+For our example, we have one 40GB IDE drive and we'll set up six partitions; \textit{/}, \textit{/boot}, \textit{/home}, \textit{/usr}, \textit{/var}, and a \textit{swap} partition. It's a good idea to keep certain directories, such as \textit{/var} and \textit{/usr} on separate partitions, as this can save you a lot of headache in the future incase your disk ever completely fails on you and you need to recover data (god forbid!). Also, when you have a separate \textit{/boot} partition as we have in our example, you might need to have your partitioning program mark that partion as active or bootable. In our example, if we were using \lstinline{fdisk}, you would press \textit{a} at the command line, and then select part1 as the active partition.\par
-If you are installing on a machine together with an other OS you perform these steps in the unpartitioned space and leave the other partitions untouched. For installation on different disks just choose the other disk (disc1 ... ) \par
+If you are installing on a machine together with an other OS you perform these steps in the unpartitioned space and leave the other partitions untouched. For installation on different disks just choose the other disk (\textit{/dev/hdb} ... )\par
-You might also want to install a /tmp partition. By default, Lunar will create a tempfs filesystem mounted on /tmp (tempfs minimizes filesystem fragmentation because it resides in volatile memory). This can be a good choice if you have a lot of memory on your machine. If memory is tight, we recommend creating a /tmp partition to minimize filesystem fragmentation.\par
+You might also want to install a \textit{/tmp} partition. By default, Lunar will create a \textit{tmpfs}\footnote{tmpfs is a temporary filesystem that resides completely in virtual memory, thus is destroyed on reboot} filesystem mounted on \textit{/tmp}. This can be a good choice if you have a lot of memory on your machine. If memory is tight, we recommend creating a \textit{/tmp} partition to minimize filesystem fragmentation.\par
\begin{figure}
\begin{center}
@@ -86,24 +91,24 @@
\caption{Partition Setup}
\end{figure}
-It is important to note that you can not mount the directories /etc, /bin, /sbin, /dev, /lib and /proc on separate partitions. These directories need to be contained within the root ("/") directory. The installation program should block you from doing this, but it's best not to try.\par
+It is important to note that you can not mount the directories \textit{/etc}, \textit{/bin}, \textit{/sbin}, \textit{/dev}, \textit{/lib} and \textit{/proc} on separate partitions. These directories must be present on the root filesystem in the root (\textit"/") directory. The installation program doesn't prevent you from doing this, but it's best not to try.\par
Here's our partition setup:\par
\begin{enumerate}
-\item /boot 100MB
-\item / 4GB
-\item swap 1GB
-\item /usr 10GB
-\item /var 10GB
-\item /home 15GB
+\item \textit{/boot 100MB}
+\item \textit{/ 4GB}
+\item \textit{swap 1GB}
+\item \textit{/usr 10GB}
+\item \textit{/var 10GB}
+\item \textit{/home 15GB}
\end{enumerate}
-In order for you to have more than four partitions on a single drive, the fourth partition is made into what is known as an extended or logical partition in which the fifth, sixth, and seventh (etc, etc) partitions reside. For our example above, if we were using fdisk, we would make the fourth partition an extended/logical partition that was 35GB, and then the fifth, sixth, and seventh partitions in our scheme resided within it. However, if we used cfdisk, we would just worry about creating six partitions, making sure that the first three are the primary type, and the last three logical.\par
+In order for you to have more than four partitions on a single drive, the fourth partition is made into what is known as an extended partition in which the fifth, sixth, and seventh (etc, etc) \textit"logical" partitions reside. For our example above, if we were using fdisk, we would make the fourth partition an extended partition that was 35GB, and then the fifth, sixth, and seventh logical partitions in our scheme resided within it. However, if we used cfdisk, we would just worry about creating six partitions, making sure that the first three are the primary type, and the last three logical.\par
Note that the names and mount points for these partitions will be assigned during the next step of this process, when you mount the partitions. Write down exactly what partitions you are planning to create because it can otherwise get confusing!\par
-Lunar offers two choices when it comes to swap. You can set up a swap partition, as we have in our example, or you can set up a swapfile in the root directory. We recommend setting up a swap partition, as you will get better performance with it than with the swapfile. However, there may be a need for you to set up the swapfile instead, which can be setup and activated after you have mounted your other partitions.\par
+Lunar offers two choices when it comes to swap. You can set up a swap partition, as we have in our example, or you can set up a swapfile in the root directory. There is no performance boost or loss from choosing either of them\footnote{swapfile vs partition debate: \textit{http://www.webservertalk.com/message1116071.html}}, but the biggest advantage of using a swapfile is that you can later adjust its size or reclaim the space. A swapfile created on a newly formatted file system is just as fast as a swap partition. If you create a swap file on a rather full filesystem (> 50\% full) it might lower performace dramatically. Lunar will setup your swap before it does anything else, so choosing a swapfile is a safe, fast and flexible option.\par
\section{Mounting Partitions and Creating Filesystems}
@@ -115,23 +120,27 @@
\caption{Creating one swap, one / and one /usr partition}
\end{figure}
-After setting up your partitions, you need to mount them and create file systems. Select the menu option "Select Target Partitions" and verify that you are indeed done creating partitions.\par
+After setting up your partitions, you need to mount them and possibly create file systems. Select the menu option "Select Target Partitions" and verify that you are indeed done creating partitions.\par
-The installer will warn you at this point that the root partition (as in "/", not "/root") needs to be mounted first. Select the disc that the root partition should be on. In our example, we are going to use \lstinline{disc0}. Our root partition is going to be on \lstinline{disc0/part2} then we select which filesystem we would like to use.\par
+It is good practice to select the root filesystem first (but not required anymore!). Select the partition that the root file system will be or is on. In our example, we are going to use \lstinline{/dev/hda}. Our root partition is going to be on \lstinline{/dev/hda2} and then we select which filesystem we would like to use.\par
+Here's a short description of the filesystems that Lunar supports and that you can choose to install on your partitions:\par
+
\begin{itemize}
- \item ext2 (Second Extended File System) -- Version 2 of the Extended File System, which was designed for linux as a replacement for the Minix Filesystem. Ext2 is not a journaled filesystem, which means that you'll need to perform disc recovery operations after a power failure or other such system crash. This filesystem is available with all kernels on the ISO.
- \item ext3 (Third Extended File System) -- Version 3 of the Extended File System, which is essentially just the journaled version of ext2. This filesystem is available with all kernels on the ISO.
- \item reiserfs (Reiser Filesystem) -- Journaled filesystem created by Hans Reiser that is excellent for use with extremely small files. This filesystem is available with all kernels on the ISO.
- \item jfs (Journaled File System) -- Created by IBM for AIX, IBM's brand of Unix, and later ported to linux by IBM under the GPL. A journaled filesystem that is very good at handling high throughput issues. This filesystem is available with all kernels on the ISO.
- \item xfs -- Created by SGI for IRIX, SGI's brand of Unix, and later ported to linux under the GPL. A journaled filesystem that SGI claims is better than any other at handling extremely large files and sparse files. This filesystem is only available with the lunar or grsec patched kernels, which we will come to in a few steps.
+ \item ext2 (Second Extended File System) -- Version 2 of the Extended File System, which was designed for linux as a replacement for the Minix Filesystem. Ext2 is not a journaled filesystem, which means that you'll need to perform disc recovery operations after a power failure or other such system crash.
+ \item ext3 (Third Extended File System) -- Version 3 of the Extended File System, which is essentially the journaled version of ext2.
+ \item reiserfs (Reiser Filesystem) -- Journaled filesystem created by Hans Reiser that is excellent for use with extremely small files.
+ \item jfs (Journalled File System) -- Created by IBM for AIX, IBM's brand of Unix, and later ported to linux by IBM under the GPL. A journaled filesystem that is very good at handling high throughput issues.
+ \item xfs -- Created by SGI for IRIX, SGI's brand of Unix, and later ported to linux under the GPL. A journaled filesystem that SGI claims is better than any other at handling extremely large files and sparse files.
\end{itemize}
-We recomment to use ext3 as your filesystem.\par
-After selecting the filesystem type you wish to use, you will be prompted through a series of steps to initialize the partition. You'll notice that the prompts are quite redundant in nature in order to be absolutely positive that you will not inadvertantly erase crucial data that you might have on a working filesystem. In addition, if you have more than four partitions, as we do in our example, you don't want to mount any file systems on the fourth partition, as it is the extended partition that houses the fifth, sixth (and so on) partitions.\par
+We recommend that you use ext3 as your filesystem. This may sound strange to a lot of people, but ext3 has proven itself to be the best default filesystem for everyone. When you are using your machine in a normal way (even servers) and you do not require special performance, ext3 will provide you with the best performance versus reliability (and data recovery options) possible. Only in special cases is it beneficial to choose another filesystem. As a sidenote: generally xfs and reiserfs are next best choices and suited better for processing large amounts of small files (reiserfs) or huge files (xfs). ext2 can sometimes be usefull for \textit{/tmp} as well. JFS is an uncommon choice.\par
-As we mentioned earlier, there is an option in the installation process to set up a swap file in the root partition instead of a swap partition as we have done in our example. The next option after mounting your filesystems is to set up the swap file if you so desire. If you have set up a swap partition already, as we have done, you can skip this step. Otherwise, you can set up your swap file here, and the only thing you need to tell the installer is how large you want the file to be.\par
+After selecting the filesystem type you wish to use, you will be prompted through a series of steps to initialize the partition. You'll notice that the prompts are quite redundant in nature in order to be absolutely positive that you will not inadvertantly erase crucial data that you might have on a working filesystem. In addition, if you have more than four partitions, as we do in our example, you don't want to mount any file systems on the fourth partition (the installer should prevent you from doing so), as it is the extended partition that houses the fifth, sixth (and so on) partitions.\par
+As we mentioned earlier, there is an option in the installation process to set up a swap file in the root partition instead of a swap partition as we have done in our example. The next option after mounting your filesystems is to set up the swap file if you so desire. If you have set up a swap partition already, as we have done, you can skip this step. Otherwise, you can set up your swap file here, and the only thing you need to tell the installer is how large you want the file to be. Common locations for a swapfile are either in the root (\textit"/") or in \textit{/var}/\par
+
+
\section{Transferring Lunar To Your Partitions}
\begin{figure}
@@ -141,12 +150,11 @@
\caption{Transfering Lunar Linux}
\end{figure}
-Next, we need to transfer the core Lunar system to the partitions that you now have created. Select \lstinline"Install Lunar", and the system will proceed to tansfer all of the neccessary files for you. Be forewarned that the /usr transfer can take some time, espescially on older or slower systems, so don't panic and think that your system has frozen. It's just doing its thing.\par
+Next, we need to transfer the base Lunar system to the partitions that you now have created. Select \lstinline"Install Lunar", and the system will proceed to format your filesystems, create swap, mount all filesystems and finally transfer all of the neccessary files for you. At the end of this process, several settings are transferred to your system (such as the language and keyboard settings) and your system is almost finished for work.\par
+\section{Setting Up Your Compiler Optimizations}
-\section{Setting Up Your GCC Architecture Optimizations}
-
\begin{figure}
\begin{center}
\includegraphics[angle=270,width=0.8\textwidth]{./image/install7.eps}
@@ -154,16 +162,17 @@
\caption{Optimisations and Bootloader}
\end{figure}
-We reached step 7 of 14, thats the half, so lets go on ...
-The architecture optimizations is a crucial step, since what you choose will make your system fly! However, it is important that you do not overdo it on you optimization settings, as certain selections can, in some instances, break code while compiling.\par
+We reached step 7 of 14, thats the half, so lets go on ...\par
-The first option wants to prevent you from overdoing the optimisations. It will hide all compiler flags that are known to cause big trougle. So if you leave it enabled your save.
+The architecture optimizations is an important step, since it decides how you wish to customize your system, such as for speed or size. However, it is important that you do not overdo it on you optimization settings, as certain selections can, in some instances, break code while compiling, resulting sometimes even in complete unusable systems.\par
-Now choose your preferred compiler. The default choice here is GCC 3.x, and is the preferred choice as GCC 2.x is no longer under development, and GCC 3.x is known to make compiled code run faster. For our example, we are going to use GCC 3.x.\par
+The first option will to prevent you from overdoing the optimizations. It will hide all compiler flags that are known to cause big trougle. So if you leave it enabled you are (most likely) safe. Even with this option set on, you might break your box so look closely at which options you choose.\par
+Now choose your preferred compiler. The default choice here is GCC 3.x, and is the preferred choice as GCC 2.x is no longer under development, and GCC 3.x is known to make compiled code run faster.\par
+
Next we have the platform selection. This question would seem to be rather silly, since our ISO only boots up on x86 systems, but we like to plan for the future. You'll want to say x86 here.\par
-Now we move onto the basic optimizations . As you can see, the options speak for themselves. Your choice depends on what your needs are. Most folks will want to use -O2 / faster here, as it is the wisest choice. More advanced users may want to use the -O3 / fastest option, but it's not for everyone. If you're short on disk space, you would take the -Os / Small option. \footnote{For example, we used -Os for the ISO as we were working within a fixed amount of disc space.} Those of you with older or slower systems that wouldn't be able to take advantage of faster optimizations may choose a more conservative setting like -O1 / fast . For our example system, we will choose -O2.\par
+Now we move onto the basic optimizations. As you can see, the options speak for themselves. Your choice depends on what your needs are. Most folks will want to use -O2 / faster here, as it is the wisest choice. More advanced users may want to use the -O3 / fastest option, but it's not for everyone. If you're short on disk space, you would take the -Os / Small option\footnote{-Os is often used to create ISO as to fit as much software on it as possible}. Those of you with older or slower systems that wouldn't be able to take advantage of faster optimizations may choose a more conservative setting like -O1 / fast . For our example system, we will choose -O2, which is the default of a new installation.\par
After choosing your basic optimization level, you'll need to tell the compiler what type of processor you have. This may seem unimportant, however the GCC 3.x compiler has ways of optimizing code for certain processors, even though they all may be x86 based. For example, GCC 3.x has certain optimizations it can perform on code for Pentium 4 machines, but not for Pentium 3. Our example machine is a Pentium 3, so we are going to select that.\par
@@ -171,7 +180,7 @@
Next are options for the C and C++ compiler, called -pipe. Very few people, if any, would need to turn off the -pipe option, so in our example we are going to leave them checked.\par
-Following that is the screen for linker options, where you will find that "-s Strip" has already been checked off. Very few people will want to uncheck this option, so we will leave this screen as is. After that, we have some addons for compiler caching and distributed compiler support. Most folks will not need either one of these\par
+Following that is the screen for linker options, where you will find that "-s Strip" has already been checked off. Very few people will want to uncheck this option, so we will leave this screen as is. After that, we have some addons for compiler caching and distributed compiler support. Most folks will not need either one of these.\par
\subsection{Adding Additional GCC Optimizations}
@@ -186,9 +195,9 @@
Here we state the more riskier optimisations. If you are new to whole thing and dont know \textbf{exactly} what you doing leave them as they are. There are too many to go into much detail here, but suffice to say that you should choose carefully. As we mentioned in the prior section, certain optimizations will cause compilation errors or even failures. An optimization such as "-ffast-math" is very risky because it breaks certain rules to get faster code, and would only be used by the bravest of souls looking to endure lots of pain. More information about GCC 3.x optimization strings can be found on the gnu.org website. \par
-Some options involves setting up the number of concurrent makes and stack parameters. As the hint mentions on the "Concurrent Makes" screen, you'll want to enter in the number of cpu's your machine has. Unless you have a machine with more than one processor, you'll want to leave this field blank. The stack parameters is also fairly straightforward. The warning on that screen says that this field is best left empty, and so that is exactly what we will do with our example. \par
+Some options involves setting up the number of concurrent makes and stack parameters. As the hint mentions on the "Concurrent Makes" screen, you'll want to enter in the number of cpu's your machine has. Unless you have a machine with more than one processor or HyperThreading, you'll want to leave this field blank. The stack parameters is also fairly straightforward. The warning on that screen says that this field is best left empty, and so that is exactly what we will do with our example. \par
-We are now finished setting up our GCC optimizations! When you have you lunar system up and running, you can always change and tweak these GCC settings by typing \lstinline"lunar" at the commandline prompt, and going to \lstinline"Optimization Settings". In addition, if you aren't that familiar with what your processor is capable of using for optimizations, you can go to the shell out option on the ISO and type
+We are now finished setting up our GCC optimizations! When you have you lunar system up and running, you can always change and tweak these GCC settings by typing \lstinline"lunar optimize" at the commandline prompt. In addition, if you aren't that familiar with what your processor is capable of using for optimizations, you can go to the shell out option on the ISO and type
\begin{lstlisting}
@@ -196,10 +205,10 @@
\end{lstlisting}
-at the prompt and the system will show you all the optimizations that the processor reports it can handle.\par
-Now we can install the bootloader Package. Lunar offers you three choices: Lilo, Grub and None. Most people would want to choose Lilo, as it is easy to install, the configuration will take place after the kernel installation. \par
-\textbf{Note}: At the moment, lilo fails to build on 2.6 kernels. That mean, if you consider to switch to Kernel 2.6 later, its wise to choose grub. See Section \ref{lilo2grub} to get a introduction, if you are familiar only with lilo.
+at the prompt and the system will show you all the optimizations that the processor reports it can handle.\par
+Now we can install the bootloader Package. Lunar offers you three choices: Lilo, Grub and None. Most people would want to choose Lilo, as it is easy to install, the configuration will take place after the kernel installation. Lunar automatically creates the proper configuration file for these bootloaders.\par
+
\section{Building Your Customized Linux Kernel}
\begin{figure}
@@ -217,23 +226,22 @@
\item Never build filesystems or core components as modules! Make sure that whatever filesystems you decided to use for your partitions earlier are built into the kernel, and are not separate modules. Likewise, make sure that certain crucial things like ide and scsi drivers are not modules, as this will make your machine unbootable. (This rule doesn't apply to the scsi low level drivers though; they can be modules.) Modules are kernel drivers that can be manually activated and deactivated after the system has been booted, but not during boot time. The kernel from the ISO already has all the filesystems available during the installation built into the kernel, so if you don't change anything there, you will be fine.
\end{itemize}
-There are serveral kernels for you to choose from. They are:
-%someone take a close look at these specs !!
+There are serveral kernels for you to choose from. They are:\par
\begin{itemize}
-\item Linux 2.4 -- The default kernel for Lunar which is the Linus tree with some handy patches for the xfs filesystem, firewire, ext3, and several other fixes.
+\item Linux 2.4 -- The default kernel for Lunar which is the Linus tree with extra patches for functionality\footnote{supermount, automount, filesystem ACL extensions} and several small fixes.
\item Linux-2.4-stable -- The Linux kernel with only crucial fixes.
-\item Linux-2.4-vanilla -- This is the Linus tree with only critical patches for certain drivers that were created after the 2.4.29 kernel was released.
-\item Linux-2.4-grsec -- This is almost the same as Linux 2.4, but with grsecurity, cpu frequency scaling, gcc 3.x architecture types, and crypto support.
-\item Linux-2.4-agr -- The aggressive patch includes everything from the standard patchset as well as the low latency, pre-emptive, and gcc 3.x architecture type patches.
-\item Linux-2.4-om --A Kernel for OpenMosix clustering %gimme more info
+\item Linux-2.4-vanilla -- This is the official 2.4 tree with no patches at all.
+\item Linux-2.4-grsec -- This is the same as linux-2.4 with grsecurity and extra crypto support.
+\item Linux-2.4-agr -- The same as linux-2.4 as well as the low latency, pre-emptive scheduler, and gcc 3.x architecture type patches.
+\item Linux-2.4-om -- The same as linux-2.4 as well as the OpenMosix Transparent Process Migration patch\footnote{OpenMosix is a project that creates a virtual SMP machine out of several computers, allowing jobs to move to unused machines, creating a parallel computing supercomputer}
\end{itemize}
-For our example, we are going to use linux with the aggressive patchset (Linux-2.4-agr). \par
+For our example, we are going to use linux with the aggressive patchset (linux-2.4-agr). \par
The final question before you begin is which type of configuration method you would like to use.\par
\begin{itemize}
-\item \lstinline{config} -- The original way to configure the linux kernel. It is completely text based, and assumes you know what everything is. Unless you've been using linux since its inception, you probably don't want to use this method.
+\item \lstinline{config} -- The original way to configure the linux kernel. It is completely text based, and assumes you know what everything is. Unless you've been using linux since its inception, you probably don't want to use this method.
\item \lstinline{menuconfig} -- As the name implies, a menu driven version of the kernel configuration. This is the easiest, and by far the most popular way of configurating your kernel.
\item \lstinline{xconfig} -- If you have an X server running, you can use this option to configure your kernel using a nifty GUI interface. You won't be able to use this on the ISO, but once your system is up and running with X, you can use this option. If you do choose this option while installing from the ISO, the system will fall back to next available configuration method, in this case menuconfig, so there is no harm in selecting it if you do.
\end{itemize}
@@ -245,25 +253,20 @@
\subsection{Lilo}
-If you chose to use lilo and also said yes to automatically configuring and running lilo, then most of the work is done for you. If you chose not to hand edit lilo.conf, however, be warned that the default configuration has the system set up to be password protected on boot. You can change this by selecting the option from the menu "Reconfigure LILO".\par
+If you chose to use lilo and also said yes to automatically configuring and running lilo, then most of the work is done for you. Lilo installs automatically into the MBR\footnote{MBR - Master Boot Record, the first few bytes of a harddisk} and that should be suitable for most users.\par
-To turn off password protection, you will need to comment out (with the symbol "\#") or delete two lines in your lilo.conf file. The first is \lstinline!password=lunar!, which is found in the top section of the file, and the other is \lstinline!restricted! which is found right below the name of your kernel in the second section.\par
+If, alternatively, you want lilo to be installed in a partition instead of the MBR, you need to edit the \textit{lilo.conf} and change the \textit{boot=} section as follows:\par
-The other item of note is whether you want lilo to reside in your MBR (Master Boot Record) or on the first sector of your /boot partition. The line in your \textit{lilo.conf} file to edit for this purpose is\par
-
\begin{lstlisting}
-boot=/dev/discs/disc0/part1
+boot=/dev/hda2
\end{lstlisting}
-To make lilo get installed on the first sector of your /boot partition, you would leave this line as it is. If you want lilo to be written to your MBR, which is the recommended method, you would change the line to read
+Where \textit{/dev/hda2} points to the partition in which you want lilo to be installed into.\par
-\begin{lstlisting}
-boot=/dev/discs/disc0/disc
- \end{lstlisting}
-
Of course, these examples are pertinent to our setup that we have been using thoughout this manual. Your actual lilo.conf file may be different.\par
-If you want to switch to Grub later, see section \ref{lilo2grub}. \par
+If you want to use Grub later, see section \ref{lilo2grub}.\par
+
\paragraph{Integrating an other OS}
If you have an other operating system installed on a harddisk, you can configure lilo like this:
@@ -273,34 +276,30 @@
label = Windows
\end{lstlisting}
-as you see in this configuration Windows is installed on /dev/hda1, which is the first partition on your hdd. It will appear as "Windows" in the boot menu. \par
-%\textbf{Note} The partition needs to be marked as "bootable". really ?????
+as you see in this configuration Windows is installed on \textit{/dev/hda1}, which is the first partition on your first hard disk. It will appear as "Windows" in the boot menu.\par
+
\subsection{Grub}
If you chose grub as your bootloader, you will need to set up the configuration file. An example would be: \\
\begin{lstlisting}
-default 0
-timeout 30
-color white/blue white/black
+default 0
+timeout 30
+color white/blue white/black
+
title linux-2.4.20
-root (hd0,0)
-kernel /vmlinubz-2.4.25-r5.0.0 root=/dev/hda2 devfs=nomount
+root (hd0,0)
+kernel /vmlinubz-2.4.25-r5.0.0 root=/dev/hda2 devfs=nomount
\end{lstlisting}
-
-As we mentioned earlier in the partitioning section, you would want to mark your /boot partition as active. With grub it is imperative that you mark your /boot partition as active, otherwise grub will not work at all when you are finished with the installation and reboot to your new system.\par
\textbf{Note}: For further information regarding \lstinline{grub} see section \ref{lilo2grub}
+Grub is by default installed in the MBR of the disk you are installing on so there's no need to repeat that step manually. If you wish to change this and install grub into the \textit{/boot} partition, you will need to manually run grub and set it up that way. Don't forget also to mark your \textit{/boot} partition as active as well.\par
-\section{Installing The MBR}
-If you installed lilo or grub into the MBR then you don't need to use this step. If, however, you chose to place lilo or grub in the first sector of the /boot partition, then you would use this option. The MBR install is especially useful if the hard drive you are installing Lunar on is brand new and has never been used.\par
+\section{Setting the root password}
-
-\section{Setting the root passwort}
-
\begin{figure}
\begin{center}
\includegraphics[angle=270,width=0.8\textwidth]{./image/install10.eps}
@@ -308,9 +307,9 @@
\caption{Setting the root password}
\end{figure}
-After the kernel is finished you will end up at the kernel choosing screen. You need to choose exit and can now set the passwort for the root account. Choose a good password, like G49dN448e . A not so good password would be your name, your birthday or some other word that actually makes sense.\par
+After the kernel is finished you will end up at the kernel choosing screen. You need to choose exit and can now set the passwort for the root account. Choose a good password, for instance: \textit{:\\1De6 at Z}. A not so good password would be your name, your birthday or some other word that actually makes sense. A good password is 8 characters long, includes both numbers and punctuation characters and upper and lower characters.\par
-\textbf{Note:} Never choose this account as your default user. This would be a great security risk, as root can do everything with your system. \textbf{Always} use an other user that is even not in the root group and has no other privileged rights. Other popular OS are in to deep trouble, because of an other default setting in this place. \par
+\textbf{Note:} Never choose this account as your default user. This would be a great security risk, as root can do everything with your system. \textbf{Always} use an other user account that is not in the root group and has special other privileged rights.\par
\section{Setting Up Networking, Services and other bits}
@@ -321,12 +320,14 @@
\caption{Setting up networking, services, ssh keys and timezone}
\end{figure}
-The final steps are to set up networking. Select the \textit{Set Up Networking} option, you can configure a series of settings, as to what kind of card you have (only needed if you built your networking device as a module, and not part of the kernel), if you need to set up wireless or not, and whether you'll need to use dhcp or not. You should be familiar enough with your network to set this up on your own, as the questions put to you are very straightforward. You can setup DNS configuration, host and domain name and the global gateway. All this things can be changed later by running the \textit{lnet} utility. See \ref{lnet} .\par
-Further you can setup the services that are started automatically at bootime. This can be changed later by the lservices tool. See Chapter \ref{lserv} \par
-We are nearly finished, at last you need to set up your timezone. This should be pretty straightforward for just about everyone. Go to \textit{Select Timezone} and you will be presented with a long list of countries and some of the more popular timezones. The only thing to note is to be sure of whether your hardware clock is set to local time or to UTC. Most everyone will choose local at this stage.\par
+The final steps are to set up networking. Select the \textit{Set Up Networking} option, you can configure a series of settings, as to what kind of card you have (only needed if you built your networking device as a module, and not part of the kernel), if you need to set up wireless or not, and whether you'll need to use dhcp or not. You should be familiar enough with your network to set this up on your own, as the questions put to you are very straightforward. You can setup DNS configuration, host and domain name and the global gateway. All this things can be changed later by running the \textit{lnet} utility. See \ref{lnet}.\par
+Further you can setup the services that are started automatically at bootime. This can be changed later by the lservices tool. See Chapter \ref{lserv}.\par
+
+We are nearly finished, at last you need to set up your timezone. This should be pretty straightforward for just about everyone. Go to \textit{Select Timezone} and you will be presented with a long list of countries and some of the more popular timezones. The only thing to note is to be sure of whether your hardware clock is set to local time or to UTC. Most everyone will choose local at this stage, especially if you dualboot windows. People who run servers might say GMT here.\par
+
\section{Reboot!}
-Once you have completed setting up your networking, you are finished installing Lunar Linux! Congratulations! Select the option \textit{Done} and remove the cd from the drive when it ejects. Your Lunar system is now ready to go!\par
+Once you have completed setting up your networking, you are finished installing Lunar Linux! Congratulations! Select the option \textit{Done} and remove the cd from the drive when it reboots. Your Lunar system is now ready to go!\par
-\textbf{Have Fun!!}
\ No newline at end of file
+\textbf{Have Fun!!}
More information about the Lunar-commits
mailing list