[Lunar-commits] <lunar> lfirsttime overhauled
Stefan Wold
ratler at lunar-linux.org
Sat Oct 11 13:34:05 CEST 2014
commit 2f3dbe0fbe014c706f056ca099376b36f2819372
Author: Stefan Wold <ratler at lunar-linux.org>
Date: Sat, 11 Oct 2014 13:16:25 +0200
URL: https://github.com/lunar-linux/lunar/commit/2f3dbe0fbe014c706f056ca099376b36f2819372
lfirsttime overhauled
---
man/lfirsttime.8 | +230/-294
1 file changed, 230 insertions(+), 294 deletions(-)
--- a/man/lfirsttime.8
+++ b/man/lfirsttime.8
@@ -1,308 +1,244 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
-.\"
-.\" Standard preamble:
-.\" ========================================================================
-.de Sh \" Subsection heading
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Vb \" Begin verbatim text
-.ft CW
-.nf
-.ne \\$1
-..
-.de Ve \" End verbatim text
-.ft R
-.fi
-..
-.\" Set up some character translations and predefined strings. \*(-- will
-.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
-.\" double quote, and \*(R" will give a right double quote. | will give a
-.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
-.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
-.\" expand to `' in nroff, nothing in troff, for use with C<>.
-.tr \(*W-|\(bv\*(Tr
-.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
-.ie n \{\
-. ds -- \(*W-
-. ds PI pi
-. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
-. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
-. ds L" ""
-. ds R" ""
-. ds C` ""
-. ds C' ""
-'br\}
-.el\{\
-. ds -- \|\(em\|
-. ds PI \(*p
-. ds L" ``
-. ds R" ''
-'br\}
-.\"
-.\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
-.\" entries marked with X<> in POD. Of course, you'll have to process the
-.\" output yourself in some meaningful fashion.
-.if \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
-..
-. nr % 0
-. rr F
-.\}
-.\"
-.\" For nroff, turn off justification. Always turn off hyphenation; it makes
-.\" way too many mistakes in technical documents.
-.hy 0
-.if n .na
-.\"
-.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
-.\" Fear. Run. Save yourself. No user-serviceable parts.
-. \" fudge factors for nroff and troff
-.if n \{\
-. ds #H 0
-. ds #V .8m
-. ds #F .3m
-. ds #[ \f1
-. ds #] \fP
-.\}
-.if t \{\
-. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
-. ds #V .6m
-. ds #F 0
-. ds #[ \&
-. ds #] \&
-.\}
-. \" simple accents for nroff and troff
-.if n \{\
-. ds ' \&
-. ds ` \&
-. ds ^ \&
-. ds , \&
-. ds ~ ~
-. ds /
-.\}
-.if t \{\
-. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
-. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
-. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
-. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
-. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
-. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
-.\}
-. \" troff and (daisy-wheel) nroff accents
-.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
-.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
-.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
-.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
-.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
-.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
-.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
-.ds ae a\h'-(\w'a'u*4/10)'e
-.ds Ae A\h'-(\w'A'u*4/10)'E
-. \" corrections for vroff
-.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
-.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
-. \" for low resolution devices (crt and lpr)
-.if \n(.H>23 .if \n(.V>19 \
-\{\
-. ds : e
-. ds 8 ss
-. ds o a
-. ds d- d\h'-1'\(ga
-. ds D- D\h'-1'\(hy
-. ds th \o'bp'
-. ds Th \o'LP'
-. ds ae ae
-. ds Ae AE
-.\}
-.rm #[ #] #H #V #F C
-.\" ========================================================================
-.\"
-.IX Title "lfirsttime 8"
-.TH lfirsttime 8 "2005-03-09" "Moritz Heiber" "Lunar Linux for the first time"
-.SH "NAME"
-lfirsttime \- or 'What to do after a successful installation?'
-.SH "SYNOPSIS"
-.IX Header "SYNOPSIS"
-This manual page has been written in order to ease the life of the system administrator after the installation part of \fBLunar Linux\fR.
-.SH "DO NOT PANIC!"
-.IX Header "DO NOT PANIC!"
-These are the suggested tasks you should accomplish immediately after the first boot of a newly installed Lunar box.
-.PP
-All of the lunar related commands mentioned below either feature a whole manpage or at least a very useful helpscreen. If you need immediate assistance regarding any of those commands, issue:
-.PP
-\&\fBman 'command'\fR or \fB'command' \-\-help\fR
-.PP
+.TH LFIRSTTIME 8 "2014-10-11" "Lunar Linux" "Lunar Linux for the first time"
+.SH NAME
+lfirsttime \- What to do after a successful installation.
+.SH SYNOPSIS
+This manual page has been written in order to ease the life of the
+system administrator after the installation part of
+.B Lunar Linux.
+.SH DESCRIPTION
+.B Lunar Linux
+is a source based distribution which means that every module installed
+is compiled from source.
+.B Lunar Linux
+is also a rolling release distribution so there is no need to
+reinstall when a new ISO is released, simply keep your packages up to
+date.
+.LP
+These are the suggested tasks you should accomplish after the first
+boot of a newly installed Lunar box.
+.LP
+All of the lunar related commands mentioned below either feature a
+whole manpage or at least a very useful helpscreen. If you need
+immediate assistance regarding any of those commands, issue:
+.LP
+.B man 'command'
+or
+.B 'command' \-\-help
+.LP
at your console.
-.PP
-The operations described below follow a strict logic and they should be executed in sequence.
-.PP
-\&\fBPlease remember that the Lunar Install/Rescue \s-1ISO\s0 is not a full featured system.\fR
-.SH "NETWORK SETTINGS"
-.IX Header "NETWORK SETTINGS"
-This step is crucial to your future success with \fBLunar Linux\fR. If you haven't set up your network card yet try it with \fBlnet\fR. Remember, you need to know about your current network card's driver and have the kernel build the appropriate modules for it.
-.Sh "Check your network settings"
-.IX Subsection "Check your network settings"
-Once you've set up your network card correctly, try to ping out.
-.PP
-Example: \fBping google.com\fR
-.PP
-If it doesn't work you may be having a name resolution problem, try pinging to the \s-1IP\s0 address instead of the name.
-.PP
-Example: \fBping 216.239.57.99\fR
-.PP
-If pinging to \s-1IP\s0 is working but pinging to name fails, check the \fB/etc/resolv.conf\fR file and see if the nameserver entries are there. You may also want to check the man page, \fBman resolv.conf\fR if you are not familiar with the entries which should be in that file.
-.Sh "Check the network device"
-.IX Subsection "Check the network device"
-If pinging the \s-1IP\s0 address fails, check to see if your network interface is up and running. You may use the command \fBifconfig\fR to see the interface's status. You must be able to see the details of your network interface in the output of ifconfig.
-.PP
-If you cannot, then check if your \fB\s-1NIC\s0 (network interface card)\fR module is loaded (assuming you are using a modular kernel); use the command \fBlsmod\fR to see the already loaded modules and see wether the module for your network card is already loaded.
-.PP
-If you do not know for sure what type of network card you have try executing the command: \fBcat /proc/pci|grep Ethernet\fR or \fBlspci\fR. This should give the manufacturer and model name of your ethernet card.
-.PP
-If your \s-1NIC\s0 module is there but your interface is not up, reconfigure the interface with \fBlnet\fR and test again. If your \s-1NIC\s0 module is still not listed in the output of \fBlsmod\fR, the chances are you have misconfigured the kernel or misconfigured your network. To check the kernel modules, try \fBls \-l /lib/modules/`uname \-r`/kernel/drivers/net\fR to see the network modules available with the current kernel. If the your \s-1NIC\s0's kernel module doesn't show up you probably have to reconfigure and recompile your current kernel to include the appropriate module(s).
-.Sh "lnet or manual configuration"
-.IX Subsection "lnet or manual configuration"
-Your network setting can be configured completely using \fBlnet\fR; just make sure you set up your interface correctly as needed. If you encounter problems after having configured your network with \fBlnet\fR you probably want to adjust the configuration manually.
-.PP
-The network configuration file for your Lunar installation may be found in \fB/etc/config.d/network/'interface'\fR (f.e. 'eth0' \-> /etc/config.d/network/eth0). Any time you adjust your interface's configuration manually or through \fBlnet\fR you will have to restart the network to make use of any changes that have been done in the meantime. The init script used to start/stop/restart network is \fB/etc/init.d/network\fR.
-.PP
-Example: \fB/etc/init.d/network restart\fR
-.PP
-Good luck and please remember that you \fBhave to\fR to be able to ping f.e. 'google.com' to install any other packages or update your system!
-.SH "CORE UPDATES AND SETUP"
-.IX Header "CORE UPDATES AND SETUP"
-Since Lunar Linux is a source based distribution, some of the binaries and/or modules on the \s-1CD\s0 may have been upgraded to newer versions already. Here are the first steps you should take to get an up\-to\-date, smoothly running and fast system:
-.Sh "Update your coretools"
-.IX Subsection "Update your coretools"
-You need to get the most recent version of the available \fBcoretools\fR. The \fBcoretools\fR are the heart of every \fBLunar Linux\fR system. They provide you with all the necessary commands to maintain a working installation thus it's always recommended to have the latest version installed. There are two different choices:
-.PP
-\&\fBlunar\fR or \fBtheedge\fR
-.PP
-\&\fBlunar\fR is the stable branch of the lunar \fBcoretools\fR. It's meant to run with stable production environments. \fBtheedge\fR is the unstable branch. It might occasionally contain bugs, however it's generally used to test out new features and bugfixes before they're migrated to the stable branch. If you'd like to help out with the lunar development or you discovered a bug in \fBlunar\fR you might want to give \fBtheedge\fR a try.
-.PP
-Since the \s-1ISO\s0 ships with \fBtheedge\fR preinstalled you \fBhave to\fR update \fBtheedge\fR before you do anything else -- even if you're planning to use \fBlunar\fR later on!
-.PP
-Execute: \fBlin theedge\fR
-.PP
-If you want to keep \fBLunar Linux\fR as stable as possible you need to install the stable \fBcoretools\fR branch now by running
-.PP
-Execute: \fBlin lunar\fR
-.Sh "Core Components"
-.IX Subsection "Core Components"
-A very brief explanation of the most important coretool components. For further information regarding the referenced parts please refer to their manpages (i.e. man <part>):
-.IP "\fBlin\fR; usage: lin <module>" 4
-.IX Item "lin; usage: lin <module>"
-Install a package/module.
-.IP "\fBlvu\fR; usage: lvu <options> <module>" 4
-.IX Item "lvu; usage: lvu <options> <module>"
-Gather information about a package/module.
-.IP "\fBlrm\fR; usage: lrm <module>" 4
-.IX Item "lrm; usage: lrm <module>"
-Remove a package/module.
-.IP "\fBlunar\fR; usage: lunar <options>" 4
-.IX Item "lunar; usage: lunar <options>"
-Lunar configuration utility
-.Sh "Update your moonbase"
-.IX Subsection "Update your moonbase"
-The package repository from where the \fBcoretools\fR gather their \fBpackage information\fR is called \fBmoonbase\fR. Also, packages are usually referred to as \fBmodules\fR. Since the moonbase on your installation is probably outdated it's strongly recommended to update your moonbase right after your coretools.
-.PP
-Execute: \fBlin moonbase\fR
-.Sh "Set your preferences"
-.IX Subsection "Set your preferences"
-\&\fBLunar Linux\fR can easily be customized and is highly configurable. For changing the options that affect your system you may use the menu driven \fBlunar\fR configuration utility. It's based upon ncurses which means you can even run it in the console of your choice. You need to become root to use it.
-.IP "\fBOptimizations\fR" 4
-.IX Item "Optimizations"
-Set the right optimizations for your computer. Be aware that changing your optimizations to the wrong values might actually break your whole installation so be really careful about what you're choosing. The \s-1ISO\s0 has been built with a minimum of available optimizations to ensure the highest amount of flexibility. To see whether or not your processor supports a certain feature try a \fBcat /proc/cpu\fR. It usually shows the available settings that suit your machine.
-.IP "\fBIntegrity checking\fR" 4
-.IX Item "Integrity checking"
-Lunar is performing a range of security checks on tarballs and installed packages to prevent faulty tarballs and possible intruders from taking over your system. It also ensures that none of your currently installed packages is broken.
-.Sp
-You may select the amount of checks from the \fBIntegrity checking\fR submenu at the \fBOptions\fR menu. It's generally recommended to at least chose \fB\s-1FIND_CHECK\s0\fR and \fB\s-1LDD_CHECK\s0\fR.
-.IP "\fBFeature menu\fR" 4
-.IX Item "Feature menu"
-As mentioned before, Lunar is highly configurable. Thus you have a whole menu to select its features from. It's strongly advised to at least take a look at it and get used to them. Explanations are usually displayed as soon as you select an item.
-.IP "\fBApart from that\fR" 4
-.IX Item "Apart from that"
-Take a look at the \fBlunar\fR configuration tool. It can be a \fBpowerful companion\fR while achieving the goal of setting up your system.
-.SH "GENERAL UPDATES"
-.IX Header "GENERAL UPDATES"
-Right now you're set to update your whole system. Before you do that make sure you have the most recent \fBcoretools\fR and \fBmoonbase\fR installed.
-.PP
-The next step can be omitted -- however, it is highly recommended that you rebuild the following modules in the right order to ensure that your system is working right.
-.PP
-Here we go:
-.PP
-Execute: \fBlin \-cr gcc glibc gcc bash coreutils tar wget\fR
-.PP
-\&\fBExplanation:\fR
-.PP
-\&\fBlin\fR is obviously used to install a module. It also accepts multiple modules in a row. The '\-cr' switch means 'compile (c)' and 'reconfigure (r)'. They're explained at the manpage. One needs to update gcc thus the first gcc statement. Right after that one should recompile glibc to ensure that it's working well with the latest compiled gcc. And finally gcc again to make use of the newly compiled glibc. The modules right afterwards are used by \fBLunar Linux\fR itself thus they need to be up-to-date and compiled against the latest available gcc and glibc.
-.Sh "\fBA complete update\fP"
-.IX Subsection "A complete update"
-Now, to update your whole system you need to issue the following
-.PP
-Execute: \fBlunar update\fR
-.PP
-It's going to compare your system's installed modules against the moonbases' definitions and update the installed modules accordingly. It's going to give you a list of modules that are going to be updated. If you're not sure wether you want a certain module to be updated remove it from the list. Once you're done the coretools are going to start the update which usually is going to take a very long time on a freshly installed system since most of its components will probably be outdated. So grab a coffee and/or a book and wait for it to finish ;\-)
-.PP
-Once it is done it is going to present you with a summary about how many module where successfully updated and which of them failed. \fBlvu\fR ('lvu activity') is going to show you which of them failed and usually why. \fBlvu\fR ('lvu compile <module>') is also going to show you the compilation's logfile which should clearly point you to the error that led to the failure of the module's compilation.
-.PP
-The first thing to do would be to 're'lin' (i.e. execute \fBlin \-c\fR once more. It is always advised to use the \-c and the \-r switch in case a module fails to compile) all the failed modules by hand. If you think you will not be able to resolve the matter on your own you can still file a bugreport at the \fBLunar Linux bugtracker\fR http://bugs.lunar\-linux.org or report the error to the \fBLunar Linux mailinglist\fR. However, you will have to subscribe to the list at http://foo\-projects.org/mailman/listinfo/lunar before being able to post any mail to it.
-.PP
-Once the update has been completed successfully you may go ahead and customize your installation to suit your own needs. Well done!
-.SH "HINTS"
-.IX Header "HINTS"
-.IP "\fBTAB-completion\fR" 4
-.IX Item "TAB-completion"
-All of the coretools are able to do tab\-completion. Say, you want to install the module 'xfce4\-panel' just go ahead and type 'lin xfce4\-p<\s-1TAB\s0>' and lin is going to append the rest of the module's name to the command. Once there are too few characters to resolve the name into one single module you just need to hit \s-1TAB\s0 twice to get a list of all the modules starting with the characters you just typed i.e. 'lin xfce<\s-1TAB\s0><\s-1TAB\s0>' is going to give you a list of all modules starting with 'xfce'.
-.IP "\fBLeftovers\fR" 4
-.IX Item "Leftovers"
-In case of a compilation failure the sources of the failed module are left in \f(CW$BUILD_DIRECTORY\fR (usually /usr/src/). Moreover, a few tracking files lunar creates to monitor the running installation process might be left in /tmp. Make sure you tidy up these two locations from time to time.
-.Sp
-\&\fB\s-1CAUTION:\s0\fR Directories like 'linux\-2.x' are kernel source directories and _must_ be left intact. Otherwise your system is going to break! Only delete them if you're absolutely sure that they don't belong to your currently running kernel.
-.IP "\fBRunning coretools processes\fR" 4
-.IX Item "Running coretools processes"
-If you're interrupting a module installation process (f.e. by pressing '\s-1CTRL\-C\s0) you should check if there are any running coretools processes running in the background as another try to install the module might fail because of them. Have a closer look at \fBps aux\fR and \fBkill/killall\fR all the remaining coretools instances of a failed installation attempt.
-.Sp
-\&\fB\s-1CAUTION:\s0\fR Lunar allows you to run multiple installations independently. Be sure about the processes' purpose you're terminating!
-.IP "\fB\s-1IRC\s0 channel\fR" 4
-.IX Item "IRC channel"
-The fastest help you get is by chatting with the developers directly. Join the \fBLunar Linux \s-1IRC\s0 channel\fR at freenode
-.Sp
+.LP
+.B Please remember that the Lunar Install/Rescue ISO is not a full featured system.
+.LP
+A list of things to do:
+.TP
+\fBNetwork settings\fP
+This step is crucial to your future success with
+.B Lunar Linux.
+If you haven't configured your network yet try it with
+.B lnet.
+.TP
+.B Check your network settings
+Once you have configured your network, try to ping something on Internet.
+.IP
+Example: \fBping ping.sunet.se\fP
+.IP
+If it doesn't work you may be having a name resolution problem, try
+pinging to the IP address instead of the name.
+.IP
+Example: \fBping 192.36.125.18\fP
+.IP
+If pinging to IP is working but pinging to name fails, check the
+\fI/etc/resolv.conf\fP file and see if the nameserver entries are
+there. You may also want to check the man page, \fBman resolv.conf\fR,
+if you are not familiar with the content of this file.
+.TP
+.B Check the network device
+If pinging the IP address fails, check if your network interface is up
+and running. You may use the command \fBip\fP to view the interface's
+status.
+.IP
+If you cannot, then check if your \fBNIC (network interface card)\fP
+module is loaded (assuming you are using a modular kernel); use the
+command \fBlsmod\fR to get a list of currently loaded modules.
+.IP
+If you do not know for sure what type of network card you have try
+executing the command: \fBcat\fP \fI/proc/pci\fP \fB| grep Ethernet\fP
+or \fBlspci\fP. This should give the manufacturer and model name of
+your ethernet card.
+.TP
+.B lnet or manual configuration
+Your network setting can be configured completely using \fBlnet\fP;
+just make sure you set up your interface correctly as needed. If you
+encounter problems after having configured your network with
+\fBlnet\fP you probably want to adjust the configuration manually.
+.IP
+The network configuration file for your Lunar installation may be
+found in \fI/etc/config.d/network/'interface'\fP (i.e. 'eth0' \->
+\fI/etc/config.d/network/eth0\fP). If you adjust your interface's
+configuration manually it is required to restart the interface using
+\fBsystemctl\fP.
+.IP
+Example eth0 using DHCP: \fBsystemcl restart lnet-dhpcd at eth0\fP
+.IP
+Example eth0 using static ip: \fBsystemctl restart lnet-static at eth0\fP
+.TP
+.B Update your modules repository
+The modules repository from where the coretools gather their
+\fBpackage information\fP is called \fBmoonbase\fP. Also, packages are
+usually referred to as \fBmodules\fP. Since the moonbase on your
+installation is probably outdated it's strongly recommended to update
+your moonbase as the first thing you do.
+.IP
+To update your moonbase run: \fBlin moonbase\fP
+.TP
+.B Update your coretools
+The \fBcoretools\fP are the heart of every \fBLunar Linux\fP
+system. They provide you with all the necessary commands to maintain a
+working installation thus it's always recommended to have the latest
+version installed. Our \fBcoretools\fP module is called \fBlunar\fP.
+.IP
+To update \fBlunar coretools\fP run: \fBlin lunar\fP
+.IP
+A very brief explanation of the most important coretool
+components. For further information regarding the referenced parts
+please refer to their manpages (i.e. man <part>):
+.RS
+.IP
+\fBlin <module>\fP Install a package/module
+.IP
+\fBlvu <option> <module>\fP View information about a package/module
+.IP
+\fBlrm <moduule>\fP Uninstall a package/module
+.IP
+\fBlunar <option>\fP Lunar configuration utility
+.RE
+.TP
+\fBSet your preferences\fP
+\fBLunar Linux\fP can easily be customized and is highly
+configurable. For changing the options that affect your system you may
+use the menu driven \fBlunar\fR configuration utility. It's based on
+ncurses which means you can even run it in the console of your
+choice. You need to become root to use it.
+.RS
+.TP
+.B Optimizations
+Set the optimizations for your computer. Be aware that changing your
+optimizations to the wrong values might actually break your whole
+installation so be really careful about what you're choosing. The
+ISO has been built with a minimum of available optimizations to
+ensure the highest amount of flexibility. To see whether or not your
+processor supports a certain feature try a \fBcat /proc/cpu\fP. It
+usually shows the available settings that suit your machine.
+.TP
+.B Integrity checking
+Lunar is performing a range of security checks on tarballs and
+installed packages to prevent faulty tarballs and possible intruders
+from taking over your system. It also ensures that none of your
+currently installed packages is broken. You may select the amount of
+checks from the \fBIntegrity checking\fP submenu at the \fBOptions\fP
+menu. It's generally recommended to at least choose
+\fBFIND_CHECK\fP and \fBLDD_CHECK\fP.
+.TP
+.B Feature menu
+As mentioned before, \fBLunar\fP is highly configurable. Thus you have
+a whole menu to select its features from. It's strongly advised to at
+least take a look at it and get used to them. Explanations are usually
+displayed as soon as you select an item. It can be a \fBpowerful
+companion\fR while achieving the goal of setting up your system.
+.RE
+.TP
+.B General updates
+Right now you're set to update your whole system. Before you do that
+make sure you have the most recent \fBmoonbase\fR and \fBcoretools\fR
+installed.
+.IP
+To update your whole system run: \fBlunar update\fP
+.IP
+\fBlunar update\fP actually implicitly update \fBmoonbase\fP and
+\fBcoretools\fP for you. If you don't want it to do that you can use
+\fBlunar renew\fP that only updates the out of date modules.
+.IP
+It's going to compare your system's installed modules against the
+moonbase's definitions and update the installed modules
+accordingly. It's going to give you a list of modules that are going
+to be updated. If you're not sure wether you want a certain module to
+be updated remove it from the list. Once you're done the coretools are
+going to start the update which usually is going to take a while
+depending on how long ago the last update was done. So grab a coffee
+and/or a book and wait for it to finish ;\-)
+.IP
+Once it is done it is going to present you with a summary about how
+many module where successfully updated and which of them
+failed. \fBlvu\fP ('lvu activity') is going to show you which of them
+failed and usually why. \fBlvu\fP ('lvu compile <module>') is also
+going to show you the compilation's logfile which should clearly point
+you to the error that led to the failure of the module's compilation.
+.IP
+The first thing to do would be to 're'lin' (i.e. execute \fBlin
+\-cr\fP once more. It is always advised to use the \-c (compile) and
+the \-r (reconfigure) switch in case a module fails to compile. If you
+think you will not be able to resolve the matter on your own you can
+still file a bugreport at https://github.com/lunar-linux/lunar/issues
+or report the error to the \fBLunar Linux mailinglist\fR. You will
+have to subscribe to the list at
+http://lists.lunar\-linux.org/mailman/listinfo/lunar before being able
+to post any e-mail to it.
+.IP
+Once the update has been completed successfully you may go ahead and
+customize your installation to suit your own needs. Well done!
+.SH HINTS
+.TP
+.B TAB-completion
+All of the coretools are able to do tab\-completion. Say, you want to
+install the module 'xfce4\-panel' just go ahead and type 'lin
+xfce4\-p<TAB>' and lin is going to append the rest of the
+module's name to the command. Once there are too few characters to
+resolve the name into one single module you just need to hit
+TAB twice to get a list of all the modules starting with the
+characters you just typed i.e. 'lin xfce<TAB><TAB>' is going to give
+you a list of all modules starting with 'xfce'.
+.TP
+.B Leftovers
+In case of a compilation failure the sources of the failed module are
+left in \fB$BUILD_DIRECTORY\fP (usually /usr/src/). Moreover, a few
+tracking files lunar creates to monitor the running installation
+process might be left in /tmp. Make sure you tidy up these two
+locations from time to time.
+.IP
+\fBCAUTION:\fP Directories like 'linux\-x.x' are kernel source
+directories and _must_ be left intact. Otherwise your system is going
+to break! Only delete them if you're absolutely sure that they don't
+belong to your currently running kernel.
+.TP
+.B IRC channel
+The fastest help you get is by chatting with the developers
+directly. Join the \fBLunar Linux IRC channel\fP at freenode
irc://irc.freenode.net/#lunar
-.SH "NOTES"
-.IX Header "NOTES"
-This is merely an introduction to what should be done to get a ready-to-go Lunar system. Please consult the documentation at the Lunar website for more information.
-.SH "SEE ALSO"
-.IX Header "SEE ALSO"
+.SH NOTES
+This is merely an introduction to what should be done to get a
+ready-to-go Lunar system. Please consult the documentation at the
+Lunar website for more information.
+.SH SEE ALSO
Documentation at the Lunar Linux website at http://lunar\-linux.org
.PP
-\&\fIlunar\fR\|(8), \fImoonbase\fR\|(1), \fIlin\fR\|(8), \fIlvu\fR\|(1), \fIlget\fR\|(8), \fIlrm\fR\|(8), \fIlnet\fR\|(8)
-.SH "DISCLAIMER"
-.IX Header "DISCLAIMER"
+\fIlunar\fR\|(8), \fImoonbase\fR\|(1), \fIlin\fR\|(8), \fIlvu\fR\|(1), \fIlget\fR\|(8), \fIlrm\fR\|(8), \fIlnet\fR\|(8)
+.SH DISCLAIMER
The information and examples given here are for illustrative purposes. If you encounter any inaccuracies please send an email to the authors.
-.SH "COPYRIGHT"
-.IX Header "COPYRIGHT"
+.SH COPYRIGHT
This document is originally Copyrighted Kagan Kongar 2002.
.PP
Portions of this document Copyrighted (C) 2003\-2004 Terry Chan
.PP
-It has been almost completely rewritten by Moritz Heiber for the Lunar Linux development team under the Creative Commons License, (C) 2005
-.SH "AUTHORS"
-.IX Header "AUTHORS"
+It has been almost completely rewritten by Moritz Heiber for the Lunar
+Linux development team under the Creative Commons License, (C) 2005
+.PP
+Updated by Stefan Wold for the Lunar Linux team under the Creative
+Commons License, (C) 2014
+.SH AUTHORS
Kagan Kongar <kongar at tsrsb.org.tr>
.PP
Terry Chan <tchan at lunar\-linux.org>
.PP
Moritz Heiber <moe at lunar\-linux.org>
+.PP
+Stefan Wold <ratler at lunar\-linux.org>
More information about the Lunar-commits
mailing list