[Lunar-commits] CVS: theedge/usr/share/man/man8 lfirsttime.8, 1.10,
1.11
Moritz Heiber
moe at lunar-linux.org
Mon Mar 7 22:03:25 UTC 2005
Update of /var/cvs/lunar/theedge/usr/share/man/man8
In directory espresso.foo-projects.org:/tmp/cvs-serv25045
Modified Files:
lfirsttime.8
Log Message:
I finally got to rewriting lfirsttime. This should be _alot_ better then
the manpage we had until now. Thanks rolling out to Jens, Jasper and
Jaime for typo-hunting. I feel dizzy now.
Index: lfirsttime.8
===================================================================
RCS file: /var/cvs/lunar/theedge/usr/share/man/man8/lfirsttime.8,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- lfirsttime.8 21 May 2004 10:27:13 -0000 1.10
+++ lfirsttime.8 7 Mar 2005 22:03:20 -0000 1.11
@@ -1,105 +1,295 @@
-.TH "lfirsttime" "8" "Release $Revision$" "Kagan Kongar" "Lunar firsttime"
+.\" 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-07" "Moritz Heiber" "Lunar Linux for the first time"
.SH "NAME"
-.LP
-\fBlfirsttime\fR \- Lunar after\-boot manual
-.SH "OVERVIEW"
-.LP
-This manual page is written to ease the life of the System Administrators after the installation part of \fBLunar Linux\fR is finished.
-.SH "DO NOT PANIC"
-.LP
-These are the suggested tasks you should accomplish immediately after the first boot of a newly installed Lunar box. The operations described below follow some logic and they should be executed in sequence ie; from beginning to end :=) Please remember that the Lunar Install/Rescue ISO is not a full featured system. You must install more software via the "lin" mechanism to get a fully functioning server and/or workstation. See the moonbase/profiles section for some handy collections of Lunar Modules. It should also be noted that you MUST "lin xfree86", BEFORE you try to "lin" any other module that requires X\-Windows. For some reason this is not obvious to quite a few Lunar users.
-
-\fB1. Check Networking: \fRBetter check networking first, try pinging out.
-.IP
-Example : ping www.google.com
-.BR
-
-The above may or may not work. If it's not working you may be having a name resolution problem, try pinging to the IP address instead of the name,
-.BR
-
-Example: ping 24.172.57.4 (lunar-linux.org)
-.BR
-
-If pinging to IP 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.
-.BR
-
-If pinging the IP address fails, check to see if your network interface is up and running. You may use the command \fBifconfig\fR to see the interface status. You must be able to see the details of your network interface in the output of ifconfig. If you cannot, then check if your NIC (network interface card) module is loaded (assuming you are using a modular kernel); use the command \fBlsmod\fR to see the loaded modules. If you do not know for sure what type of network card you have try executing the command: \fBcat /proc/pci|grep Ethernet\fR. This should output the manufacturer and model of your ethernet card. If your NIC module is there but your interface is not up, reconfigure the interface with the command \fBlnet\fR and test again. If your NIC module is still not listed in the output of lsmod, the chances are you have misconfigured the kernel or misconfigured networking. To check the kernel modules, try \fBls \-l /lib/modules/`uname \-r`/kernel/drivers/net\fR to see the network modules available in the kernel. If you are unable to see your NIC module, recompile and reinstall your kernel with the command \fBlin \-c linux\fR and try again after reboot.
-.BR
-The network can completely be configured using \fBlnet\fR, make sure you set up your interface correctly as needed. If needed follow the next steps to manually adjust the configuration.
-
-.BR
-The network configuration file for your Lunar installation may be found in \fB/etc/config.d/network/<interface>\fR, ie; the configuration of your eth0 is written under \fB/etc/config.d/network/eth0\fR The configuration script you may use to configure your interfaces is called \fBlnet\fR. Any time you adjust the configuration of your networking interface you must restart networking to implement any changes you have made. The init script used to start/stop/restart network is \fB/etc/init.d/network\fR.
-.BR
-
-Good luck and please remember that you must be able to ping dbguin.lunar\-linux.org in order to update your system.
-.LP
-
-\fB2. Update the Moonbase: \fRSince Lunar Linux is a source based distribution, some of the binaries and/or modules on the CD may have been upgraded to newer versions already.
-.IP
-Do a \fBlin moonbase; lin lunar\fR. These commands will update the package collection (Moonbase) and the core package management tools.
-.LP
-
-
-\fB3. Set Your Preferences: \fRThere are a number of options which you may set or reset. For optimum performance, you must visit those.
-.IP
-Type \fBlunar\fR and press enter as root. See \fBoption\fR menu. Please visit \fBOptimize Architecture\fR item first. Select your CPU and compile options there (my own preferences are \fBi686 pipe faster strip\fR and the ISO is prepared with \fBi386 pipe small strip\fR).
-.BR
-
-Also, check \fBOption \-> Integrity Checking\fR and be sure that at least \fBFIND_CHECK\fR and \fBLDD_CHECK\fR are enabled.
-.BR
-
-Do not forget to have a look at \fBOption \-> Feature Menu\fR
-.BR
-
-Beyond the mentioned tasks you should take the time to have a general look at the options available and get acquainted with them. :=)
-.LP
-\fB
-4. Rebuild: \fRIn order to 1) be able to rollback your installations, you need a cache for the installed packages. 2) have the fastest Linux distro available. \fBNOTE:\fR This step is only recommended now for users that must have their entire Lunar box highly optimized. Regular Lunar users will only need a \fBlunar renew\fR (much quicker to complete than a rebuild) at this point and then continue on with step 5.
-.BR
-
-Just type \fBlunar rebuild\fR and go out for lunch. The rebuild process may take some time depending on the CPU power and available RAM on your machine.
-.BR
-
-This process should complete flawlessly. However, check the \fB/usr/src\fR directory for the remains of unsuccessful installations. If a module is installed successfully, nothing is left behind in /usr/src/<module_name>. If an installation failed you will find a source directory for that module left behind in \fB/usr/src\fR.
-.BR
-
-If there are any directories except the kernel, re\-lin those modules (lin \-c <module_name) and watch carefully to see what is happening during the build. Report bugs at: http://bugs.lunar\-linux.org/ and you should also subscribe to the lunar mailing list which you may do at: http://lunar\-linux.org/mailman/listinfo/lunar.
-.LP
-
-\fB5. Customize Your Box: \fRIMO no need to describe that step further.
-
-.SH "LIFESAVERS"
-.LP
-Below are some useful addresses
-.BR
-
-\fBWebsite: \fRhttp://www.lunar\-linux.org/
-.BR
-
-\fBMaillist: \fRhttp://lunar\-linux.org/mailman/listinfo/lunar
-.BR
-
-\fBIRC: \fRirc.freenode.net #lunar
-
+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 usefull helpscreen. If you need immediant assistance regarding any of those commands, issue:
+.PP
+\&\fBman 'command'\fR or \fB'command' \-\-help\fR
+.PP
+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 built 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 encouter 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 ment 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 lateron!
+.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 explaination 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 is higly customize\- and 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. Beware that changing your optimizations to the wrongly values might actually break your whole installations so be really carefull about what you're chosing. The \s-1ISO\s0 has been built with a minimum of available optimizations to ensure the highest amount of flexibility. To see wether 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 cheks from the \fBIntegrity checking\fR submenu at the \fBOptions\fR menu. It's generally recommeneded 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 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 recommened 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 incase 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 "\fB\s-1IRC\s0 channel\fR" 4
+.IX Item "IRC channel"
+The fastest help you get by chatting with the developers directly. Join the \fBLunar Linux \s-1IRC\s0 channel\fR at freenode
+.Sp
+irc://irc.freenode.net/#lunar
.SH "NOTES"
-.LP
-This is a work in progress. Expect frequent updates.
+.IX Header "NOTES"
+This is by far not a complete coverage of what should be done with a ready-to-go Lunar system. Please consult the documentations at the Lunar website for more information.
.SH "SEE ALSO"
-.LP
-lunar(8), moonbase(1), lin(8), lvu(1), lget(8), lrm(8), lnet(8)
+.IX Header "SEE ALSO"
+Documenations 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"
-.LP
-The information and examples given here are for illustrative purposes. Use at
-your own risk. Every attempt has been made to insure that the content of this
-document was accurate when written. If you find inaccuracies, please send me
-clarifications.
+.IX Header "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"
-.LP
-This document is Copyrighted Kagan Kongar 2002. It may be reproduced and distributed in whole or in part, in any medium physical or electronic, as long as this copyright notice is retained on all copies.
-.LP
-Portions of this document Copyrighted (C) 2003-2004 Terry Chan
+.IX Header "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"
-.LP
-Kagan Kongar <kongar at tsrsb.org.tr>
-.PP
-Terry Chan <tchan at lunar\-linux.org>
+.IX Header "AUTHORS"
+Kagan Kongar <kongar at tsrsb.org.tr>
+.PP
+Terry Chan <tchan at lunar\-linux.org>
+.PP
+Moritz Heiber <moe at lunar\-linux.org>
More information about the Lunar-commits
mailing list