[Lunar-commits] r15510 - lunar-doc/trunk/lunar-manual

[ca3sar]

Author: ca3sar
Date: 2005-06-28 16:37:54 +0000 (Tue, 28 Jun 2005)
New Revision: 15510

Modified:
   lunar-doc/trunk/lunar-manual/chapter4.tex
   lunar-doc/trunk/lunar-manual/chapter5.tex
Log:
Fixing Chapters ... :S

Modified: lunar-doc/trunk/lunar-manual/chapter4.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/chapter4.tex	2005-06-28 16:31:54 UTC (rev 15509)
+++ lunar-doc/trunk/lunar-manual/chapter4.tex	2005-06-28 16:37:54 UTC (rev 15510)
@@ -0,0 +1,102 @@
+\chapter{Inside Lunar Linux} \label{inside}
+more detailed
+\section{Core Tools}
+docu of lin lvu lunar etc etc
+much more detail than above.
+\subsection{$lin$}
+\subsection{$lvu$}
+
+\subsection{Admins Tiny Little Helpers}\label{tlhelp}
+\paragraph{lservices}\label{lserv}
+\paragraph{lnet}\label{lnet}
+
+ lsevices, luser  etc etc ?
+
+\section{Handling /dev Devices}\label{devnode}
+
+\subsection{A little background}
+
+Every box needs a set of device node in order to work. Currently there are 2 ways of creating these nodes: statically or dynamically. \par
+
+\subsection{Static device nodes}
+
+/dev content is permanent, on a real permanent filesystem (like ext3, XFS, reiser...). All the needed nodes are present, or are created with a mknod command. You can also create nodes with the makedev utility. \par
+
+\subsection{Dynamic device nodes}
+
+Nodes are created from hotplug events, e.g., on the fly. Here, depending on your kernel, you have 2 choices:
+\par
+
+\subsubsection{devfs}
+devfs' device nodes are created in kernel space, on a virtual fs. It is therefore part of the kernel tree source.
+
+\subsubsection{udev}
+
+udev's device nodes are created in userspace, and by a userland application, thus outside the kernel tree. udev can lie on any filesystem, permanent or not, but due to its nature, is normally on a virtual filesystem, like ramfs - this is Lunar's case. \par
+
+Altough devfs is still currently in 2.6 it "will be removed real soon" (TM). So basically we can think of 2 defaults: for 2.4, devfs is mainly used; on 2.6, udev will be mainly used. A smaller portion of users still have static (on real fs) nodes. \par
+
+\paragraph{What commandline options can be used}
+
+To tell Lunar what type of device nodes I want to use there is a commandline switch that is dev=, that can take 4 values:
+
+\begin{itemize} 
+\item dev=static
+\item dev=devfs
+\item dev=udev
+\item no commandline whatsoever
+\end{itemize}
+
+The options are quite self explaining. A good thing to take in mind is that they behave differently depending on your kernel.
+
+\subsection{2.4 kernels}
+
+valid dev= values are:
+
+\begin{itemize} 
+\item dev=devfs
+\item dev=static
+  \end{itemize}
+
+If dev=udev was passed to a 2.4 kernel on boot, a warning message will be displayed, and it will fallback to normal 2.4 behaviour: if no dev= commandline has been supplied, or its value is not correct, it shall fall through:
+
+\begin{itemize} 
+\item Test for dev=devfs, and if devfs' binary is there, try to boot with it.
+\item If there's no devfs installed, boot as if a static dev was present.
+  \end{itemize}
+
+\subsection{2.6 kernels}
+
+valid dev= values are:
+
+\begin{itemize}
+\item  dev=udev
+\item dev=devfs
+\item dev=static
+  \end{itemize}
+
+And are tested in exactly this order if no valid dev= is supplied or no commandline is supplied whatsoever.
+
+\subsection{Adding the params: bootloaders}
+
+\subsubsection{lilo}
+
+To add a commandline param in lilo, you have to use the append label. Taking dev=udev as an example:
+
+\begin{flushleft}
+image=/boot/vmlinuz	label=awesomekernel	root=/dev/hda2	append="dev=udev video=radeonfb:1152x864-16 at 60"
+\end{flushleft}
+
+If you have prompt set in your lilo.conf, you can even write the option just before the kernel you want loads.
+
+\subsubsection{grub}
+
+To add a commandline param in grub, all you have to do it put it behind the kernel placement, on the kernel label's line:
+
+\begin{flushleft}
+title awesomekernel
+root (hd0,1)
+kernel /boot/vmlinuz root=/dev/hda1 dev=udev video=radeonfb:1152x864-16 at 60 
+\end{flushleft}
+
+Don't forget that in grub you can edit the kernel label line on boot.
\ No newline at end of file

