Changeset 328

Jan 17, 2006, 11:42:18 AM (13 years ago)

Documentation work goes on:

  • 20 new sgml chunks integrated
  • Makefile really working now for the first case
  • FDL now has ids
20 deleted
3 edited


  • branches/2.06/documentation/Makefile

    r327 r328  
    88$(TARGET).txt: $(SRC)
    9     docbook2txt -u $(TARGET).sgml -o $(TARGET).txt
     9    docbook2txt $(TARGET).sgml
    1111$(TARGET).ps: $(SRC) $(DSL) $(IMAGES)
    12     docbook2ps -d $(TARGET).dsl'#print' -o $(TARGET).ps $(TARGET).sgml
     12    #docbook2ps -d $(TARGET).dsl'#print' -o $(TARGET).ps $(TARGET).sgml
     13    docbook2ps $(TARGET).sgml
     14    hugelatex -fmt=jadetex -mltex $(TARGET).tex
     15    hugelatex -fmt=jadetex -mltex $(TARGET).tex
     16    hugelatex -fmt=jadetex -mltex $(TARGET).tex
     17    dvips $(TARGET).dvi -o $(TARGET).ps
    1419$(TARGET)/index.html: $(SRC) $(DSL) $(IMAGES)
    15     mkdir -p $(TARGET)
    16     cd $(TARGET)
    17     docbook2html -d $(TARGET).dsl'#html' $(TARGET).sgml
    18     cd ..
     20    rm -f $(TARGET)
     21    docbook2html -d $(TARGET).dsl'#html' -o $(TARGET) $(TARGET).sgml
    2023$(TARGET).html: $(SRC) $(DSL) $(IMAGES)
    21     docbook2html -u -d $(TARGET).dsl'#txt' -o $(TARGET).html $(TARGET).sgml
     24    docbook2html -u -d $(TARGET).dsl'#txt' $(TARGET).sgml
    2326$(TARGET).pdf: $(SRC) $(DSL) $(IMAGES)
    24     docbook2html -u -d $(TARGET).dsl'#pdf' -o $(TARGET).pdf $(TARGET).sgml
     27    docbook2pdf -d $(TARGET).dsl'#pdf' $(TARGET).sgml
     28    hugepdflatex -fmt=jadetex -mltex $(TARGET).tex
     29    hugepdflatex -fmt=jadetex -mltex $(TARGET).tex
     30    hugepdflatex -fmt=jadetex -mltex $(TARGET).tex
     31    dvips $(TARGET).dvi -o $(TARGET).pdf
    2633$(TARGET).rtf: $(SRC) $(DSL) $(IMAGES)
    27     docbook2rtf -u -d $(TARGET).dsl'#pdf' -o $(TARGET).rtf $(TARGET).sgml
     34    docbook2rtf -d $(TARGET).dsl'#pdf' $(TARGET).sgml
  • branches/2.06/documentation/fdl.sgml

    r324 r328  
    1717    </blockquote>
    19   <sect1 label="0">
     19  <sect1 id="fdl-preamble" label="0">
    2020    <title>PREAMBLE</title>
    4444  </sect1>
    46   <sect1 label="1">
     46  <sect1 id="fdl-def" label="1">
    4747    <title>APPLICABILITY AND DEFINITIONS</title>
    112112  </sect1>
    114   <sect1 label="2">
     114  <sect1 id="fdl-verbatimcp" label="2">
    115115    <title>VERBATIM COPYING</title>
    130130  </sect1>
    132   <sect1 label="3">
     132  <sect1 id="fdl-quantitycp" label="3">
    133133    <title>COPYING IN QUANTITY</title>
    172172  </sect1>
    174   <sect1 label="4">
     174  <sect1 id="fdl-modif" label="4">
    175175    <title>MODIFICATIONS</title>
    303303  </sect1>
    305   <sect1 label="5">
     305  <sect1 id="fdl-combining" label="5">
    306306    <title>COMBINING DOCUMENTS</title>
    330330  </sect1>
    332   <sect1 label="6">
     332  <sect1 id="fdl-collection" label="6">
    333333    <title>COLLECTIONS OF DOCUMENTS</title>
    347347  </sect1>
    349   <sect1 label="7">
     349  <sect1 id="fdl-aggregation" label="7">
    350350    <title>AGGREGATION WITH INDEPENDENT WORKS</title>
    368368  </sect1>
    370   <sect1 label="8">
     370  <sect1 id="fdl-translation" label="8">
    371371    <title>TRANSLATION</title>
    384384  </sect1>
    386   <sect1 label="9">
     386  <sect1 id="fdl-term" label="9">
    387387    <title>TERMINATION</title>
    397397  </sect1>
    399   <sect1 label="10">
     399  <sect1 id="fdl-futurerev" label="10">
    400400    <title>FUTURE REVISIONS OF THIS LICENSE</title>
    418418  </sect1>
    420   <sect1 label="">
     420  <sect1 id="fdl-howto" label="">
    421421    <title>How to use this License for your documents</title>
  • branches/2.06/documentation/mondorescue-howto.sgml

    r327 r328  
    1213<title>MondoRescue HOWTO</title>
    2020in its latest version the
    21 &curdate;</pubdate>
    4750Bryan J. Smith
    5155<holder role="">Bruno Cornec</holder>
    6772, or even if it breaks the hardware. All the software included in it, if not alr
    6873eady copyrighted is released under the GPL.
    73 <revnumber>2.06</revnumber>
    74 <date>2006-01-16</date>
    75 <authorinitials>Bruno Cornec</authorinitials>
    76 <revdescription>
    77 <para>
    78 First SGML version publically available, remade from the HTML docs of the project.
    79 </para>
    80 </revdescription>
     79    <revnumber>2.06</revnumber>
     80    <date>2006-01-16</date>
     81    <authorinitials>Bruno Cornec</authorinitials>
     82    <revdescription>
     83    <para>
     84    First SGML version publically available, remade from the HTML docs of the project.
     85    </para>
     86    </revdescription>
    114120However, software editors don't garantee you a lot either (re-read the contracts).
    117 <sect2 id="newversion"><title>New versions of this document</title>
     124<sect1 id="newversion"><title>New versions of this document</title>
    119126<para>The newest version of this document can always be found on
    122129If you make a translation of this document into another language, please let meknow so that I can include a reference to it here.
    124 </sect2>
    125 <sect2><title>Suggestions / Feedback</title>
     133<sect1><title>Suggestions / Feedback</title>
    127135I rely on you, the reader, to make this HOWTO useful. THis HOWTO is probably incomplete even if it tries to be accurate to the best of our knowledge.
    148156any tangible help because you aren't either. That's what the log
    149157file 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>
    151160This 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 :-)
    159168Guylhem AZNAR <email></email>.
    161 </sect2>
    163 <sect2 id=thanks><title>Aknowledgements</title>
     172<sect1 id=thanks><title>Aknowledgements</title>
    165174<para>Thanks goes to these people for helping and adding to this
    214 </sect2>
    216 <sect1 id="quickstart"><title>QuickStart</title>
     226<chapter id="quickstart"><title>QuickStart</title>
    217227<itemizedlist mark="bullet" spacing="Compact">
    224234<para>Install the tarball, RPM, or DEB mindi and mondo
    225 packages. (see <xref linkend="installation">Installation</xref>
     235packages. (see <link linkend="installation">Installation</link>
    226236for more details)</para>
    447457<para>If you can boot, fine. If not, make a Mindi "Test" CD to
    448458checkout the compatibility of your system. (see
    449 <xref linkend="testingmindi">Testing Mindi</xref> for more
     459<link linkend="testingmindi">Testing Mindi</link> for more
    450460details). Remove the CD/floppy; boot your computer as usual;
    451461execute as root</para>
    494504<para>If you still cannot boot from Mindi's CD then please e-mail
    495 the <xref linkend="feedback">mailing list</xref> for help.
     505the <link linkend="feedback">mailing list</link> for help.
    579 </sect1>
     591<chapter id="overview"><title>Overview</title>
     593<sect1 id="mondorescue">
     594<title>Mondo Rescue</title>
     595<para>Mondo Rescue backs up your file system to CD, tape, NFS
     596(archives stored remotely) or ISO's (archives stored locally).
     597Mondo uses afio as the backup engine; afio is a well-respected
     598replacement for tar. In the event of catastrophic data loss, you
     599may restore some or all of your system, even if your hard drives
     600are now blank. Mondo Rescue can do a lot of other cool
     604<para>You can use Mondo to clone an installation of Linux. Just
     605backup the crucial stuff and exclude /home, /var/log, etc.</para>
     608<para>You can backup a non-RAID file system and restore it as RAID
     609including the root partition (if your kernel supports that).</para>
     612<para>You can backup a system running on one format and restore as
     613another format.</para>
     616<para>You can restructure your partitions, e.g. shrink/enlarge,
     617reassign devices, add hard drives, etc, before you partition and
     618format your drives. Mondo will restore your data and amend
     619/etc/lilo.conf and /etc/fstab accordingly.</para>
     622<para>You can backup Linux/Windows systems, including the boot
     623sectors. Mondo will make everything right at restore-time.
     624(However, do run "Scandisk" when you first boot into Windows, just
     625in case.)</para>
     628<para>You can use your Mondo backup CD to verify the integrity of
     629your computer.</para>
     632<para>Mondo's principal virtue is that it protects you from the
     633problems that can arise when you reinstall completely from scratch.
     634If you want to wipe and restore your system every year just as a
     635matter of 'good practice', Mondo is not for you. However, if you
     636want to get up and running again in a hurry after someone breaks
     637into your computer and wipes it (or if you accidentally wipe it
     638yourself) then Mondo is definitely for you. It will permit you to
     639roll back to a known-good installation in a very short period of
     640time, sometimes as little as twenty minutes. Even if you backup
     641large amounts of data to tape daily and do not want to add yet
     642another backup regime, please consider backing up the core
     643filesystem (i.e. everything but the directories containing your
     644huge database and your prizewinning novel) every month or so, just
     645in case. You will be glad you did.</para>
     646<para>What is Mondo not?</para>
     647<para>Mondo is not an everyday backup program. It is not designed
     648to replace tar, afio, kbackup, etc. Mondo is designed to make it
     649possible to recover from scratch if necessary. Tar and afio offer a
     650quick, convenient way to backup small sets of files, sometimes to
     651removable media.</para>
     654<sect1 id="mindi">
     657Mindi Linux creates a set of boot/root floppy disk images
     658that will let you perform basic system maintenance on your Linux
     659distro. The principal virtues of Mindi's boot disks are the fact
     660that they contain your kernel, modules, tools and libraries. You
     661can ask for additional binaries (or other files) to be included on
     662the kit. The libraries will be added for you.
     664<para>Whichever modules were loaded at backup-time, they are
     665reloaded at boot-time. So, in theory, you will boot into almost the
     666same environment as you were in when you backed up. If you want to
     667add files to your Mindi boot disks, edit '&lt;INSTALLPATH OF
     668MINDI&gt;/mindi/deplist.txt' and add the files to that list. The
     669added files and dependencies, will be spread across the data disks
     670at run-time.
     672<para>Mindi makes sure that Mondo has all the tools it needs at
     673boot-time. Mondo uses fdisk, mkfs, cat, less, more, afio, gzip,
     674bzip2, your keyboard configuration, your glibc libraries, your
     675other libraries, your kernel, your modules, ... a lot! Mindi takes
     676care of all that, so that Mondo can get on with the job of backing
     677up or restoring your data.
     679<para>Mindi is also handy for making boot CDs/disks which stand on
     680their own. You do not need Mondo. Indeed, if you like, you could
     681use another backup/restore program with Mindi. Just add it to
     682Mindi's dependency list (type 'locate deplist.txt' to find it).
     683Mindi will include your software on its boot CD/disks the next time
     684you run mindi.
     689<sect1 id="linuxbackup">
     690<title>Linux Backup</title>
     691<para>Mondo Rescue and Mindi Linux are used primarily as Linux
     692backup and cloning tools. The fall in prices of CD-RW drives and
     693writable discs will allow current users to keep good backups and
     694future users to leverage the cloning capability.</para>
     695<para>Tape drives are more likely to suit your needs if you run a
     696larger installation (or have lots of MP3's). Warning! OnStream
     697drives do not play well with Mondo. I do not know why. It is, in my
     698opinion, something which OnStream should look into. Mondo uses
     699fopen(), fread(), fwrite() and fclose() to interact with tape
     700drives. That works for most drives but some drives just don't like
     702<para>I have tested it thousands of times on my own computer with
     703my own data and with no alternate backup regime. It worked for me.
     704Thousands of users testify to Mondo's stability and its ease of
     705use. However, please test it on your own system before you rely on
     706it. In fact, do not rely on any software until you have tested it
     707to see if it performs as expected.</para>
     708<para>To establish that Mondo will behave well in an emergency,
     709please be prepared. Run a test backup as follows:-</para>
     712<para>Run mondoarchive without any command-line options.</para>
     714<listitem>Backup a subset of files - e.g. /usr/local - to CD or
     715tape. Say 'yes' when asked if you want to verify them.</listitem>
     716<listitem>If you are not backing up to CD, please create boot
     717floppies when prompted.</listitem>
     719<para>Next, restore archives to your live filesystem.</para>
     722<para>When mondoarchive terminates, run mondorestore without any
     723command-line options.</para>
     725<listitem>Insert the CD or the first boot floppy when prompted.
     726Press &lt;Enter&gt;. Wait a moment.</listitem>
     727<listitem>Select a subset of files to restore, e.g. /usr/local/man
     728and /usr/local/bin. Hit OK.</listitem>
     729<listitem>Restore files to /tmp or /root/RESTORED or something
     731<listitem>When mondorestore terminates, compare the restored files
     732to the originals using cmp or diff.</listitem>
     734<para>Finally, simulate an emergency restore.</para>
     737<para>Boot from CD/floppies.</para>
     739<listitem>Select 'Interactive Mode' at boot-time. (Type
     740'interactive' and hit &lt;Enter&gt;.)</listitem>
     741<listitem>Hit OK when shown the mountlist. Say 'yes' when asked if
     742you accept the mountlist.</listitem>
     743<listitem>Select files to restore, e.g. /usr/local/man and
     744/usr/local/bin. Hit OK.</listitem>
     745<listitem>Restore files to /tmp or /root/RESTORED or something
     747<listitem>When mondorestore terminates, please reboot and compare
     748the restored files to the originals.</listitem>
     750<para>FYI, the subroutines to repartition and reformat your drives
     751are very stable. If you are a RAID or LVM user, you
     752might&nbsp;encounter some difficulties when wiping and restoring
     753from scratch because of the sheer range of filesystem layouts and
     754the impossibility of testing Mondo on every single one. If you have
     755trouble, just drop to the command-line and partition/format
     756manually. Then, call mondorestore, select Interactive Mode, and say
     757'no' when asked if you want Mondo to partition or format your
     758drives for you.</para>
     759<para>You see, even if you have trouble, you still have two hands
     760and most of the tools you need - lvchange, pvcreate, fdisk, mkraid,
     761etc. - to do it manually. After you have prepped and formatted your
     762drives manually (if you have to), just run mondorestore again and
     763say 'no' when asked if you want to prep or format your drives. What
     764could be easier?</para>
     767<sect1 id="winbackup">
     768<title>Windows Backup</title>
     769<para>Backing up windows partitions.</para>
     770<sect2 id="win95"><title>Windows ME/95/98</title>
     771<para>Verify that the partition is listed in /etc/fstab and is
     772mounted (e.g. /dev/hda1). Mondo will take care of everything else.
     773The files will be archived just like all other files in the live
     774file system. At restore-time, Mondo will take care of the boot
     775sector of /dev/hda1 prior to the restore.</para>
     776<para>Note: if Windows ME/95/98 is not located on /dev/hda1 or
     777/dev/sda1, then Mondo will not take care of the boot sector of
     778/dev/hda1. The user will have to boot from a DOS floppy and run SYS
     779C: to correct the Windows boot sector.</para>
     781<sect2 id="winnt"><title>Windows NT4/2K/XP</title>
     782<para>Windows NT4/2K/XP typically use the NTFS file system, not
     783VFAT.. The user should use '-x /dev/hda1' (or whichever device the
     784/dev/hda1. The user will have to boot from a DOS floppy and run SYS
     785C: to correct the Windows boot sector.</para>
     786</sect2><sect2 id="AEN13"><title>3.4.2. Windows NT4/2K/XP</title>
     787<para>Windows NT4/2K/XP typically use the NTFS file system, not
     788VFAT.. The user should use '-x /dev/hda1' (or whichever device the
     789Windows partition resides). Mondo will treat the partition as a
     790biggiefile. Mondo will also add an entry to the mountlist to
     791reflect the size and type of the partition. The user may not edit
     792that partition's size at restore-time (for obvious reasons).</para>
     793<para>Please bear in mind that Mondo was written for Linux users.
     794If Mondo does not backup or restore your Windows system well, you
     795might want to consider paying for 1-to-1 technical support.
     796Ironically, the only people to pay for 1-to-1 technical support
     797have been Linux users, whereas Windows users want a free ride. That
     798is one reason why the Linux community gives me warm fuzzies.</para>
     801<sect1 id="history">
     802<title>Mondo Rescue and Mindi Linux
     804<para>Mondo Rescue was created in December 1999 as a utility to
     805clone Linux/Windows installations. Norton Ghost would not do the
     806job, and my boss wanted to jump on the Linux bandwagon. So, I wrote
     807a few scripts and shoehorned them into the latest Linux-Mandrake
     808CD. Since that time, Mondo grew into a disaster recovery suite for
     809Linux and Windows. Mondo forced me to learn about the kernel, its
     810initrd initial ramdisk, modules, library dependencies, disk
     811partitioning, and the myriad differences between the Top 10 Linux
     813a few scripts and shoehorned them into the latest Linux-Mandrake
     814CD. Since that time, Mondo grew into a disaster recovery suite for
     815Linux and Windows. Mondo forced me to learn about the kernel, its
     816initrd initial ramdisk, modules, library dependencies, disk
     817partitioning, and the myriad differences between the Top 10 Linux
     819<para>The first formal release was made on February 18th, 2000.
     820Mondo is currently one of the top five Linux backup/restore
     821programs. Mondo has been compared favorably to ArcServe, Arkeia and
     822BRU. Although Mondo lacks the more advanced, enterprise-level
     823features of ArcServe and Arkeia, for workstations and small- to
     824medium-size servers it is ideal because it is small, fast,
     825efficient, stable, comes with source code, and is being actively
     826developed and supported.</para>
     829<sect1 id="sysreq">
     832<sect2 id="hwreq">
     833<title>Hardware Requirements</title>
     835<para>Your computer must have:</para>
     838<para>Intel(R)-compatible CPU</para>
     841<para>64MB of RAM (128MB recommended)</para>
     844<para>800MB of hard disk space free</para>
     847<para>CD writer, tape streamer, NFS share or some way to backup the
     848backups :)</para>
     851<para>It is recommended that your computer have very good airflow.
     852The backup with Mondo Rescue and Mindi Linux will utilize your CPU,
     853CD drive and fixed disk(s) like very few other applications. With a
     854few hours of system backup activity, computers without sufficient
     855airflow may show symptoms such as not burning full CD discs. The
     856solution is a $20 or less additional fan at your local electronics
     857discount store.</para>
     860<sect2 id="kernelreq">
     861<title>Kernel Requirements</title>
     863<para>Your kernel must have:</para>
     866<para>stable loopfs support, which means it really needs to be
     8672.2.19 or 2.4.7 (or later)</para>
     870<para>CD-ROM device support</para>
     873<para>ISO9660 file system support</para>
     876<para>initrd ramdisk support (built-in)</para>
     879<para>Virtual memory file system support (built-in)</para>
     882<para>floppy disk support (built in)</para>
     885<para>ext2 file system support (built-in)</para>
     888<para>Support for the backup media (Tape, CD-RW, NFS, Hard
     892<para>If the backup media is CD-RW then you need SCSI emulation
     896<para>Please note that the stock kernels of Red Hat 7.2, 7.3, 8.0,
     897Mandrake 8.2, 9.0, SuSE 7.x,, 8.x, and Slackware 8.x all meet
     898Mondo's requirements. If your kernel does not meet Mondo's
     899requirements then there is something wrong with it. Mondo's demands
     900are not unreasonable.</para>
     901<para>Mondo (specifically Mindi) does not require any specific
     902modules. It does require that your kernel support the initrd
     903initial ramdisk facility. Typically this is supported by the Linux
     904kernel. Modules used are needed to support the CD, floppy disks,
     905hard disks, etc. If the support is modular, then the modules will
     906be incorporated in a boot disk by Mindi. If the support is built-in
     907(static), then it will be available at boot-time by default.</para>
     909<sect2 id="swreq">
     910<title>Software Requirements</title>
     911<para>See Mondo's <ulink url="../download.html">Download
     912page</ulink> for details.</para>
     913<para>Mondo requires afio, bzip2, cdrtools/cdrecord, ncurses, newt,
     914isolinux/syslinux, lzo (optional), lzop (optional), mkisofs, slang,
     915and a few other packages.</para>
     916<para>Good Linux distributions provide all these packages. If yours
     917does not then please go to the aforementioned Download page or surf
     918the Net, preferably the website of the distribution you are
     920<para>Mondo's expectations are not unreasonable, either of your
     921Linux distribution or of your kernel. However, if your distribution
     922fails to meet its expectations and you cannot find out how to
     923resolve them, please feel free to e-mail the
     924<ulink url="../../feedback/feedback.html">mailing
     929<chapter id="installation">
     932<sect1 id="mindi-install">
     933<title>Mindi Installation</title>
     934<para>If you are installing from a tarball then copy it to wherever
     935you have enough space, for example /tmp and type:</para>
     937<informaltable><tgroup cols="1"><tbody>
     941bash# cd /tmpbash# tar -zxvf mindi-0.7x.tgzbash# cd mindi-0.7xbash# ./
     947<para>This installs mindi into /usr/local/share/mindi and installs
     948links to the programs into /usr/local/sbin</para>
     949<para>Or, if you are installing from an RPM then copy it to
     950wherever you have enough space, for example /tmp and type:</para>
     952<informaltable><tgroup cols="1"><tbody>
     956bash# rpm -Uvh /tmp/mindi-0.7x-x.i386.rpm
     962<para>This installs mindi into /usr/share/mindi and installs links
     963to the programs into /usr/sbin. This may be /usr/local/share/mindi
     964and /usr/local/sbin, depending on the package you use. Different
     965Linux distributions put system files in different places. The funny
     966thing is, each distribution claims it is right and the others are
     967wrong. Oh, and they all agree that I mustn't have read the LFS!
     969<para>Debian users may wish to first create a .deb file and then
     970use the debian package manager:</para>
     972<informaltable><tgroup cols="1"><tbody>
     976bash# cd /tmpbash# alien mindi*.rpmbash# dpkg -i mindi*.deb
     982<para>This installs mindi into /usr/share/mindi and installs links
     983to the programs into /usr/sbin</para>
     986<sect1 id="mondo-install">
     987<title>Mondo Installation</title>
     988<para>If you are installing from a tarball then copy it to wherever
     989you have enough space, for example /tmp and type:</para>
     991<informaltable><tgroup cols="1"><tbody>
     995bash# cd /tmpbash# tar -zxvf mondo-1.xx.tgzbash# cd mondo-1.xxbash# make &amp;&amp; make install
     1001<para>This installs mondo into /usr/local/share/mondo and installs
     1002links to the programs into /usr/local/bin</para>
     1003<para>Or, if you are installing from an RPM then copy it to copy it
     1004to wherever you have enough space, for example /tmp and
     1007<informaltable><tgroup cols="1"><tbody>
     1011bash# rpm -Uvh /tmp/mondo-1.5x-x.i386.rpm
     1017<para>This installs mondo into /usr/share/mondo and installs links
     1018to the programs into /usr/bin</para>
     1019<para>Debian users may wish to first create a .deb file and then
     1020use the debian package manager:</para>
     1022<informaltable><tgroup cols="1"><tbody>
     1026bash# cd /tmpbash# alien mondo*.rpmbash# dpkg -i mondo*.deb
     1032<para>This installs mondo into /usr/share/mondo and installs links
     1033to the programs into /usr/bin</para>
     1037<chapter id="test">
     1040<sect1 id="mindi-test">
     1041<title>Testing Mindi</title>
     1043<para>Mindi is a vital part of the backup procedure. If you have
     1044used Mondo before or if you are in a hurry, skip steps 6.2 and 6.3;
     1045go straight to QuickStart.</para>
     1046<para>However, if you have time or if you have been having trouble
     1047getting Mondo to work, I would recommend trying out Mindi directly
     1048(rather than via Mondo) to see if it can produce a bootable CD on
     1049your system.</para>
     1050<para>Make sure you are root while doing this, otherwise mindi will
     1051fail, now do this.</para>
     1052<para>If you have any problems, please:-</para>
     1055<para>read /var/log/mindi.log</para>
     1057<listitem>feel free to edit mindi (it's a shell script, btw) to try
     1058to fix the problem yourself</listitem>
     1059<listitem>contact the mailing list if you get stuck.</listitem>
     1063<informaltable><tgroup cols="1"><tbody>
     1067bash# mindi
     1073<para>Example screen output, selecting to use your own kernel, to
     1074create boot disks, and to create a bootable CD image:</para>
     1076<informaltable><tgroup cols="1"><tbody>
     1080Mindi Linux mini-distro generator v0.72 by HRabson &lt;;--------------------------
     1081----------------------------------------------------Do you want to use your own kernel to build the boo
     1082t disk (y/n) ? yYour kernel is /boot/vmlinuz-2.4.14-k6 (v2.4.14-k6)Generating list of dependency files.
     1083....................... Done.Analyzing your keyboard's configuration.Adding the following keyboard mapp
     1084ing tables:................... DoneDropping i686-optimized libraries if appropriate.............DoneAss
     1085embling dependency files........ Done.The files have been subdivided into 2 directories.Your mountlist
     1086will look like this:-DEVICE MOUNTPOINT FORMAT SIZE (MB)/dev/hda3 / ext2 996/dev/hda2 swap swap 127/dev/
     1087hda4 /usr ext2 6189Tarring and zipping the groups......... Done.Creating data disk #1...#2... Done.1722
     1088KB boot disk was created OK............................ Done.2880KB boot disk was created OK...........
     1089................. Done.In the directory '/root/images/mindi' you will find the images:-mindi-boot.1722.
     1090img mindi-boot.2880.img mindi-data-1.img mindi-data-2.imgWould you like to create boot+data floppy disk
     1091s now (y/n) ?yWARNING! THIS WILL ERASE YOUR FLOPPY DISKS.About to write boot disk. Please press ENTER.W
     1092riting boot disk.................................................. Done.About to write data disk #1. Pl
     1093ease press ENTER.Writing data disk #1........................... Done.About to write data disk #2. Plea
     1094se press ENTER.Writing data disk #2........................... Done.Shall I make a bootable CD image? (
     1095y/n) yFinished.One 1.72MB boot disk, one 2.88MB boot disk and 2 data disks were created.
     1101<para>If your kernel is too large (more than about 900KB) then you
     1102cannot make boot floppies, although you can still make a bootable
     1103CD image. The easiest way to test Mindi in either case is to say
     1104'n' to its first question and 'y' to its second, then use the
     1105separate application cdrecord to make a bootable CD-R or
     1107<para>Use the cdrecord application to write the CD image:</para>
     1109<informaltable><tgroup cols="1"><tbody>
     1113bash# cd /root/images/mindibash# cdrecord -scanbus
     1119<para>The output of the above call to cdrecord will tell you your
     1120CD writer's node. It is usually '0,0,0'. Choose one of the
     1121following calls to write the CD, depending on whether the disk in
     1122the drive is a CD-R or a CD-RW. Please replace 'x,x,x' with your
     1123writer's node. For further information, type 'man cdrecord" from a
     1124Linux command line.</para>
     1125<para>If writing to a CD-RW Drive/Disc:</para>
     1127<informaltable><tgroup cols="1"><tbody>
     1131bash# cdrecord -blank fast dev=x,x,x speed=4 mindi.iso (for CD-RW)
     1137<para>If writing to a CD-R Drive/Disc:</para>
     1139<informaltable><tgroup cols="1"><tbody>
     1143bash# cdrecord dev=x,x,x speed=4 mindi.iso (for CD-R)
     1149<sect1 id="mondo-test">
     1150<title>Testing Mondo</title>
     1155<chapter id="backup">
     1158<sect1 id="backup-recommandations">
     1160<para>Mama does Mondo? Papa does Mondo? Is that a Dean Martin song?
     1161Well, anyway, here is how I backup my system:</para>
     1164<para>Shut down all possible applications (this minimizes any
     1165compare differences following the backup)</para>
     1172<informaltable><tgroup cols="1"><tbody>
     1176bash# mondoarchive
     1182<para>For most users, that should be enough. :-) Mondoarchive will
     1183usually autodetect your hardware and configure it for you.</para>
     1184<para>If you are a power user (or you like to control every detail
     1185of how Mondo runs) then you may want to look at the command-line
     1186switches. For example:-</para>
     1188<informaltable><tgroup cols="1"><tbody>
     1192bash# mondoarchive -Ow4 -gF -I /home
     1198<para>Cdrecord will tell me where my CD recorder lives, in SCSI
     1199terms, which in my case is '0,0,0'. The call to mondoarchive tells
     1200Mondo that I want to backup everything to a 4x CD-RW drive that has
     1201a CD-RW disk in it. (Use -Oc instead of -Ow if you are using
     1203<para>Please put the first CD-R(W) in the drive now. You will be
     1204prompted to insert CD #2 but you will not be prompted to insert the
     1205first disk. However, if you forget, do not worry: if Mondo fails to
     1206write the first (or any) disk, it will offer to retry, abort or
     1208<para>I run Mondo at the highest compression available ('-9) and
     1209then go to work. I then walk home at lunch (I live right by my
     1210workplace), change CD, eat lunch, and go back to work. When I get
     1211home, it has all been done.</para>
     1212<para>Your mileage may vary. Experiment. Find the speed/compression
     1213compromise that best suits your needs.</para>
     1214<para>If you are using cron then please use -F to make sure that
     1215Mondo does not prompt you to create bootable floppy disks. Cron
     1216does not handle user interaction well because it pipes stdin and
     1217stdout specially. Please consult cron's manual for more
     1218information. Jesse Keating has written a script for cron/Mondo
     1219users. It is available on the
     1220<ulink url="../../docs/docs.html">Documentation</ulink>
     1224<sect1 id="backup-commands">
     1225<title>Backup Commands and Options</title>
     1227<para>Backup Command:</para>
     1229<informaltable><tgroup cols="1"><tbody>
     1233mondoarchive &lt;-option1&gt; &lt;-option2&gt; ... &lt;-optionN&gt;
     1241<informaltable><tgroup cols="1"><tbody>
     1245bash# mondoarchive -E /mnt/dos /mnt/cdrom -9 -Oc 8
     1251<para>Would create backup CD to a CD-R disc at the highest
     1252compression level, writing at speed 2 and ignoring the /mnt/dos and
     1253/mnt/cdrom directories.</para>
     1254<para>To see a detailed list of switches and their meaning, see the
     1255<ulink url="">HTML
     1256man page</ulink> on the website or type 'man mondoarchive' at the
     1258<sect2 id="backup-cdr">
     1259<title>Standard Example With CD-R</title>
     1261<informaltable><tgroup cols="1"><tbody>
     1265bash# mondoarchive -Oc 2 -g
     1271<para>Replace '2' in '-Oc2' with the writer's speed. If
     1272mondoarchive cannot find your CD-R then please add '-d 0,0,0' (or
     1273whatever your CD writer's SCSI node is; usually, it is 0,0,0) to
     1274the call.</para>
     1275<para>Please insert the first disk in the writer while the PC is
     1276chugging away. If Mondo needs additional CD-R(W) then it will ask
     1277for them.</para>
     1279<sect2 id="backup-cdrw">
     1280<title>Standard Example With CD-RW</title>
     1282<informaltable><tgroup cols="1"><tbody>
     1286bash# mondoarchive -Ow 2 -g
     1292<para>Replace '2' in '-Ow2' with the writer's speed.</para>
     1294<sect2 id="backup-tape">
     1295        <title>Standard Example With Tape</title>
     1297<informaltable><tgroup cols="1"><tbody>
     1301bash# mondoarchive -Ot -d /dev/st0 -g
     1307<para>With previous versions of Mondo, you needed to specify the
     1308size of the tape. As of v1.51, that is no longer necessary.</para>
     1310<sect2 id="backup-failsafe">
     1311        <title>Standard Example With Failsafe kernel</title>
     1313<informaltable><tgroup cols="1"><tbody>
     1317bash# mondoarchive -k FAILSAFE -Ow 2
     1323<para>Due to slight policy differences in the Debian distribution
     1324approach, the '-k FAILSAFE' option is typically needed with
     1327<sect2 id="backup-network">
     1328        <title>Standard Example With Network Backup</title>
     1330<informaltable><tgroup cols="1"><tbody>
     1334bash# mount -t nfs /mnt/nfsbash# mondoarchive -OVn -g -s 20
     13350mbash# umount /mnt/nfs
     1341<para>The resultant ISO's can be burned to CD's if you want (which
     1342isn't a good idea unless you're a Mondo expert because they'll try
     1343to restore over a network by default, which is silly cos the
     1344archives are on the CD's). Or, you can boot from the Mindi floppies
     1345(or mondorescue.iso) and hit ENTER a few times to restore.</para>
Note: See TracChangeset for help on using the changeset viewer.