Changeset 1233


Ignore:
Timestamp:
Mar 11, 2007, 3:35:20 PM (13 years ago)
Author:
bruno
Message:
  • LCA video announce
  • web site now deals with video and audio directories
  • various HOWTO fixes from Mike Kinney (kinneym_at_redacesolutions.com>)
Location:
branches/stable
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • branches/stable/mondo-doc/mondorescue-howto.sgml

    r1044 r1233  
    173173e-mail! Thank you. Without it we can't offer
    174174any tangible help because you aren't either. That's what the log
    175 file is for. It is located at <filename>/var/log/mondo-archive.log</filename>; and <filename>/var/log/miindi.log</filename> or at <filename>/var/log/mondo-restore.log</filename>
    176 </para>
    177 <para>
    178 This document was originaly written by native english speakers, but is maintained by a non-native english speaker so help me correct mistaques instead of rumbling that I've done one :-)
     175file is for. It is located at <filename>/var/log/mondo-archive.log</filename>; and <filename>/var/log/mindi.log</filename> or at <filename>/var/log/mondo-restore.log</filename>
     176</para>
     177<para>
     178This document was originaly written by native english speakers, but is maintained by a non-native english speaker so help me correct mistaques (sic) instead of rumbling that I've done one :-)
    179179</para>
    180180<para>
     
    711711boot-time. Mondo uses fdisk, mkfs, cat, less, more, afio, gzip,
    712712bzip2, your keyboard configuration, your glibc libraries, your
    713 other libraries, your kernel, your modules, ... a lot! Mindi takes
    714 care of all that, so that Mondo can get on with the job of backing
     713other libraries, your kernel, your modules, ... which is a lot of tools!
     714Mindi takes care of all that, so that Mondo can get on with the job of backing
    715715up or restoring your data.
    716716</para>
     
    738738drives. That works for most drives but some drives just don't like
    739739that.</para>
    740 <para>Mondo Rescue has tested thousands of times on various computers.
    741 It worked for them.
     740<para>Mondo Rescue has been tested thousands of times on various computers.
     741It has worked for them.
    742742Thousands of users testify to Mondo's stability and its ease of
    743743use. However, please test it on your own system before you rely on
     
    858858        Since November 2005, Hugo Rabson has tranfered the maintenance
    859859        of the Mondo Rescue suite to Andree Leidenfrost and Bruno Cornec,
    860         both previous developpers and packagers of the tool since nearly
     860        both previous developers and packagers of the tool since nearly
    861861        the begining.
    862862</para>
     
    948948<para>See Mondo's <ulink url="http://www.mondorescue.org/downloads.shtml">Download
    949949page</ulink> for details.</para>
    950 <para>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs, ncurses, newt,
     950<para>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs (may be part of the dvd+rw-tools package), ncurses, newt,
    951951isolinux/syslinux, lzo (optional), lzop (optional), mkisofs, slang,
    952952and a few other packages.</para>
     
    10291029</sect1>
    10301030
     1031<sect1 id="installation-mindi-busybox">
     1032<title>Mindi Busybox Installation</title>
     1033<para>If you are installing from a tarball then copy it to wherever
     1034you have enough space, for example /tmp and type:</para>
     1035<para></para>
     1036<informaltable><tgroup cols="1"><tbody>
     1037<row>
     1038<entry>
     1039
     1040        bash# cd /tmp
     1041</entry>
     1042</row>
     1043<row>
     1044    <entry>
     1045        bash# tar -zxvf mindi-busybox-1.x.tgz
     1046    </entry>
     1047</row>
     1048<row>
     1049    <entry>
     1050        bash# cd mindi-busybox-1.x
     1051    </entry>
     1052</row>
     1053<row>
     1054    <entry>
     1055        bash# make oldconfig
     1056    </entry>
     1057</row>
     1058<row>
     1059    <entry>
     1060        bash# make busybox
     1061    </entry>
     1062</row>
     1063<row>
     1064    <entry>
     1065        bash# make install
     1066    </entry>
     1067</row>
     1068</tbody></tgroup></informaltable>
     1069<para>This installs busybox files and symlinks into /usr/local/lib/mindi/rootfs
     1070</para>
     1071<para>Or, if you are installing from an RPM/deb then copy it to
     1072wherever you have enough space, for example /tmp and type:</para>
     1073<para></para>
     1074<informaltable><tgroup cols="1"><tbody>
     1075<row>
     1076<entry>
     1077
     1078bash# rpm -Uvh /tmp/mindi-busybox-1.x-x.i386.rpm
     1079</entry>
     1080</row>
     1081<row>
     1082<entry>
     1083
     1084or
     1085</entry>
     1086</row>
     1087<row>
     1088<entry>
     1089
     1090bash# dpkg -i /tmp/mindi-busybox-1.x-x.deb
     1091
     1092</entry>
     1093</row>
     1094</tbody></tgroup></informaltable>
     1095
     1096<para>This installs busybix files and symlinks into /usr/lib/mindi/rootfs
     1097</para>
     1098</sect1>
     1099
    10311100<sect1 id="installation-mondo">
    10321101<title>Mondo Installation</title>
     
    10941163<para>This installs mondo into /usr/lib/mondo and installs
    10951164the programs into /usr/sbin</para>
     1165</sect1>
     1166
     1167<sect1 id=rpm-verif>
     1168        <title>RPM verifications</title>
     1169        <para>For RPM based distributions (Fedora, OpenSuSE, Mandriva, ...), you may want to do this post-install in order to check the validity of your installation:
     1170<informaltable><tgroup cols="1"><tbody>
     1171<row>
     1172    <entry>
     1173        bash# rpm -Va mindi mondo mindi-busybox
     1174    </entry>
     1175</row>
     1176</tbody></tgroup></informaltable>
     1177<para>
     1178    This gives some truly obtuse output. Basically it will list all files that do NOT pass the verify tests (done on size, MD5 signature, etc). Please read rpm man page to discover the meaning of the output.
     1179    </para>
    10961180</sect1>
    10971181</chapter>
     
    12691353
    12701354<sect1 id="backup-recommandations">
    1271 <title>Recommandations</title>
     1355<title>Recommendations</title>
    12721356<itemizedlist>
    12731357<listitem>
     
    12751359        compare differences following the backup). Especially shutdown
    12761360        properly any running database on your system, as the recovery
    1277         may lead to corrupted data.</para>
     1361        may lead to corrupted data. Or if applicable, boot to single user mode.</para>
    12781362</listitem>
    12791363<listitem>
     
    14881572 has been done. The problem lies in the fact that cron does not allow
    14891573 user interaction with a job. If you schedule a mondoarchive job via
    1490  cron, you better be sure it needs only one media. in practical terms,
     1574 cron, you better be sure it needs only one media. In practical terms,
    14911575 this means using tapes or ISOs (if CD-R(W) is your backup medium).
    14921576 However, for tape users, there's always the possibility that the
     
    15151599If your backup already occupies two media, this method will allow
    15161600 as much of the backup as possible to proceed during quiet periods.
    1517  Time the backup to start wich enough time to complete the first media
     1601 Time the backup to start with enough time to complete the first media
    15181602 shortly before the operator arrives for work. The next media can
    15191603 be mounted and the backup completed asap and minimises the time for
     
    15401624 of interacting via a FIFO or some such) except termination via its
    15411625 pid. The only program that I know of that allows such interaction
    1542  and serves as a wrapper for other prrocesses is 'screen'
     1626 and serves as a wrapper for other processes is 'screen'
    15431627 </para>
    15441628 </sect2>
     
    15481632 attach to a terminal when it first starts. This won't happen under
    15491633 cron so screen will fail. Fortunately, screen comes with a "start
    1550  detached" option.
     1634 detached" (-d) option.
    15511635 </para>
    15521636 </sect2>
     
    18451929<listitem><para>Wipe your drives and restore everything,
    18461930automatically and unattended. Warning: This does exactly what is
    1847 says, so be carefull using it.</para>
     1931says, so be careful using it.</para>
    18481932</listitem></varlistentry>
    18491933<varlistentry><term>Expert</term>
     
    23752459</tbody></tgroup></informaltable>
    23762460
    2377 <para>I hope this manual is proving to be useful to you.</para>
     2461<para>I hope this manual was useful for you.</para>
    23782462</sect2>
    23792463</sect1>
     
    23962480<itemizedlist>
    23972481<listitem>
    2398 <para>Your kernel version</para>
    2399 </listitem>
    2400 <listitem>
    2401 <para>Your Linux distro's name and version</para>
    2402 </listitem>
    2403 <listitem>
    2404 <para>Whether your kernel supports initrd and loopfs; it should!</para>
    2405 </listitem>
    2406 <listitem>
    2407 <para>What sort of PC you are using, including hard disk configurations</para>
     2482<para>Your kernel version (uname -a)</para>
     2483</listitem>
     2484<listitem>
     2485        <para>Your Linux distro's name and version (/etc/distro-release)</para>
     2486</listitem>
     2487<listitem>
     2488        <para>Whether your kernel supports initrd and loopfs; it should! (grep -E '^CONFIG_BLK_DEV_LOOP|^CONFIG_BLK_DEV_INITRD' /usr/src/linux/.config </para>
     2489</listitem>
     2490<listitem>
     2491<para>What sort of PC you are using, including hard disk configurations (results of dmidecode, lshw, fdisk -l are useful here)</para>
    24082492</listitem>
    24092493</itemizedlist>
     
    24302514'mondo'. Hugo Rabson wasn't sure what to call this project. 'Faust' was one
    24312515idea he had, partly as a dig at his former boss who practically owned
    2432 him because of his legal status at the time. In the end, He chose
     2516him because of his legal status at the time. In the end, he chose
    24332517something short and distinctive.</para>
    24342518</answer>
     
    24382522                keels over and dies. What's wrong?</para></question>
    24392523<answer>
    2440         <para>A: It works on Red Hat 7.x/8/9, RHEL 2.1/3/4, Mandrakelinux 8.x/9.x/10.x, Debian 3.0, most flavors
     2524        <para>A: It works on Red Hat 7.x/8/9, RHEL 2.1/3/4, Mandrakelinux 8.x/9.x/10.x/200x, Fedora 4/5/6, Debian 3.x, most flavors
    24412525                of SuSE/SLES, some flavors of Slackware, etc.
    24422526The more distributions we support, the more moving targets we have to
     
    24572541                <para>A: Please send a copy of <filename>/var/log/mindi.log</filename> to the &ML;
    24582542along with a description of your distro, your kernel, etc.
    2459 Oh, and before sending it, please read it asit's much easier to understand it.</para>
     2543Oh, and before sending it, please read it as it is much easier to understand it.</para>
    24602544</answer>
    24612545</qandaentry>
     
    24982582please?</para></question>
    24992583<answer>
    2500 <para>A: please enter the suggestion in our feature system at &WWW;
     2584<para>A: Please enter the suggestion in our feature system at &WWW;
    25012585</para>
    25022586</answer>
     
    26352719<para>A: Recompile your kernel (or use '-k FAILSAFE'). Take a look
    26362720at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to
    2637 see what you're kernel must support.</para>
     2721see what your kernel must support.</para>
    26382722</answer>
    26392723</qandaentry>
     
    26442728<para>A: Recompile your kernel and add Virtual memory file system
    26452729support. Take a look at <link linkend="overview-sysrq-kernelreq">Linux
    2646 Kernel support</link> to see what you're kernel must support. (Of
     2730Kernel support</link> to see what your kernel must support. (Of
    26472731course, if your PC has less than 64MB of RAM, you could always...
    26482732what's the phrase? I know, upgrade your RAM!)</para>
     
    26562740        <para>A: Your kernel must support initrd, loopfs, IDE|SCSI|USB CD-ROM's, and
    26572741ramdisks. Take a look at <link linkend="overview-sysrq-kernelreq">Linux
    2658 Kernel support</link> to see what you're kernel must support. If
     2742Kernel support</link> to see what your kernel must support. If
    26592743your kernel does not support these things, Mondo will not boot from
    26602744your CD. However, when running Mindi, you may choose to use _its_
     
    27142798kernel and/or recompile it. Take a look at
    27152799<link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to see
    2716 what you're kernel must support.</para>
     2800what your kernel must support.</para>
    27172801</answer>
    27182802</qandaentry>
     
    27512835<answer>
    27522836<para>A: Recompile your kernel and add initrd support. Take a look
    2753 at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link>to
    2754 see what you're kernel must support.</para>
     2837at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to
     2838see what your kernel must support.</para>
    27552839</answer>
    27562840</qandaentry>
     
    28082892<question><para id="TAPENICE">Q: My tape drive
    28092893doesn't play nicely with Mondo at boot-time. What do I do?</para></question>
    2810 <answer><para>A: Play with 'mt'. Use its setblksize and
     2894<answer><para>A: Play with the 'mt' command (package mt-st). Use its setblksize and
    28112895defblksize switches to reconfigure your tape drive if necessary.
    28122896Some tape drives just are painful. If yours is one of
     
    28872971                drives?</para></question>
    28882972<answer>
    2889 <para>A: Yes. See above.</para>
     2973        <para>A: Yes. See above.</para>
     2974        <para>Of course, mondo will relay on the kernel to support your tape drive. So you should first check that your kernel found it correctly. Use for example:
     2975                 ine of the following commands
     2976<informaltable><tgroup cols="1"><tbody>
     2977<row>
     2978<entry>
     2979        bash# dmesg | grep tape
     2980</entry>
     2981</row>
     2982<row>
     2983<entry>
     2984        bash# cat /proc/scsi/scsi
     2985</entry>
     2986</row>
     2987<row>
     2988<entry>
     2989        bash# mt -f /dev/st0 status
     2990</entry>
     2991</row>
     2992</tbody></tgroup></informaltable>
     2993
     2994
    28902995</answer>
    28912996</qandaentry>
     
    29603065partitions and their settings. Mondo will do the partitioning and
    29613066formatting for you.</para>
    2962 <para>Tested Raid controllers includes all those showind only classical devices
     3067<para>Tested Raid controllers includes all those showing only classical devices
    29633068        such as /dev/sdx, and SmartArray cciss controllers.</para>
    29643069</answer>
     
    29713076<informaltable><tgroup cols="1"><tbody>
    29723077<row>
    2973 <entry>
    2974 
    2975 bash# cdrecord -scanbus
    2976 
    2977 </entry>
    2978 </row>
    2979 </tbody></tgroup></informaltable>
     3078    <entry>
     3079        bash# cdrecord -scanbus
     3080    </entry>
     3081</row>
     3082</tbody></tgroup></informaltable>
     3083<para>or for ATAPI type of devices:</para>
     3084<para></para>
     3085<informaltable><tgroup cols="1"><tbody>
     3086<row>
     3087    <entry>
     3088        bash# cdrecord -scanbus dev=ATAPI
     3089    </entry>
     3090</row>
     3091</tbody></tgroup></informaltable>
     3092<para>you may replace ATAPI by ATA in the previous line with certain cdrecord versions and hadrware configurations</para>
     3093
    29803094
    29813095<para>Find your CD burner's device# (e.g. '0,0,0'). Call Mondo with
     
    32093323<qandaentry>
    32103324<question>
    3211 <para id="LVM"/>Q: I can't nuke-restore my LVM or RAID or
     3325<para id="LVM">Q: I can't nuke-restore my LVM or RAID or
    32123326LVM-on-RAID setup. I have to do it manually. What now?</para></question>
    32133327<answer>
  • branches/stable/tools/livwww

    r1042 r1233  
    8787ln -sf /var/www/html/mediawiki .
    8888ln -sf /var/www/html/admin .
     89ln -sf ../video .
     90ln -sf ../audio .
    8991
    9092# Compute News
Note: See TracChangeset for help on using the changeset viewer.