Modified: lunar-doc/trunk/lunar-manual/chapter5.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/chapter5.tex	2005-06-28 16:31:54 UTC (rev 15509)
+++ lunar-doc/trunk/lunar-manual/chapter5.tex	2005-06-28 16:37:54 UTC (rev 15510)
@@ -1,107 +1,3 @@
-\chapter{Inside Lunar Linux} \label{inside}
-more detailed
-\section{Core Tools}
-docu of lin lvu lunar etc etc
-much more detail than above.
-\subsection{$lin$}
-\subsection{$lvu$}
-
-\subsection{Admins Tiny Little Helpers}\label{tlhelp}
-\paragraph{lservices}\label{lserv}
-\paragraph{lnet}\label{lnet}
-
- lsevices, luser  etc etc ?
-
-\section{Handling /dev Devices}\label{devnode}
-
-\subsection{A little background}
-
-Every box needs a set of device node in order to work. Currently there are 2 ways of creating these nodes: statically or dynamically. \par
-
-\subsection{Static device nodes}
-
-/dev content is permanent, on a real permanent filesystem (like ext3, XFS, reiser...). All the needed nodes are present, or are created with a mknod command. You can also create nodes with the makedev utility. \par
-
-\subsection{Dynamic device nodes}
-
-Nodes are created from hotplug events, e.g., on the fly. Here, depending on your kernel, you have 2 choices:
-\par
-
-\subsubsection{devfs}
-devfs' device nodes are created in kernel space, on a virtual fs. It is therefore part of the kernel tree source.
-
-\subsubsection{udev}
-
-udev's device nodes are created in userspace, and by a userland application, thus outside the kernel tree. udev can lie on any filesystem, permanent or not, but due to its nature, is normally on a virtual filesystem, like ramfs - this is Lunar's case. \par
-
-Altough devfs is still currently in 2.6 it "will be removed real soon" (TM). So basically we can think of 2 defaults: for 2.4, devfs is mainly used; on 2.6, udev will be mainly used. A smaller portion of users still have static (on real fs) nodes. \par
-
-\paragraph{What commandline options can be used}
-
-To tell Lunar what type of device nodes I want to use there is a commandline switch that is dev=, that can take 4 values:
-
-\begin{itemize} 
-\item dev=static
-\item dev=devfs
-\item dev=udev
-\item no commandline whatsoever
-\end{itemize}
-
-The options are quite self explaining. A good thing to take in mind is that they behave differently depending on your kernel.
-
-\subsection{2.4 kernels}
-
-valid dev= values are:
-
-\begin{itemize} 
-\item dev=devfs
-\item dev=static
-  \end{itemize}
-
-If dev=udev was passed to a 2.4 kernel on boot, a warning message will be displayed, and it will fallback to normal 2.4 behaviour: if no dev= commandline has been supplied, or its value is not correct, it shall fall through:
-
-\begin{itemize} 
-\item Test for dev=devfs, and if devfs' binary is there, try to boot with it.
-\item If there's no devfs installed, boot as if a static dev was present.
-  \end{itemize}
-
-\subsection{2.6 kernels}
-
-valid dev= values are:
-
-\begin{itemize}
-\item  dev=udev
-\item dev=devfs
-\item dev=static
-  \end{itemize}
-
-And are tested in exactly this order if no valid dev= is supplied or no commandline is supplied whatsoever.
-
-\subsection{Adding the params: bootloaders}
-
-\subsubsection{lilo}
-
-To add a commandline param in lilo, you have to use the append label. Taking dev=udev as an example:
-
-\begin{flushleft}
-image=/boot/vmlinuz	label=awesomekernel	root=/dev/hda2	append="dev=udev video=radeonfb:1152x864-16 at 60"
-\end{flushleft}
-
-If you have prompt set in your lilo.conf, you can even write the option just before the kernel you want loads.
-
-\subsubsection{grub}
-
-To add a commandline param in grub, all you have to do it put it behind the kernel placement, on the kernel label's line:
-
-\begin{flushleft}
-title awesomekernel
-root (hd0,1)
-kernel /boot/vmlinuz root=/dev/hda1 dev=udev video=radeonfb:1152x864-16 at 60 
-\end{flushleft}
-
-Don't forget that in grub you can edit the kernel label line on boot.
-
-
 \chapter{Getting to work ...}
 
 \section{Kernel 2.6}