PageRenderTime 83ms CodeModel.GetById 19ms RepoModel.GetById 0ms app.codeStats 1ms

/linkedfs/usr/share/doc/helpdocs.htm

https://bitbucket.org/harakiri/trk
HTML | 3436 lines | 3329 code | 52 blank | 55 comment | 0 complexity | 4c2861db8a40a8cae313c8b03843871c MD5 | raw file
Possible License(s): GPL-2.0, MIT, LGPL-3.0 
    

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2. 

  2. <html><head>
    3. 

  3. 

  4. 

  5. <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    6. 

  6. <title>Trinity Rescue Kit  | CPR for your computer | Trinityhome | </title>
    7. 

  7. 

  8. <style type="text/css">
    9. 

  9. /* ========================================================*/
    10. 

  10. /*                              Vision.To CMS / www.vision.to                      */
    11. 

  11. /*                      SPECIAL CSS PRINT STYLE BY www.vision.to           */
    12. 

  12. /* ========================================================*/
    13. 

  13. body {
    14. 

  14.         text-align: left; /* IE Only */
    15. 

  15.         margin: 0;padding: 0;
    16. 

  16.                 color: #000;
    17. 

  17. font-family: Georgia, "Times New Roman", Times, serif;
    18. 

  18.   font-size: 12pt;
    19. 

  19. }
    20. 

  20. /*---------------------------------------------------------------*/
    21. 

  21. #print-wrapper {
    22. 

  22. margin-top:0;
    23. 

  23.         padding: 2px;
    24. 

  24.         margin-left: 0;
    25. 

  25.         margin-right: auto;
    26. 

  26.         width: 600px;
    27. 

  27.                 min-width:598px;
    28. 

  28.         border: 1px none #ddd;
    29. 

  29.         text-align: left;
    30. 

  30. background:#fff;
    31. 

  31. color:#000;
    32. 

  32. 

  33.         }
    34. 

  34.         }
    35. 

  35. 

  36. /*---------------------------------------------------------------*/
    37. 

  37. #print-header {
    38. 

  38.         /*clear: both;*/
    39. 

  39.                 border-bottom: 1px solid #ddd;
    40. 

  40.                 padding: 0.5em;
    41. 

  41.                 margin-bottom: 2px;
    42. 

  42.         }
    43. 

  43. /*---------------------------------------------------------------*/
    44. 

  44. 

  45. #print-content {
    46. 

  46.         /*float: left;*/
    47. 

  47.                 width: 100%;
    48. 

  48.         position: relative;
    49. 

  49.                 /*
    50. 

  50.         margin-left: auto;
    51. 

  51.                 margin-right: auto;
    52. 

  52.         */
    53. 

  53.                 text-align: left;
    54. 

  54.                 color:#000;
    55. 

  55.         padding: 0.5em;
    56. 

  56. min-height:650px;
    57. 

  57. height:expression(this.scrollHeight > 650 ? "auto":"650px");
    58. 

  58.         }
    59. 

  59. 

  60. /*---------------------------------------------------------------*/
    61. 

  61. #print-footer {
    62. 

  62.         text-align: center;
    63. 

  63.         color: #000;
    64. 

  64.                 margin-top: 2px;
    65. 

  65.         padding: 0.5em;
    66. 

  66.         /* line-height: 1.2em; */
    67. 

  67.         clear: both;
    68. 

  68.                 border-top: 1px solid #ddd;
    69. 

  69.         }
    70. 

  70. 

  71. .brclear {
    72. 

  72. /* Use a break with this class to clear float containers- Thank You Big John :-) positioniseverything.net */
    73. 

  73. clear:both;
    74. 

  74. height:0;
    75. 

  75. margin:0;
    76. 

  76. font-size: 1px;
    77. 

  77. line-height: 0;
    78. 

  78. }
    79. 

  79. 

  80. 

  81. </style>
    82. 

  82. <meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.1  (Unix)"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"><meta content="text/html; charset=UTF-8" http-equiv="CONTENT-TYPE"><title></title><meta content="OpenOffice.org 3.1  (Unix)" name="GENERATOR"></head><body>
    83. 

  83. <div id="print-wrapper">
    84. 

  84.   <div id="print-header">
    85. 

  85.     <h1><img src="helpdocs_files/200610190000370.gif" alt="image" class="BartsCmsImage" height="135" width="140"> Trinityhome</h1>
    86. 

  86.   </div>
    87. 

  87.   <div id="print-content">
    88. 

  88.     
    89. 

  89. <div id="page-container" class="page-container"><!-- open page-container -->
    90. 

  90. 

  91. 

  92. <h1 class="page-title">Trinity Rescue Kit  | CPR for your computer</h1>
    93. 

  93. 

  94. 

  95. 

  96. <div class="page-content">
    97. 

  97. 

  98. 

  99. 

  100. 

  101. 

  102. <a href="#K94N78PT0VFVLYYDHBV9JJ0N7EUA3RSDQMRNK66BSCW41">Getting started with TRK</a><br><a href="#E3JEBK6FCRUYGL65MT9YXJBJ20Z7EK5IEFNFQKKS25G8H">0. Quick and dirty guide to using TRK</a><br><a href="#841YA21RBZPBCRPIQGT0BYCFWYCIELPDGF1G8SY9GCAJU">0.1 The easiest way to get it onto a CD: a self burning TRK</a><br><a href="#YUU68L1SK1TXA04XDZX4MPPJJXTUJZP8J95IKX0WNJIN9">0.2 Burning TRK with Magiciso</a><br><a href="#NDQL3ZBZYMUVVWYN4348DUF9650TV0083FKX5LMUY6EJS">0.3 Booting from TRK</a><br><a href="#BL8Q8FN81J34KW4EMG9IHTQJZ2L5J22LD02C6FAXQ4S0Q">0.4 Resetting passwords</a><br><a href="#48H6PKLBPTE32K9P95Q4T4MADLMZA6W5431IEDKTWQLN0">1. TRK for Linux newbies</a><br><a href="#2FK5NB4F87EHQWYKAJWGIQZLFA53HWY9185EAZJ9XPGCA">1.1 What is TRK? What 's a live distribution?</a><br><a href="#BVJ9IR04WMV4XH1MSM34S6T8MGH4JW8KHHKQYBKKN6FBD">1.2 What is different between accessing your PC from Windows and accessing from TRK?</a><br><a href="#WQKZJKT0E8QJQM9HJZ4WTYKI5DK0ZDBLUMB3YUU2S9B7M">1.3 Getting around with common linux commands (cd, cp, mv, rm, more, grep, mount)</a><br><a href="#M69SKN1KBY3NSX3XG2DPJ306MHH6EL0SIZ9UD05EPYT7K">1.4 Reading information about your PC (dmesg, /proc/partitions)</a><br><a href="#QBRDPTSD001QIT0CN3AHZ75WRJKLINJYQ024JJ8A9ZQIH">2. TRK own commands and utils</a><br><a href="#XFPUBF4W6TFSCHXH5RXKMFAR0BVLGLR3S6NTBHF71KQ3T">2.1 Virusscan</a><br><a href="#HW79FF1ZME1FBEY6DVXDG60JAJVNKK6T64SB9I0MMSSPW">2.2 Winpass and regedit</a><br><a href="#SI14T7V9WN984HEA7MUC0E8RMGDSNVN63F0LCLKYZKWTS">2.3 Mass Clone: a multicast disk cloning tool</a><br><a href="#VZX1W3W6015LZRZ127YCKFJS9LX59AAU0YKLR6IHYETNW">2.4 Winclean</a><br><a href="#TTVJRRE5QQRJBVB2F61R719J0CHFRFVAZGJFXPBD4SM6D">2.5 Mountallfs</a><br><a href="#HH1WPPJEI4DHJTAHXPSYR3637JMCUVX22NNH2YLBSPI18">2.6 Updatetrk</a><br><a href="#DNEHBFA6ISQPQUF15A9HX1XVYX82E8LIMQQNVRJ480INJ">2.7 Trk2usb</a><br><a href="#WM8PAWXULFITSRN0X6I1YVCLB9IA41FQDD5E0TYBZ7VGP">2.8 Trk2iso</a><br><a href="#EGNT0M1F9DJ7XUB34LIEU8DXZVGDWEW0K9IAMAFLDQJ09">2.9 Fileserver</a><br><a href="#20T4DLR6P2JZL5SVUKVM5FB7MQPKJQUCFC6INMF3FQSSK">2.10 Bridge</a><br><a href="#PSTEW6D05PZF2FK7VHGLCYWQZWP8T538NMCAJF0FVPLMV">2.11 Setip</a><br><a href="#WU8QP3M0YGLR9XQ8V4MW69X4SZF6ZM1L701LTECHLNZLB">2.12 Setproxy</a><br><a href="#C3E9S86L5Q2DV4J2X7FRSW3NCGQ426N40T3HR0UMGLR1F">2.19 Ntfsundeleteall</a><br><a href="#MFRIGTQ75RPR5IIC4TXNKUF95JATHDEUIV3PEIMA01RV9">2.13 Getswap</a><br><a href="#U49HULJB0RZJRSQX054MZS1LH8P05M7QG7X0I628MRH48">2.14 Trinisup</a><br><a href="#FKJT61FZ5GVCPWKXWTXSLUF6CQM3YVP36YM2QSRKZCNEY">2.15 Pi - automated backup wrapper script originally for Partition Image</a><br><a href="#3HU5ZWWY8SYP7AEGNHT9CEDCSWG7RQEJXZELK1AJJYYGZ">2.20 Clonexp (obsoleted by mclone)</a><br><a href="#4WP777Y6KKDSK5E2140SK6QED0J74GSY26W03JWEV0X5V">3. Procedures</a><br><a href="#LIAT4IG4QYXT3EP1K2EVX276MK95G33SC3B7CH1S6NBZT">3.1 Rescueing files of dying harddiscs (mounting network =&gt; cp, ddrescue)</a><br><a href="#QVQWIA3HK45X8M47KB6N7V5KDDAWB7HSSYD1Y78814V0G">3.2 Recovering deleted files or files from formatted drives (ntfsundeleteall, photorec)</a><br><a href="#7PFVZK0Q4R5TZMDJ351RJA8VHEBE66K4KQP91EPVWKEKX">3.3 Recovering lost partitions (testdisk, gpart, fdisk)</a><br><a href="#L5ICUK4HDV6QAJA1ISR37W4DEYAHUY95TI8CT3KXNHCPR">3.4 Bootsector repair</a><br><a href="#UHPDX3JS857PC91QX5QDU7JHMFX9NFZ8NECA7MT6HQKJQ">3.5 Manually cloning a Windows installation</a><br><a href="#JVI22F4QK5AFSUR3MHQC9ZW33AWHWA05W9XNES3PN4V5N">3.6 Hardware testing</a><br><a href="#4PL88HNFBZGXK7BHVL44UCJIPXXUD8I7MU5L2JR38YRJW">3.7 Virus scanning</a><br><a href="#AKDLI8WEFV4L96NMKIKSXE2ZQWDFRHLSTQ42PQ6UB16AX">3.8 Manual PC cleaning</a><br><a href="#ZTZJTNZS1Z028YDFIX59T2IQNHU57JDW236KHV38JU1IH">4. Boot time options and triggers</a><br><a href="#Z034WGIXRNSS0HJZYHKU5ED0RRGXKGQA7I4TQDF6RYPH6">4.1 Boot menu options</a><br><a href="#EUGBVSAKSIDQ4SSW21D1CDTZC5RKS0DXKJY51ZFJ7J022">4.2 Triggers</a><br><a href="#9PAH415576DS0RB2Z5DH8AQ1XFD42G21V39QU4LS1P9S6">4.2.1 The TRK options server: make your lan TRK aware</a><br><a href="#CA4YM8MPTJ078B4RZR3V7NZDL7WUM33Q4XDGWQVE0KCZM">4.2.2 Scripts on the computer's local harddisks</a><br><a href="#B8MI3TRVGJ2SY2XHN562I89WYSUF20I4ZWCSETDL364RY">4.2.3 Script on the TRK medium</a><br><a href="#SMFWK0I2J980KIYM9IK3CSPF1J06UQ3C29YDZ75874YID">5. Upgrade, update and change of bootmedia procedures</a><br><a href="#VCMNDG08JQ9JED3YXFLITGXVHLRRQIXBL9PPFEMQUMZZR">5.1 TRK on CD</a><br><a href="#FIRS44G0F6QRJDGPU467B1R5DHKC3QV9ZCRU6XJBUZS43">5.2 How to install/upgrade your USB media to run the latest version of TRK</a><br><a href="#DJQBVW3TV8F9F6T9P2QZJ9WFCCVH0HU3SA5CWYWHX2G2Z">5.3 Setting up your PXE boot environment</a><br><a name="K94N78PT0VFVLYYDHBV9JJ0N7EUA3RSDQMRNK66BSCW41" &nbsp;="" id="K94N78PT0VFVLYYDHBV9JJ0N7EUA3RSDQMRNK66BSCW41"></a><h1>Getting started with TRK</h1><h2><span style="font-size: 10pt; font-family: Arial;"><o:p></o:p></span>Foreword and conventions of this documentation:</h2>
    103. 

  103. <h3>Consulting help</h3>
    104. 

  104. <p>-Trinity Rescue Kit 3.4 has manpages for almost every utility, even
    105. 

  105. the ones specific to TRK (new since 3.4). So if you need help on a
    106. 

  106. certain command, like f.i. Winpass, just type 'man winpass' at the
    107. 

  107. commandline. All manpages themselves are always online available at
    108. 

  108. http://trinityhome.org/manpages</p>
    109. 

  109. <p>-This helppage is also available as a single document locally on the TRK medium.  <strong>You can call on this documentation as one big page from TRK by typing 'trkhelp'</strong>
    110. 

  110. at the command prompt (or chosen from the startup menu). This will
    111. 

  111. start the builtin Links browser in graphical mode opening all of the
    112. 

  112. documentation at once. To be able to switch between this help and your
    113. 

  113. commandprompt, you must be in text mode</p>
    114. 

  114. <p>Most commands also have a built-in help. Most of the time 'command -h' or 'command –help' will help you a lot further.</p>
    115. 

  115. <p><br>
    116. 

  116. Use the key "q" to quit links and type 'trkhelp -t' to run in text
    117. 

  117. mode. Once in textmode, use alt+F2 to go the second console of TRK. In
    118. 

  118. total there are 6 consoles, each switchable with their respective alt+
    119. 

  119. function key.<br>
    120. 

  120. If you are not online, you can consult the local documentation which is on the TRK medium by entering 'trkhelp -l'. <br>
    121. 

  121. You can combine these two parameters: 'trkhelp -l -t' gets you the local helpfiles in textmode.</p>
    122. 

  122. <p>-All TRK&nbsp;manpages are also available online in html format.&nbsp;Browse them here: <a href="http://trinityhome.org/manpages/">http://trinityhome.org/manpages/</a></p>
    123. 

  123. <h3>&nbsp;<br>
    124. 

  124. Conventions</h3>
    125. 

  125. <p>-literal commands that you can execute in TRK or Linux are put
    126. 

  126. between 'single quotes'. Omit the quotes when using the real
    127. 

  127. commandline. Exceptions on these quotes will be mentionned (when single
    128. 

  128. quotes really appear in the command).<br>
    129. 

  129. <br>
    130. 

  130. -"double quotes" are used to emphasise words, unless they are used inside commands.<br>
    131. 

  131. <br>
    132. 

  132. -&lt;trkmedium&gt; stands for the rootfolder of the medium on which TRK
    133. 

  133. runs. TRK can be run from CD, usb stick/disk, fixed harddisk or from
    134. 

  134. network over PXE. These specific bootmethods will be explained later in
    135. 

  135. this document.<br>
    136. 

  136. <br>
    137. 

  137. -this documentation is intended for people who at least have some
    138. 

  138. experience with computer troubleshooting or know how to install their
    139. 

  139. own Windows. If you have absolutely no idea of this, I recommend you
    140. 

  140. call someone who knows more.</p>
    141. 

  141. <p>&nbsp;</p><br><a name="E3JEBK6FCRUYGL65MT9YXJBJ20Z7EK5IEFNFQKKS25G8H" &nbsp;="" id="E3JEBK6FCRUYGL65MT9YXJBJ20Z7EK5IEFNFQKKS25G8H"></a><h1>0. Quick and dirty guide to using TRK</h1><p>This
    142. 

  142. page is intended for the really impatient who are passing by here and
    143. 

  143. probably just want to reset a password in Windows. The procedures
    144. 

  144. assume you are using MS&nbsp;Windows.</p>
    145. 

  145. <p>I'll make sure I don't type too much text for you to read.</p>
    146. 

  146. <h2>In short...</h2>
    147. 

  147. <p>TRK&nbsp;is not a software you install on your computer in Windows
    148. 

  148. but rather a completely independent operating system based on Linux and
    149. 

  149. which runs from CD (or USB stick or network).</p>
    150. 

  150. <p>To get the latest version of TRK, go to the download page or download the latest copy here.</p>
    151. 

  151. <p>The quickest way to get you running TRK is to download and run the self-burning TRK&nbsp;version.</p>
    152. 

  152. <p>If you want to see how the self burning of TRK&nbsp;is done, see the page on <a href="https://trinityhome.org/Home/index.php?content=0.1_THE_EASIEST_WAY_TO_GET_IT_ONTO_A_CD_A_SELF_BURNING_TRK&amp;front_id=19&amp;lang=en&amp;locale=en">0.1&nbsp;Self burning TRK</a></p>
    153. 

  153. <p>Should you want to burn the iso with a 3rd party software called magiciso, see <a href="https://trinityhome.org/Home/index.php?content=0.2_BURNING_TRK_WITH_MAGICISO&amp;front_id=19&amp;lang=en&amp;locale=en">0.2&nbsp;Burning TRK&nbsp;with Magiciso</a></p>
    154. 

  154. <p>For booting from TRK, see <a href="https://trinityhome.org/Home/index.php?content=0.3_BOOTING_FROM_TRK&amp;front_id=19&amp;lang=en&amp;locale=en">0.3&nbsp;Booting from TRK</a></p>
    155. 

  155. <p>For password resetting, see <a href="https://trinityhome.org/Home/index.php?content=0.4_RESETTING_PASSWORDS&amp;front_id=19&amp;lang=en&amp;locale=en">0.4 Resetting passwords</a></p>
    156. 

  156. <p>If you know how to burn an isofile, skip section 0.1 and 0.2.</p>
    157. 

  157. <p>If you know how to boot from CD, skip section 0.3</p>
    158. 

  158. <p>For password resets, you can equally skip section 0.4 because
    159. 

  159. TRK&nbsp;3.4 now has a simple menu from which you can select whatever
    160. 

  160. you need to do.</p>
    161. 

  161. <p>&nbsp;</p><br><a name="841YA21RBZPBCRPIQGT0BYCFWYCIELPDGF1G8SY9GCAJU" &nbsp;="" id="841YA21RBZPBCRPIQGT0BYCFWYCIELPDGF1G8SY9GCAJU"></a><h1>0.1 The easiest way to get it onto a CD: a self burning TRK</h1><p>-Download and save the latest copy of the self-burning TRK, e.g. "trinity-rescue-kit.3.4-build-366.exe"</p>
    162. 

  162. <p>-Doubleclick on "trinity-rescue-kit.3.4-build-366.exe"</p>
    163. 

  163. <p>Now see the screenshots</p>
    164. 

  164. <p>&nbsp;Ok, you've put your blank CD&nbsp;in the tray, now answer yes
    165. 

  165. and see all of the next screens pass by.&nbsp;There 's no more work for
    166. 

  166. you on the burning part!</p>
    167. 

  167. <p><img src="helpdocs_files/10-selfburn-trk.jpg" alt="" height="138" hspace="5" vspace="5" width="587"></p>
    168. 

  168. <p><img src="helpdocs_files/11-selfburn-trk.jpg" alt="" hspace="5" vspace="5"></p>
    169. 

  169. <p>&nbsp;</p>
    170. 

  170. <p><img src="helpdocs_files/12-selfburn-trk.jpg" alt="" hspace="5" vspace="5"></p>
    171. 

  171. <p>&nbsp;</p>
    172. 

  172. <p><img src="helpdocs_files/13-selfburn-trk.jpg" alt="" hspace="5" vspace="5"></p>
    173. 

  173. <p>&nbsp;</p>
    174. 

  174. <p><img src="helpdocs_files/14-selfburn-trk.jpg" alt="" hspace="5" vspace="5"></p>
    175. 

  175. <p>&nbsp;...and that 's it, now boot from it.</p><br><a name="YUU68L1SK1TXA04XDZX4MPPJJXTUJZP8J95IKX0WNJIN9" &nbsp;="" id="YUU68L1SK1TXA04XDZX4MPPJJXTUJZP8J95IKX0WNJIN9"></a><h1>0.2 Burning TRK with Magiciso</h1><p>There
    176. 

  176. are many other programs that can burn ISO files to a CD. Magiciso is
    177. 

  177. just used as an example because it's one of the most easy to
    178. 

  178. use.&nbsp;An alternative might be the very lightweight <a href="http://www.terabyteunlimited.com/downloads-free-software.htm">BurnCDCC</a> or another free and full blown CD writer is <a href="http://cdburnerxp.se/">CD&nbsp;Burner XP</a>.<br>
    179. 

  179. Users from Windows 7 can just burn an ISO&nbsp;to disk without installing any additional software.</p>
    180. 

  180. <p>Remember that to install programs or run the self burning TRK, you have to be an administrator of your local computer.</p>
    181. 

  181. <p>The screenshots speak for themselves</p>
    182. 

  182. <p>1<br>
    183. 

  183. <img alt="" src="helpdocs_files/01-wwwmagicisocom.jpg" hspace="2" vspace="2"></p>
    184. 

  184. <p>2<br>
    185. 

  185. <img alt="" src="helpdocs_files/02-wwwmagicisocom.jpg" hspace="2" vspace="2"></p>
    186. 

  186. <p>3<br>
    187. 

  187. <img alt="" src="helpdocs_files/03-mi-disclaimer.jpg" hspace="2" vspace="2"></p>
    188. 

  188. <p>4<br>
    189. 

  189. <img alt="" src="helpdocs_files/04-burn1.jpg" hspace="2" vspace="2"></p>
    190. 

  190. <p>5<br>
    191. 

  191. <img alt="" src="helpdocs_files/05-open-file.jpg" hspace="2" vspace="2"></p>
    192. 

  192. <p>6<br>
    193. 

  193. <img alt="" src="helpdocs_files/06-burn2.jpg" hspace="2" vspace="2"></p>
    194. 

  194. <p>7<br>
    195. 

  195. <img alt="" src="helpdocs_files/07-burn3.jpg" hspace="2" vspace="2"></p>
    196. 

  196. <p>8<br>
    197. 

  197. <img alt="" src="helpdocs_files/07-burn4.jpg" hspace="2" vspace="2"></p><br><a name="NDQL3ZBZYMUVVWYN4348DUF9650TV0083FKX5LMUY6EJS" &nbsp;="" id="NDQL3ZBZYMUVVWYN4348DUF9650TV0083FKX5LMUY6EJS"></a><h1>0.3 Booting from TRK</h1><p>To
    198. 

  198. be able to boot from TRK, I&nbsp;can give you a few tips, but there is
    199. 

  199. never 1 uniform way on how to do it because every computer is different
    200. 

  200. and every brand has different shortcut keys.</p>
    201. 

  201. <p>In many cases, the fact that the CD with TRK&nbsp;is in your CD tray
    202. 

  202. when you boot your computer might be enough to get it booting from it.</p>
    203. 

  203. <p>In other cases, you get the option to select the bootdevice at
    204. 

  204. startup. Depending on the brand, this might be with any different
    205. 

  205. function key or even "esc" and "enter".&nbsp;Most of the time, the
    206. 

  206. power on screen tells you what key to press.</p>
    207. 

  207. <p>Ultimately you must set the bootsequence in the bios of the
    208. 

  208. computer.&nbsp;The bios is basic configuration of a computer before
    209. 

  209. even any operating system or software has been started.</p>
    210. 

  210. <p>Here 's a few screenshots I've taken from VMWare, which basically behaves like any other physical computer.</p>
    211. 

  211. <p>Here 's the initial bootsplash which lasts only a few seconds. <br>
    212. 

  212. <img src="helpdocs_files/bootsplash-vmware.png" alt="" height="480" hspace="5" vspace="5" width="640"><br>
    213. 

  213. The text speaks for itself. </p>
    214. 

  214. <p>Hitting "esc" is enough to select a temporary bootdevice. <br>
    215. 

  215. <img src="helpdocs_files/bootselection-vmware.png" alt="" height="418" hspace="5" vspace="5" width="546"></p>
    216. 

  216. <p>Alternatively if you hit F2, you can go into the bios and set the
    217. 

  217. bootsequence permanently.&nbsp;Remember that in that case when you have
    218. 

  218. a bootable CD in your tray, your PC&nbsp;will always boot from
    219. 

  219. that.&nbsp;It will also make startup slower because it will first look
    220. 

  220. for a cd and its bootability.<br>
    221. 

  221. <img src="helpdocs_files/bios-boot-vmware.png" alt="" height="480" hspace="5" vspace="5" width="640"></p>
    222. 

  222. <p>Now this is only an example for VMWare.&nbsp;Any other computer is
    223. 

  223. different in the fact that it can be any of the other function keys you
    224. 

  224. need to press to enter the bios or choose a bootdevice.&nbsp;Read the
    225. 

  225. text from the splash screen.</p>
    226. 

  226. <p>To get a better explanation on setting the bootsequence, take a look at the documentation done for Hiren's Bootcd:</p>
    227. 

  227. <p>
    228. 

  228. 

  229. 

  230.  	<style type="text/css">
    231. 

  231. 	<!--
    232. 

  232. 		@page { margin: 0.79in }
    233. 

  233. 		P { margin-bottom: 0.08in }
    234. 

  234. 		A:link { so-language: zxx }
    235. 

  235. 	-->
    236. 

  236. 	</style>   
    237. 

  237. 

  238. </p>
    239. 

  239. <p><a href="http://www.hiren.info/pages/bios-boot-cdrom">http://www.hiren.info/pages/bios-boot-cdrom</a></p>
    240. 

  240. <p>&nbsp;</p><br><a name="BL8Q8FN81J34KW4EMG9IHTQJZ2L5J22LD02C6FAXQ4S0Q" &nbsp;="" id="BL8Q8FN81J34KW4EMG9IHTQJZ2L5J22LD02C6FAXQ4S0Q"></a><h1>0.4 Resetting passwords</h1><p>Once
    241. 

  241. you 've managed to burn TRK&nbsp;to CD and set the right bootsequence,
    242. 

  242. you can start doing stuff with it, like resetting the password (that's
    243. 

  243. what you came here for didn't you?).</p>
    244. 

  244. <p>See this little <a href="https://trinityhome.org/Files/trk-screenshots/video/trk-winpass-howto-01.avi">movie</a> which runs you through it from A to Z and do some further reading on the <a href="https://trinityhome.org/Home/index.php?content=3922.2_WINPASS_AND_REGEDIT&amp;front_id=19&amp;lang=en&amp;locale=en">usage of winpass.</a></p>
    245. 

  245. <p>You will notice that once you started TRK, the simple menu that you get is self explanatory.</p>
    246. 

  246. <p>&nbsp;</p><br><a name="48H6PKLBPTE32K9P95Q4T4MADLMZA6W5431IEDKTWQLN0" &nbsp;="" id="48H6PKLBPTE32K9P95Q4T4MADLMZA6W5431IEDKTWQLN0"></a><h1>1. TRK for Linux newbies</h1><p>This
    247. 

  247. section gives a quick introduction about the concepts of Linux, a live
    248. 

  248. distribution and how you should see and control your computer from the
    249. 

  249. viewpoint of TRK</p><br><a name="2FK5NB4F87EHQWYKAJWGIQZLFA53HWY9185EAZJ9XPGCA" &nbsp;="" id="2FK5NB4F87EHQWYKAJWGIQZLFA53HWY9185EAZJ9XPGCA"></a><h1>1.1 What is TRK? What 's a live distribution?</h1><p>
    250. 

    251. 

  251. 

  252.  	<style type="text/css">
    253. 

  253. 	<!--
    254. 

  254. 		@page { margin: 0.79in }
    255. 

  255. 		P { margin-bottom: 0.08in }
    256. 

  256. 		H1 { margin-bottom: 0.08in }
    257. 

  257. 		H1.western { font-family: "Times New Roman", serif }
    258. 

  258. 		H1.cjk { font-family: "Bitstream Vera Sans" }
    259. 

  259. 		H1.ctl { font-family: "Bitstream Vera Sans" }
    260. 

  260. 	-->
    261. 

  261. 	</style> 
    262. 

  262. 

  263. </p>
    264. 

  264. <p>This is a definition for people that have absolutely no idea of what
    265. 

  265. an operating system means. If you don 't understand what I just said,
    266. 

  266. you need to read the following text. The people who do know what it all
    267. 

  267. means, might take the following definition as incorrect, but that 's
    268. 

  268. just so I can explain in simple language what I mean.<br>
    269. 

  269. <br>
    270. 

  270. “Trinity Rescue Kit" or <strong>TRK is a collection of programs that can start a computer in an alternate way if it failed to start normally.<br>
    271. 

  271. </strong><br>
    272. 

  272. TRK is a so called "live distribution" of Linux. Linux is in fact the
    273. 

  273. "brain" and "the senses" that drives your computer, all the programs
    274. 

  274. are the limbs that allow you to control it. All this put together make
    275. 

  275. up a so called operating system. Because of confusion in terminology
    276. 

  276. and because of the so many flavors, we talk about Linux being the
    277. 

  277. operating system and what makes it complete with programs is called the
    278. 

  278. distribution. And as for distributions, a lot of flavors exist
    279. 

  279. (hundreds, maybe even thousands). One of these flavors is Trinity
    280. 

  280. Rescue Kit. TRK is a "live" distribution because it can boot from
    281. 

  281. removable media, perform hardware detection on-the-fly and automate as
    282. 

  282. many configuration tasks as possible.<br>
    283. 

  283. <br>
    284. 

  284. TRK operates completely from RAM (= compare this with the short term
    285. 

  285. memory of your brain) and read-only media. This means also it doesn ‘t
    286. 

  286. touch nor change anything stored on your computer until you tell it to
    287. 

  287. do so. Another implication this will have is that by starting your
    288. 

  288. computer with Trinity Rescue Kit you have the guarantee that no viruses
    289. 

  289. that might be on your local computer can become active. In the case of
    290. 

  290. your computer running Microsoft Windows in normal circumstances, it
    291. 

  291. just is impossibe by design that a windows virus can run on TRK because
    292. 

  292. TRK is Linux.<br>
    293. 

  293. <br>
    294. 

  294. You have the possibility of using 5 different antivirus scanners with
    295. 

  295. TRK (current version of this writing: 3.4). One of them, the free open
    296. 

  296. source Clamav is integrated in the distribution, the other 4, F-prot,
    297. 

  297. Bitdefender Vexira and Avast get downloaded from the Internet when
    298. 

  298. launched. For Avast you need a free license key handy, for which you
    299. 

  299. need to<a href="http://www.avast.com/registration-free-antivirus.php"> register on their site</a>.<br>
    300. 

  300. <br>
    301. 

  301. More on what TRK is can be read on the frontpage</p>
    302. 

  302. <h1 class="western"><br>
    303. 

  303. &nbsp;</h1>
    304. 

  304. <p>&nbsp;</p><br><a name="BVJ9IR04WMV4XH1MSM34S6T8MGH4JW8KHHKQYBKKN6FBD" &nbsp;="" id="BVJ9IR04WMV4XH1MSM34S6T8MGH4JW8KHHKQYBKKN6FBD"></a><h1>1.2 What is different between accessing your PC from Windows and accessing from TRK?</h1><p>
    305. 

  305. 

  306. 

  307.  	<style type="text/css">
    308. 

  308. 	<!--
    309. 

  309. 		@page { margin: 0.79in }
    310. 

  310. 		P { margin-bottom: 0.08in }
    311. 

  311. 	-->
    312. 

  312. 	</style>Instead
    313. 

  313. of running programs on your computer using Windows, you are now
    314. 

  314. starting your computer with something completely different. Trinity
    315. 

  315. Rescue Kit is not designed to give you the same environment you get
    316. 

  316. normally, but to provide you the means and the utilities to perform
    317. 

  317. rescue and repair operations that might not be (anymore) possible on
    318. 

  318. your computer in normal Windows operation mode.<br>
    319. 

  319. <br>
    320. 

  320. Because this is Linux, you will not see your drives in the same way you
    321. 

  321. do under Windows (or DOS), but they will appear as logically assigned
    322. 

  322. devices. So instead of the C:-drive, you will get /dev/hda1 in which
    323. 

  323. ‘hda’ is your first available harddisk ('h' in hda is for ide drives,
    324. 

  324. 's' is for scsi, sata and removable drives), hda1 is the first
    325. 

  325. (primary) partition on which a filesystem may reside. The filesystem
    326. 

  326. used in general for Windows is NTFS. This stands for New Technology
    327. 

  327. FileSystem, but in the mean time the "New" in technology is already
    328. 

  328. more than 12 years old. Nevertheless, it has gotten some improvements
    329. 

  329. over the years and it is, I must admit, a good filesystem. The other
    330. 

  330. filesystem natively supported by Windows is FAT, which come in the
    331. 

  331. flavors FAT12 (for floppies), FAT16 (for small disks up to 2Gb) and
    332. 

  332. FAT32 (for bigger disks).<br>
    333. 

  333. <br>
    334. 

  334. What 's also different from Windows is that these filesystems are not
    335. 

  335. accessible by default in Linux, you have to so called "mount" them.
    336. 

  336. Where in Windows you will get a drive C: with your files on, in Linux
    337. 

  337. you have to call the command 'mount' and mount the filesystem against a
    338. 

  338. subdirectory. An example of this: let 's say your drive C: is /dev/hda1
    339. 

  339. (/dev contains the collection of device references on your system). You
    340. 

  340. have a directory /mnt0. In this case you type 'mount /dev/hda1 /mnt0'.
    341. 

  341. When you invoke the command 'mount' afterwards without any parameters,
    342. 

  342. you will see that /dev/hda1 is mounted on /mnt0. If you cd to that
    343. 

  343. directory and type 'ls' (=equivalant of 'dir' in Windows), you will get
    344. 

  344. a directory listing of what 's available on that C: drive.<br>
    345. 

  345. <br>
    346. 

  346. Now with this all explained, you should see the picture: TRK runs on
    347. 

  347. your computer but treats it as a doctor inspecting a dead body:
    348. 

  348. everything is there, but the person is not. You can now perform surgery
    349. 

  349. on the body and try to revive it.
    350. 

  350. </p>
    351. 

  351. <p>&nbsp;</p><br><a name="WQKZJKT0E8QJQM9HJZ4WTYKI5DK0ZDBLUMB3YUU2S9B7M" &nbsp;="" id="WQKZJKT0E8QJQM9HJZ4WTYKI5DK0ZDBLUMB3YUU2S9B7M"></a><h1>1.3 Getting around with common linux commands (cd, cp, mv, rm, more, grep, mount)</h1><p>
    352. 

  352. 

  353. 

  354.  	<style type="text/css">
    355. 

  355. 	<!--
    356. 

  356. 		@page { margin: 0.79in }
    357. 

  357. 		P { margin-bottom: 0.08in }
    358. 

  358. 	-->
    359. 

  359. 	</style>   
    360. 

  360. 

  361. </p>
    362. 

  362. <p>This is a small tour on commands you will find useful when working
    363. 

  363. with TRK (and Linux in general). Let 's take as a convention that
    364. 

  364. commands you have to type are put between 'single quotes'. At the
    365. 

  365. commandline you omit these quotes (unless I say not to).<br>
    366. 

  366. <br>
    367. 

  367. What I 'm going to teach here is basically how you work with files, like copying, moving, editing, etc...<br>
    368. 

  368. <br>
    369. 

  369. First, let's start with changing directories.<br>
    370. 

  370. <br>
    371. 

  371. People that have worked with the commandline in Windows or Dos will
    372. 

  372. recognize many things. The big difference with this is that directories
    373. 

  373. in Linux are separated by forward slashes instead of backslashes in
    374. 

  374. Windows. Another big difference is that Linux folders and files are
    375. 

  375. case sensitive: capitals have to be typed as capitals, otherwise the
    376. 

  376. file or folder will not be found.<br>
    377. 

  377. <br>
    378. 

  378. -<strong>cd</strong><br>
    379. 

  379. <br>
    380. 

  380. The command to change a directory (or folder how it 's called in Windows) is 'cd'<br>
    381. 

  381. f. i. you want to change to the directory /tmp you type 'cd /tmp'. If
    382. 

  382. the folder contains spaces, there are two ways you can get into them:
    383. 

  383. or you put the foldername between double quotes or you use so called
    384. 

  384. escape characters to represent the spaces.<br>
    385. 

  385. <br>
    386. 

  386. Let 's say we want to cd to the folder 'Documents and Settings' you can
    387. 

  387. type 'cd "Documents and Settings"' or 'cd Documents\ and\ Settings'
    388. 

  388. where the backslash (\) in Linux is used to 'escape' characters, i.e.
    389. 

  389. you treat the characters litterally instead of as a control character.
    390. 

  390. Enough of that.<br>
    391. 

  391. <br>
    392. 

  392. Another way of easily changing directories is by typing the first
    393. 

  393. letters of it and then pressing the tab-key. F.i. type 'cd Doc' and
    394. 

  394. press tab. The command will complete as 'cd Documents\ and\ Settings'.
    395. 

  395. If more files or folders match, the tab command will show you the
    396. 

  396. possible options left. Very nice feature, saves you lots of time and
    397. 

  397. painful fingers.<br>
    398. 

  398. <br>
    399. 

  399. -<strong>cp</strong><br>
    400. 

  400. <br>
    401. 

  401. File copying, the second thing you 'll probably need.<br>
    402. 

  402. Once you 're in the right directory, you need to be able to copy files to other locations.<br>
    403. 

  403. Here 's how to do it, together with the most important switches.<br>
    404. 

  404. Take a file called file1, located in /tmp/ and you want to copy it to
    405. 

  405. /home: simple command 'cp /tmp/file1 /home' or when you first cd-ed to
    406. 

  406. /tmp: 'cp file1 /home/'. Source-target.<br>
    407. 

  407. Suppose you want to copy multiple files, you can use a wildcard with
    408. 

  408. '*'. If /tmp contains file1 and file2 and copy them both at the same
    409. 

  409. time: 'cp /tmp/file* /home/'<br>
    410. 

  410. If you want to copy files and folders recursively, together with all the attributes, use the switch '-a'<br>
    411. 

  411. To see what gets copied while it 's busy, add the '-v' parameter too (verbose).<br>
    412. 

  412. Say /tmp contains 'file1', 'file2', a subfolder called 'testfolder'
    413. 

  413. which also contains 'file3', then perform 'cp -av /tmp/* /home' This
    414. 

  414. will copy the complete contents of /tmp, including subfolders to /home.<br>
    415. 

  415. If cp asks you to overwrite already existing files, you can force that by adding '-f' (force) to your command:<br>
    416. 

  416. 'cp -avf /tmp/* /home'<br>
    417. 

  417. <br>
    418. 

  418. -<strong>mv</strong><br>
    419. 

  419. <br>
    420. 

  420. Moving files. This is the same principle as copying files but easier, e.g.<br>
    421. 

  421. 'mv /tmp/* /home' moves all the contents, including subdirs to /home<br>
    422. 

  422. Adding the parameters -v and f moves them verbosely without prompting to overwrite existing files.<br>
    423. 

  423. <br>
    424. 

  424. -<strong>rm</strong><br>
    425. 

  425. <br>
    426. 

  426. Remove files.<br>
    427. 

  427. Remove 1 file, example: 'rm /tmp/file1'<br>
    428. 

  428. Remove files recursively, without prompting: 'rm -rf /tmp/*'<br>
    429. 

  429. <br>
    430. 

  430. -<strong>more</strong><br>
    431. 

  431. <br>
    432. 

  432. Viewing files and output of commands. This is a util you can use any
    433. 

  433. time there 's too much output coming to your screen or you need to look
    434. 

  434. into a file.<br>
    435. 

  435. E.g.: 'more /tmp/file1' shows you the contents of file1, but gives it a
    436. 

  436. page at a time. To go to the next page, press space. The arrows and
    437. 

  437. enter key scroll down line by line.<br>
    438. 

  438. You can use this command also in combination with other commands to halt their output so you can read what it says.<br>
    439. 

  439. Example: 'dmesg | more' : 'dmesg' gives you the output of your kernel
    440. 

  440. startup procedure and recent system messages, but it 's maybe about 300
    441. 

  441. lines of output. So in this case we so called "pipe" the output of
    442. 

  442. 'dmesg' to 'more' using the "|" sign. In this way I have also explained
    443. 

  443. you with an example the use of "command piping"<br>
    444. 

  444. <br>
    445. 

  445. -<strong>command piping</strong><br>
    446. 

  446. <br>
    447. 

  447. Continueing on this subject, let 's see what other uses command piping can do for us.<br>
    448. 

  448. It can be used to filter out a certain line with a specific keyword.<br>
    449. 

  449. Let 's say you want to know whether there 's a file called
    450. 

  450. Document.doc' somewhere in a subdirectory, but you don 't know which.
    451. 

  451. Then use this command from within the base directory you want to search
    452. 

  452. in: 'find ./ | grep -i document.doc' (the -i parameter upper- or
    453. 

  453. lowercase characters)<br>
    454. 

  454. You can also pipe the output of a command to a file instead of the
    455. 

  455. screen. F.i. to put the complete filelisting of a directory tree to a
    456. 

  456. file, do like this 'find ./ &gt; /tmp/filelist.txt'<br>
    457. 

  457. <br>
    458. 

  458. -<strong>editing files</strong><br>
    459. 

  459. <br>
    460. 

  460. Here 's quickly how to use vi, the most common text editor on Linux.
    461. 

  461. Beware: this does not edit Word documents or any other document format
    462. 

  462. that is in binary format.<br>
    463. 

  463. Open a file or create a new file: 'vi /tmp/file1'<br>
    464. 

  464. Move your cursor around with your arrows to the line you want to edit.<br>
    465. 

  465. To insert text, type 'i', this will put you in insert mode. To remove
    466. 

  466. text, use 'x', (go out of insert mode first with escape). To remove or
    467. 

  467. cut a complete line, use 'dd'. You can paste this line elsewhere with
    468. 

  468. 'p'.<br>
    469. 

  469. This is basically editing in vi. To save a document, go out of insert
    470. 

  470. mode and type ':wq' (colon write quit). To exit without saving: ':q!'
    471. 

  471. (colon quit exclamation mark).<br>
    472. 

  472. If you don 't like vi, you can use pico which is a bit simpler to use, but less common on the different Linux systems.<br>
    473. 

  473. <br>
    474. 

  474. -<strong>mounting filesystems</strong><br>
    475. 

  475. <br>
    476. 

  476. When working with Linux and more specifically here with Trinity Rescue
    477. 

  477. Kit, it is imperative that you understand the way you "talk" to
    478. 

  478. filesystems.<br>
    479. 

  479. Whereas Windows just assigns a driveletter to any local filesystem it
    480. 

  480. knows and finds (which is only NTFS and FAT), Linux does it all by
    481. 

  481. invoking "mount" of a filesystem against a directory where you mount it.<br>
    482. 

  482. Trinity Rescue Kit has a utility called "mountallfs" that searches for
    483. 

  483. every filesystem on the local computer's disk drives and mounts it in a
    484. 

  484. directory that has the same basename as the device where the filesystem
    485. 

  485. resides. More on that later in this documentation. In other, normal
    486. 

  486. Linux distributions, local filesystems are detected or created on
    487. 

  487. install.<br>
    488. 

  488. <br>
    489. 

  489. Let 's talk now how to perform manual mounting.<br>
    490. 

  490. Mounting can be performed with any filesystem, regardless of it being local or on the network. <br>
    491. 

  491. <br>
    492. 

  492. *<u> Mounting a local filesystem can be done like this:</u><br>
    493. 

  493. <br>
    494. 

  494. To know what device contains te filesystem you want to mount, you can
    495. 

  495. look at a file called "/proc/partitions" This will tell you the
    496. 

  496. partition lay-out of your disks, which will most likely contain
    497. 

  497. filesystems. A common "/proc/partitions" file may look like this:<br>
    498. 

  498. <br>
    499. 

  499. /dev/hda<br>
    500. 

  500. /dev/hda1<br>
    501. 

  501. /dev/hda2<br>
    502. 

  502. <br>
    503. 

  503. /dev/hda claims in fact the whole disk. Under Windows it is impossible
    504. 

  504. to create a filesystem in there, under Linux it is possible but
    505. 

  505. improbable and not recommended.<br>
    506. 

  506. Most likely you will find a filesystem on /dev/hda1 and /dev/hda2, which will be you C: and D:-drive under Windows in general.<br>
    507. 

  507. Mounting this is quite easy, in general you don 't have to give any paramters with it, Linux will detect the type of filesystem.<br>
    508. 

  508. 'mount /dev/hda1 /mnt0'<br>
    509. 

  509. <br>
    510. 

  510. Trinity Rescue Kit by default has two directories for manual mounting
    511. 

  511. of filesystems. You can create as many as you like, in as many subdirs
    512. 

  512. as you like. That 's all I 'm going to explain about local filesystem
    513. 

  513. mounting. I recommand you use "mountallfs". More on that later.<br>
    514. 

  514. <br>
    515. 

  515. * <u>Mounting network filesystems.</u><br>
    516. 

  516. <br>
    517. 

  517. This is a very interesting bit, because with Trinity Rescue Kit you
    518. 

  518. will want to evacuate your files to another computer. In TRK (and most
    519. 

  519. other Linux distributions) it is possible to talk to Windows
    520. 

  520. filesharing technology. For those who want to know the name of this
    521. 

  521. technology, it 's called SMB (=Server Message Block). TRK can act as a
    522. 

  522. client as well as a server. In this case we 're talking about TRK as a
    523. 

  523. client.<br>
    524. 

  524. <br>
    525. 

  525. Let 's say you have a running windows machine and you 've configured it
    526. 

  526. to share "myshare". If you have not configured a share, you can connect
    527. 

  527. to the c$ hidden share, but then you need to deactivate "Use simple
    528. 

  528. simple filesharing" in the folder options of your Windows explorer. But
    529. 

  529. let us take the "myshare" share.<br>
    530. 

  530. <br>
    531. 

  531. For the ease of use, it 's a good thing to create a user on your
    532. 

  532. Windows machine called "root", give him a password and make it an
    533. 

  533. administrator. But that 's not really necessary, you can also use the
    534. 

  534. local "administrator" account, this will just require you to add a
    535. 

  535. parameter to the mount command.<br>
    536. 

  536. <br>
    537. 

  537. Let 's take the case of the "myshare" share, your Windows pc has
    538. 

  538. 10.0.0.5 as ip-address (always faster to just point to the ip-address
    539. 

  539. instead of the name) and you 've created a local user called root. Then
    540. 

  540. here 's the command: 'mount //10.0.0.5/myshare /mnt0'<br>
    541. 

  541. <br>
    542. 

  542. You will get prompted for a password in if no output is given, your
    543. 

  543. share should appear under /mnt0. Make sure "myshare" has enough
    544. 

  544. permissions for the user "root"<br>
    545. 

  545. <br>
    546. 

  546. If you don't want to create a user, you don 't want to create a share
    547. 

  547. and you did disable simple filesharing (or your windows machine is
    548. 

  548. member of a domain), you can go ahead like this:<br>
    549. 

  549. 'mount -o username=administrator //10.0.0.5/c$ /mnt0' , which will
    550. 

  550. prompt for the password an give you the credentials of "administrator".
    551. 

  551. You can already pass the password (e.g. blahblah) in the commandline if
    552. 

  552. nobody is looking over your shoulder: 'mount -o
    553. 

  553. username=administrator,password=blahblah //10.0.0.5/c$ /mnt0'<br>
    554. 

  554. <br>
    555. 

  555. Below is a screenshot of a Windows PC that has opened the disk of a remote TRK booted machine.</p>
    556. 

  556. <p><br>
    557. 

  557. <img alt="" src="helpdocs_files/fileserver-explorer.png" height="600" hspace="5" width="800"></p>
    558. 

  558. <p>&nbsp;</p>
    559. 

  559. <p>&nbsp;</p><br><a name="M69SKN1KBY3NSX3XG2DPJ306MHH6EL0SIZ9UD05EPYT7K" &nbsp;="" id="M69SKN1KBY3NSX3XG2DPJ306MHH6EL0SIZ9UD05EPYT7K"></a><h1>1.4 Reading information about your PC (dmesg, /proc/partitions)</h1><p>
    560. 

  560. 

  561. 

  562.  	<style type="text/css">
    563. 

  563. 	<!--
    564. 

  564. 		@page { margin: 0.79in }
    565. 

  565. 		P { margin-bottom: 0.08in }
    566. 

  566. 	-->
    567. 

  567. 	</style>Let 's summarize a little what 's already been said and look at reading info on your computer.<br>
    568. 

  568. <br>
    569. 

  569. -<strong>/proc</strong><br>
    570. 

  570. <br>
    571. 

  571. Standard Linux always has a filesystem called "proc", which is a
    572. 

  572. virtual filesystem in which files reside that have to do with your
    573. 

  573. hardware and running processes. It 's a wonderful invention. We already
    574. 

  574. talked about /proc/partitions, which is a file containing all local
    575. 

  575. disk partitions.<br>
    576. 

  576. <br>
    577. 

  577. Another interesting file is /proc/cpuinfo, which gives you information about your CPUs<br>
    578. 

  578. <br>
    579. 

  579. /proc/meminfo gives you information about the memory usage. Don 't let
    580. 

  580. yourself get misled by the Memfree line, which will always look very
    581. 

  581. low. Actually, Linux always reserves most part of the memory so it can
    582. 

  582. make use of it in a fast way. What you need to look at is the Active
    583. 

  583. and Inactive. The maximum amount of memory you will see will never be
    584. 

  584. more than 4Gb, since the TRK kernel needs to keep maximum compatibility<br>
    585. 

  585. <br>
    586. 

  586. Another useful file to read info on your cdrom drive is /proc/sys/dev/cdrom/info.<br>
    587. 

  587. <br>
    588. 

  588. Those are about the important files in /proc you need to know about now.<br>
    589. 

  589. <br>
    590. 

  590. -<strong>dmesg</strong><br>
    591. 

  591. <br>
    592. 

  592. The command "dmesg" gives you your kernel messages. Any hardware
    593. 

  593. detected will give you a message somewhere in the output of this
    594. 

  594. command. If you want to know the type of network card that has been
    595. 

  595. detected, perform 'dmesg|more' and look for any mentions of eth0,
    596. 

  596. eth1,...<br>
    597. 

  597. <br>
    598. 

  598. What type of harddisk controller you have: dmesg. Just use it when you
    599. 

  599. find yourself stuck on hardware questions. Also disk failures will be
    600. 

  600. visible with this command. Network errors, link down, etc, one command.<br>
    601. 

  601. <br>
    602. 

  602. Another way of looking at this information is through /var/log/messages
    603. 

  603. (more /var/log/messages), which on normal Linux distributions contain
    604. 

  604. output logs of previous boots too.<br>
    605. 

  605. <br>
    606. 

  606. To know what device your newly inserted USB stick has, plug it in, let
    607. 

  607. it settle for a few seconds and then run dmesg again. Or just run
    608. 

  608. 'dmesg|tail' to see only the last added lines.<br>
    609. 

  609. Here 's an excerpt of what you might read from dmesg. It tells you something about your network card:<br>
    610. 

  610. <font face="Courier New"><font size="2">eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html<br>
    611. 

  611. eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin &lt;saw@saw.sw.com.sg&gt; and others<br>
    612. 

  612. ACPI: PCI Interrupt 0000:05:08.0[A] -&gt; GSI 20 (level, low) -&gt; IRQ 16<br>
    613. 

  613. eth0: OEM i82557/i82558 10/100 Ethernet, 00:08:02:C6:4E:9D, IRQ 16.<br>
    614. 

  614. Board assembly 262285-001, Physical connectors present: RJ45<br>
    615. 

  615. Primary interface chip i82555 PHY #1.<br>
    616. 

  616. General self-test: passed.<br>
    617. 

  617. Serial sub-system self-test: passed.<br>
    618. 

  618. Internal registers self-test: passed.<br>
    619. 

  619. ROM checksum self-test: passed (0x04f4518b).</font></font><br>
    620. 

  620. <br>
    621. 

  621. -<strong>lspci and lsusb</strong><br>
    622. 

  622. <br>
    623. 

  623. This gives you any information on what 's on your PCI and respectively
    624. 

  624. USB bus. This doesn 't only mean what 's in your PCI slots, but
    625. 

  625. everything on the bus, so also onboard ethernet and usb controllers.
    626. 

  626. </p>
    627. 

  627. <p>
    628. 

  628. 

  629. <strong>-lshw</strong>
    630. 

  630. 

  631. </p>
    632. 

  632. <p>Now here 's a great utility that can give you a complete listing of
    633. 

  633. all your hardware, recognised and not recognised. When you run it, it
    634. 

  634. will give you a LOT&nbsp;of output, so best here is to run it 'lshw |
    635. 

  635. more', or if you only need specific info about f.i. disk drives, you
    636. 

  636. can run 'lshw -C&nbsp;DISK'. Getting the info off your TRK can be done
    637. 

  637. directly to the interweb (provided your network card got detected) by
    638. 

  638. running 'lshw | wgetpaste', which will publish the output on
    639. 

  639. http://pastebin.ca and return you a short url to where it can be found.</p>
    640. 

  640. <p>
    641. 

  641. 

  642. <br>
    643. 

  643. -<strong>smartctl</strong><br>
    644. 

  644. <br>
    645. 

  645. The smartmontools are part of Trinity Rescue Kit and not so common on
    646. 

  646. normal Linux systems, yet they are a valuable addition to any system.
    647. 

  647. What it does is read the s.m.a.r.t. information of disk drives so you
    648. 

  648. can know when errors start to occur.<br>
    649. 

  649. <br>
    650. 

  650. Just use it like this: 'smartctl -a /dev/sda' where sda is your first
    651. 

  651. scsi or sata drive. Make sure smart is enabled in the computer's bios.<br>
    652. 

  652. <br>
    653. 

  653. -<strong>acpi and acpitool</strong><br>
    654. 

  654. <br>
    655. 

  655. Two tools to read the battery and thermal information of your computer. Type acpi --help to get more info on possible options.<br>
    656. 

  656. <br>
    657. 

  657. acpitool can give you much more information like fan speeds and cpu.
    658. 

  658. Also certain laptop types are supported for their special features like
    659. 

  659. brigthness on Asus laptops etc...<br>
    660. 

  660. <br>
    661. 

  661. -<strong>df and du</strong><br>
    662. 

  662. <br>
    663. 

  663. Two standard utils provided in Linux. df shows you the usage of your
    664. 

  664. mounted filesystems, du shows you the usage of a specific folder. Use
    665. 

  665. it like 'df -h' and 'du -h' where "-h" stands for "human readable",
    666. 

  666. making the output rounded to mega- and gigabytes.<br>
    667. 

  667. This is in short how you can get to know your computer a little and how to jumpstart using Linux and Trinity Rescue Kit.<br>
    668. 

  668. <br>
    669. 

  669. <strong>-lshw</strong><br>
    670. 

  670. <br>
    671. 

  671. Recently recommended and added, but looks very promising, lshw gives
    672. 

  672. you a complete list of all your hardware in your computer. Best to pipe
    673. 

  673. this to a file, because the list can get long.
    674. 

  674. </p>
    675. 

  675. <p>&nbsp;</p><br><a name="QBRDPTSD001QIT0CN3AHZ75WRJKLINJYQ024JJ8A9ZQIH" &nbsp;="" id="QBRDPTSD001QIT0CN3AHZ75WRJKLINJYQ024JJ8A9ZQIH"></a><h1>2. TRK own commands and utils</h1><p>Let 's look at the added value of Trinity Rescue Kit, with its own specific commands and utils.</p><br><a name="XFPUBF4W6TFSCHXH5RXKMFAR0BVLGLR3S6NTBHF71KQ3T" &nbsp;="" id="XFPUBF4W6TFSCHXH5RXKMFAR0BVLGLR3S6NTBHF71KQ3T"></a><h1>2.1 Virusscan</h1><p>
    676. 

    677. 

  677. 

  678.  	<style type="text/css">
    679. 

  679. 	<!--
    680. 

  680. 		@page { margin: 0.79in }
    681. 

  681. 		P { margin-bottom: 0.08in }
    682. 

  682. 		H1 { margin-bottom: 0.08in }
    683. 

  683. 		H1.western { font-family: "Times New Roman", serif }
    684. 

  684. 		H1.cjk { font-family: "Bitstream Vera Sans" }
    685. 

  685. 		H1.ctl { font-family: "Bitstream Vera Sans" }
    686. 

  686. 		H2 { margin-bottom: 0.08in }
    687. 

  687. 		A:link { so-language: zxx }
    688. 

  688. 	-->
    689. 

  689. 	</style>
    690. 

  690. 

  691. </p>
    692. 

  692. <p>Virusscan is a script that actually wraps 5 different virusscanners into one. <br>
    693. 

  693. Only one of them is actually included on the TRK cd (Clamav), the others are downloaded from their website upon usage.</p>
    694. 

  694. <p>When running virusscan, it is highly recommended that your computer
    695. 

  695. has a decent internet connection so you can get the latest virus
    696. 

  696. signatures.</p>
    697. 

  697. <h2>Scan engines</h2>
    698. 

  698. <p style="margin-bottom: 0in;">Currently, 5 AV engines and md5 file checksumming are implemented.</p>
    699. 

  699. <h3>-ClamAV</h3>
    700. 

  700. <p>This is the basic engine provided and is already preinstalled on
    701. 

  701. TRK. It is very effective on mailservers but is quite slow and tends to
    702. 

  702. crash when used as a commandline scanner. It also focuses more on
    703. 

  703. mailworms and, from experience, has less effectiveness for local viri.
    704. 

  704. Clamav is the only GPL licensed AV engine implemented. All others have
    705. 

  705. some sort of free-for-non-commercial-use license and are closed source.
    706. 

  706. The pros of Clamav are: <br>
    707. 

  707. * very quick on new virus outbreaks <br>
    708. 

  708. * included in TRK <br>
    709. 

  709. * GPL licensed, so free for everyone <br>
    710. 

  710. The cons: <br>
    711. 

  711. * slow and very CPU and memory intensive <br>
    712. 

  712. * detects the least viri of the 5 scanners in virusscan. <br>
    713. 

  713. <br>
    714. 

  714. Because it's in fact a mailserver scanner, it will focus more on worms
    715. 

  715. than on filth that comes from malicious websites and such. <br>
    716. 

  716. * cannot disinfect inside files on its own. What is done in this case
    717. 

  717. is quarantine the infected files into a tar.gz archive in
    718. 

  718. &lt;scandestination&gt;/TRK-INFECTED/. Should a file be accidentally
    719. 

  719. deleted, you can recover it afterwards and rescan it with another
    720. 

  720. antivirustool</p>
    721. 

  721. <h3>-F-Prot</h3>
    722. 

  722. <p>This antivirus tool and all the others are not included in TRK but
    723. 

  723. get downloaded from the Internet as soon as you call upon them. They
    724. 

  724. disappear after a reboot of TRK. If you want them to be available after
    725. 

  725. a reboot, you have to run updatetrk. This will be explained later in
    726. 

  726. this documentation. The pros of F-prot: <br>
    727. 

  727. * lightweight, not a big download <br>
    728. 

  728. * pretty fast, low cpu usage <br>
    729. 

  729. * good disinfection method <br>
    730. 

  730. The cons: <br>
    731. 

  731. * does not detect everything <br>
    732. 

  732. * their website sometimes fails and download of f-prot is aborted</p>
    733. 

  733. <h3>-BitDefender Scanner</h3>
    734. 

  734. <p>It has a good average between filesize, cpu/memory load and
    735. 

  735. virusdetection. It can detect many different types of malware. From
    736. 

  736. what has been experienced so far, it may detect other viri and malware
    737. 

  737. than the other 4. It's recommended to sweep with this after another one
    738. 

  738. has already run. <br>
    739. 

  739. Pros of BitDefender Scanner: <br>
    740. 

  740. * detects quite some viri <br>
    741. 

  741. * pretty fast <br>
    742. 

  742. * detects alternate malware <br>
    743. 

  743. Cons: <br>
    744. 

  744. * sometimes doesn't detect very common viri <br>
    745. 

  745. * slow update process</p>
    746. 

  746. <h3>-Vexira</h3>
    747. 

  747. <p>This AV engine hasn't been tested so much, but it looks like a good average AV engine.</p>
    748. 

  748. <h3>-Avast</h3>
    749. 

  749. <p>Avast is the latest addition to virusscan (and replaces Grisoft AVG
    750. 

  750. because AVG lacks cleaning support in its new version). Avast is a
    751. 

  751. great AV on Windows, very lightweight, but has not been tested in depth
    752. 

  752. yet on Linux/TRK. <br>
    753. 

  753. For this particular AV engine you need a registered, free license key which is sent to you by mail. <br>
    754. 

  754. Get it at <a href="http://www.avast.com/registration-free-antivirus.php">http://www.avast.com/registration-free-antivirus.php</a> <br>
    755. 

  755. If you want to avoid entering the license key each time, it's recommened to run updatetrk</p>
    756. 

  756. <h3>-MD5</h3>
    757. 

  757. <p>This is not an antivirus engine but just reads all of your files and
    758. 

  758. makes md5sums of it. It writes the result to a logfile in the same way
    759. 

  759. like it does for an AV engine. The logfile format is: modification
    760. 

  760. seconds since 1-1-1970 &lt;space&gt; md5sum &lt;space&gt; filepath.</p>
    761. 

  761. <p>&nbsp;</p>
    762. 

  762. <p>To get complete and up to date info, please check out the online version of the manpage for virusscan: <a href="http://trinityhome.org/manpages/man8/virusscan.8.html">http://trinityhome.org/manpages/man8/virusscan.8.html</a></p>
    763. 

  763. <p><br>
    764. 

  764. &nbsp;</p>
    765. 

  765. <p>&nbsp;</p><br><a name="HW79FF1ZME1FBEY6DVXDG60JAJVNKK6T64SB9I0MMSSPW" &nbsp;="" id="HW79FF1ZME1FBEY6DVXDG60JAJVNKK6T64SB9I0MMSSPW"></a><h1>2.2 Winpass and regedit</h1><p>
    766. 

  766. 

  767. 

  768.  	<style type="text/css">
    769. 

  769. 	<!--
    770. 

  770. 		@page { margin: 0.79in }
    771. 

  771. 		P { margin-bottom: 0.08in }
    772. 

  772. 		H2 { margin-bottom: 0.08in }
    773. 

  773. 		A:link { so-language: zxx }
    774. 

  774. 	-->
    775. 

  775. 	</style>
    776. 

  776. 

  777. </p>
    778. 

  778. <p style="margin-bottom: 0in;">Winpass is a bash wrapper script for <strong>chntpw </strong>supplied with Trinity Rescue Kit that resets MS Windows NT based local passwords.</p>
    779. 

  779. <p>By default winpass without any arguments will reset the builtin
    780. 

  780. administrator account of a locally installed Windows, but you can
    781. 

  781. specify other accounts as well at the commandline. In fact, you can add
    782. 

  782. any parameter from chntpw which will be parsed to the commandline. So
    783. 

  783. winpass -l will list all usernames found in the SAM (=Windows user and
    784. 

  784. password database). Should you have troubles that metacharacters are
    785. 

  785. present in the username (such as the Ø or something), you can still
    786. 

  786. use the HEX reference to the username listed next to it. Be sure to
    787. 

  787. prepend that with a '0x'. More info on that can be found in the chntpw
    788. 

  788. manual.</p>
    789. 

  789. <p>Winpass does not reset any Active Directory passwords</p>
    790. 

  790. <dl>
    791. 

  791.     <dt>-l</dt>
    792. 

  792.     <dd> 	list usernames contained in the SAM of the local computer and exit  	</dd>
    793. 

  793.     <dt> 	-i</dt>
    794. 

  794.     <dd> 	interactively run chntpw. This option lists the local usernames and 	gives you the option to choose from them  	</dd>
    795. 

  795.     <dt> 	-e, regedit</dt>
    796. 

  796.     <dd> 	run as registry editor. To get a list of commands in the editor, 	type "?"  	</dd>
    797. 

  797.     <dt> 	-u "username"</dt>
    798. 

  798.     <dd>
    799. 

  799. optional username if the user you wish to reset is not "Administrator".
    800. 

  800. Be sure to add quotes for the username if it contains whitespaces </dd>
    801. 

  801.     <dt> 	--restore</dt>
    802. 

  802.     <dd style="margin-bottom: 0.2in;">
    803. 

  803. restore the original SAM file, thus restoring the original
    804. 

  804. password/user situation from before the first time winpass was ever
    805. 

  805. run. Should you somehow have messed up the user accounts, you can go
    806. 

  806. back to the original situation with this option. Since build 338 the
    807. 

  807. option to overwrite the backup when winpass is run multiple times has
    808. 

  808. been disabled to prevent yes-men users answering yes to every question
    809. 

  809. being asked. Removing the backup must now be done manually. You can
    810. 

  810. find it in general under /sda1/WINDOWS/system32/config/SAM </dd>
    811. 

  811. </dl>
    812. 

  812. <p>&nbsp;</p>
    813. 

  813. <h2>Example:</h2>
    814. 

  814. <p>Here's an example of resetting the password for user "John Doe". Note the double quotes around the username.</p>
    815. 

  815. <p>[root@trk]:(~)# <b>winpass -u "John Doe"</b> <br>
    816. 

  816. Searching and mounting all filesystems on local machine <br>
    817. 

  817. Remounting NTFS partitions with ntfs-3g <br>
    818. 

  818. Result of mounting: <br>
    819. 

  819. /dev/hda1 on /hda1 type fuseblk (rw,allow_other,blksize=4096) <br>
    820. 

  820. Windows NT/2K/XP installation(s) found in: <br>
    821. 

  821. 1: /hda1/WINDOWS <br>
    822. 

  822. Make your choice or 'q' to quit [1]: <b>1</b> <br>
    823. 

  823. Ok, continue <br>
    824. 

  824. chntpw version 0.99.6 080526 (sixtyfour), (c) Petter N Hagen <br>
    825. 

  825. Hive &lt;SAM&gt; name (from header): &lt;\SystemRoot\System32\Config\SAM&gt; <br>
    826. 

  826. ROOT KEY at offset: 0x001020 * Subkey indexing type is: 666c <br>
    827. 

  827. Page at 0x8000 is not 'hbin', assuming file contains garbage at end <br>
    828. 

  828. File size 262144 [40000] bytes, containing 7 pages (+ 1 headerpage) <br>
    829. 

  829. Used for data: 317/24808 blocks/bytes, unused: 6/3640 blocks/bytes.</p>
    830. 

  830. <p><br>
    831. 

  831. Hive &lt;SECURITY&gt; name (from header): &lt;\SystemRoot\System32\Config\SECURITY&gt; <br>
    832. 

  832. ROOT KEY at offset: 0x001020 * Subkey indexing type is: 666c <br>
    833. 

  833. Page at 0x10000 is not 'hbin', assuming file contains garbage at end <br>
    834. 

  834. File size 262144 [40000] bytes, containing 15 pages (+ 1 headerpage) <br>
    835. 

  835. Used for data: 1108/53920 blocks/bytes, unused: 11/7040 blocks/bytes.</p>
    836. 

  836. <p><br>
    837. 

  837. &nbsp;</p>
    838. 

  838. <p><br>
    839. 

  839. * SAM policy limits: <br>
    840. 

  840. Failed logins before lockout is: 3 <br>
    841. 

  841. Minimum password length : 7 <br>
    842. 

  842. Password history count : 7 <br>
    843. 

  843. | RID -|---------- Username ------------| Admin? |- Lock? --| <br>
    844. 

  844. | 01f4 | Administrator | ADMIN | | <br>
    845. 

  845. | 03eb | ASPNET | ADMIN | | <br>
    846. 

  846. | 01f5 | Guest | ADMIN | dis/lock | <br>
    847. 

  847. | 03e8 | HelpAssistant | | dis/lock | <br>
    848. 

  848. | 03f0 | John Doe | ADMIN | | <br>
    849. 

  849. | 03ea | SUPPORT_388945a0 | | dis/lock |</p>
    850. 

  850. <p><br>
    851. 

  851. ---------------------&gt; SYSKEY CHECK &lt;----------------------- <br>
    852. 

  852. SYSTEM SecureBoot : -1 -&gt; Not Set (not installed, good!) <br>
    853. 

  853. SAM Account\F : 1 -&gt; key-in-registry <br>
    854. 

  854. SECURITY PolSecretEncryptionKey: 1 -&gt; key-in-registry <br>
    855. 

  855. Syskey not installed!</p>
    856. 

  856. <p><br>
    857. 

  857. RID : 1008 [03f0] <br>
    858. 

  858. Username: John Doe <br>
    859. 

  859. fullname: John Doe <br>
    860. 

  860. comment : <br>
    861. 

  861. homedir :</p>
    862. 

  862. <p><br>
    863. 

  863. User is member of 2 groups: <br>
    864. 

  864. 00000221 = Users (which has 4 members) <br>
    865. 

  865. 00000220 = Administrators (which has 7 members)</p>
    866. 

  866. <p><br>
    867. 

  867. Account bits: 0x0010 = <br>
    868. 

  868. [ ] Disabled | [ ] Homedir req. | [ ] Passwd not req. | <br>
    869. 

  869. [ ] Temp. duplicate | [X] Normal account | [ ] NMS account | <br>
    870. 

  870. [ ] Domain trust ac | [ ] Wks trust act. | [ ] Srv trust act | <br>
    871. 

  871. [ ] Pwd don't expir | [ ] Auto lockout | [ ] (unknown 0x08) | <br>
    872. 

  872. [ ] (unknown 0x10) | [ ] (unknown 0x20) | [ ] (unknown 0x40) |</p>
    873. 

  873. <p><br>
    874. 

  874. Failed login count: 0, while max tries is: 3 <br>
    875. 

  875. Total login count: 0</p>
    876. 

  876. <p><br>
    877. 

  877. - - - - User Edit Menu: <br>
    878. 

  878. <br>
    879. 

  879. 1-Clear(blank)userpassword <br>
    880. 

  880. <br>
    881. 

  881. 2-Edit(setnew)userpassword(carefulwiththisonXPorVista) <br>
    882. 

  882. <br>
    883. 

  883. 3-Promoteuser(makeuseranadministrator) <br>
    884. 

  884. (4 - Unlock and enable user account) [seems unlocked already] <br>
    885. 

  885. <br>
    886. 

  886. q-Quiteditinguser,backtouserselect <br>
    887. 

  887. Select: [q] &gt; <b>1</b> <br>
    888. 

  888. Password cleared!</p>
    889. 

  889. <p><br>
    890. 

  890. Hives that have changed: <br>
    891. 

  891. <br>
    892. 

  892. #Name <br>
    893. 

  893. <br>
    894. 

  894. 0&lt;SAM&gt;-OK</p>
    895. 

  895. <p><br>
    896. 

  896. Backup file already exists. Not touching this file. Please be aware
    897. 

  897. that 'winpass --restore' would restore the very original file from
    898. 

  898. before winpass was ever run <br>
    899. 

  899. Writing /hda1/WINDOWS/system32/config/SAM <br>
    900. 

  900. [root@trk]:(~)#</p>
    901. 

  901. <p style="margin-bottom: 0in;">&nbsp;</p>
    902. 

  902. <p>For the full documentation, refer to the online manpage:</p>
    903. 

  903. <p><a href="http://trinityhome.org/manpages/man8/winpass.8.html">http://trinityhome.org/manpages/man8/winpass.8.html</a></p>
    904. 

  904. <h2><font size="6">regedit</font></h2>
    905. 

  905. <p>This is actually the same script as winpass, but called in this way
    906. 

  906. it copies all registry hives and opens them (sam, security, system and
    907. 

  907. software). Only drawback is that it cannot know which user registry to
    908. 

  908. open, since they are located in different directories. Because chntpw
    909. 

  909. is not scriptable, I cannot read registry hives from a shell script to
    910. 

  910. determine the location of userhives.<br>
    911. 

  911. <br>
    912. 

  912. Once running, refer to the <a href="http://home.eunet.no/pnordahl/ntpasswd/faq.html">documentation of chntpw/regedit</a> on how to use it.<br>
    913. 

  913. <br>
    914. 

  914. <br>
    915. 

  915. &nbsp;</p>
    916. 

  916. <p>&nbsp;</p><br><a name="SI14T7V9WN984HEA7MUC0E8RMGDSNVN63F0LCLKYZKWTS" &nbsp;="" id="SI14T7V9WN984HEA7MUC0E8RMGDSNVN63F0LCLKYZKWTS"></a><h1>2.3 Mass Clone: a multicast disk cloning tool</h1><p>
    917. 

  917. 

  918. 

  919.  	<style type="text/css">
    920. 

  920. 	<!--{12802443353150}-->
    921. 

  921. 	</style>           
    922. 

  922. 

  923. </p>
    924. 

  924. <p style="margin-bottom: 0in;">Mclone or Mass Clone is a utility that creates and distributes harddisk images over the network via multicast. <br>
    925. 

  925. It is very fast since it uses only one network packet for an infinite
    926. 

  926. number of receivers. On a 100mbit switch it will average at about
    927. 

  927. 93mbit. The only limitation here is the speed of the network, disk or
    928. 

  928. cpu. <br>
    929. 

  929. Main features: <br>
    930. 

  930. -make exact copies of any operating system <br>
    931. 

  931. -optimized for Windows XP/Vista/Seven imaging using ntfsclone. Other filesystems are copied with dd <br>
    932. 

  932. -fast and scalable <br>
    933. 

  933. -save to image and restore from image (to multicast) with optional 3 compression algorythms (gzip, bzip2 and 7-zip) <br>
    934. 

  934. -restore original bootsector/ntfs c/h/s values. An old bug in many
    935. 

  935. BIOSes sometimes gave wrong values for Cylinders/Heads/Sectors count.
    936. 

  936. Although CHS is an old method for assigning disk geometry (LBA should
    937. 

  937. be used), Windows XP and family still use it to assign addressing of
    938. 

  938. their bootcode. Recent Linux kernels discard wrong C/H/S values and set
    939. 

  939. it to the LBA values. This resulted sometimes in unbootable cloned
    940. 

  940. Windows machines (the blinking cursor nightmare). Recently a patched
    941. 

  941. version of relocntfs appeared (now called ntfsreloc) which is able to
    942. 

  942. "force" original C/H/S values into your NTFS. Mclone does it
    943. 

  943. automatically for you. Major feature over other cloning tools. <br>
    944. 

  944. -run up to 50 different sessions separately over your LAN <br>
    945. 

  945. -optional speed limitation. Just so your LAN doesn't get saturated. <br>
    946. 

  946. -option to specify disks/partitions instead of just everything automatically <br>
    947. 

  947. -option to skip bootsector <br>
    948. 

  948. -option to skip C/H/S check</p>
    949. 

  949. <p>Since TRK is network bootable from another TRK without any
    950. 

  950. modifications to your LAN's config, you could just boot one TRK from
    951. 

  951. CD/usb stick, boot all your other computers over the network and run
    952. 

  952. mclone on all of them.</p>
    953. 

  953. <p>An average image of about 4Gb on a 100mbit network is cloned in about 7 minutes</p>
    954. 

  954. <h2>USAGE</h2>
    955. 

  955. <p>In short: the computer to be cloned (the sender) runs 'mclone -s', all others run 'mclone' (the receivers). <br>
    956. 

  956. Once all computers are ready and waiting, just press enter on one of them and cloning begins.</p>
    957. 

  957. <p>You can also save to an image file. The computer that will save the image as a set of files runs mclone with the option -o. <br>
    958. 

  958. For example:</p>
    959. 

  959. <p>mclone -o standard-xp-install</p>
    960. 

  960. <p>will save an uncompressed image to "standard-xp-install", creating
    961. 

  961. it as a directory in the current directory if it does not exist. <br>
    962. 

  962. The command:</p>
    963. 

  963. <p>mclone -C 7-zip -o standard-xp-install</p>
    964. 

  964. <p>will add 7-zip compression to the image. But beware of compression.
    965. 

  965. I've noticed that gzip is the only compressor that doesn't eat too much
    966. 

  966. of your CPU so not to lose transfer speed. If size is more important to
    967. 

  967. you, use bzip2 or 7-zip <br>
    968. 

  968. In all of these cases you run 'mclone -s' on the computer from which you wish to create an image. (The Sender.) <br>
    969. 

  969. Restoring from this recently created image is done with:</p>
    970. 

  970. <p>mclone -i standard-xp-install</p>
    971. 

  971. <p>No need to specify the compression anymore, mclone will use the correct decompressor. <br>
    972. 

  972. So remember: <br>
    973. 

  973. -o mode and 'mclone' without arguments is a receiving mode, so the
    974. 

  974. other side must run mclone -s (sender mode) -i and -s mode are sender
    975. 

  975. mode, the other side runs 'mclone' as a receiver</p>
    976. 

  976. <p>Here are all the options that you can specify.</p>
    977. 

  977. <p>The command: mclone without any arguments runs in client mode, meaning it will RECEIVE an image from a sender</p>
    978. 

  978. <dl>
    979. 

  979.     <dt>-s</dt>
    980. 

  980.     <dd> 	SENDER mode. This mode will send the contents of the local harddisks 	to listening clients <br>
    981. 

  981.     e.g.: The sender runs 'mclone -s', the 	clients run 'mclone'. The sender will clone a one to many copy of 	itself  	</dd>
    982. 

  982.     <dt> 	-o &lt;path-to-image&gt;  	</dt>
    983. 

  983.     <dd>
    984. 

  984. This mode is a RECEIVER mode that stores an image from a sender to
    985. 

  985. image files in the path specified by the argument 'path-to-image' <br>
    986. 

  986. e.g.: 'mclone -o /data/xp-image'. Note: the dir does not need to exist,
    987. 

  987. but please erase it if an image is already in there. </dd>
    988. 

  988.     <dt> 	-i &lt;path-to-image&gt;</dt>
    989. 

  989.     <dd style="margin-bottom: 0.2in;"> 	This is a SENDER mode that sends an image to clients. You first need 	to have an image created with mclone -o of course.  	</dd>
    990. 

  990.     <dd style="margin-bottom: 0.2in;"> 	e.g.: 'mclone -i /data/xp-image'  	</dd>
    991. 

  991.     <dt> 	-n &lt;session number&gt;</dt>
    992. 

  992.     <dd style="margin-bottom: 0.2in;"> 	Specify as many as 50 sessions when performing multiple cloning. 	Client and sender need to specify the same number  	</dd>
    993. 

  993.     <dd style="margin-bottom: 0.2in;"> 	e.g.: 'mclone -n 5' for client, 'mclone -s -n 5' for sender  	</dd>
    994. 

  994.     <dt> 	-h</dt>
    995. 

  995.     <dd style="margin-bottom: 0.2in;"> 	short help screen  	</dd>
    996. 

  996.     <dt style="margin-bottom: 0.2in;"> 	Optional arguments <b>ONLY FROM SENDER MODE</b>:</dt>
    997. 

  997.     <dt> 	-d &lt;disks&gt;</dt>
    998. 

  998.     <dd> 	Skip disk detection and specify your own (comma separated if more 	than one). Only valid for SENDER mode (-s). <br>
    999. 

  999.     e.g.: 'mclone -s -d 	/dev/sda,/dev/sdc'  	</dd>
    1000. 

  1000.     <dt> 	-p &lt;partitions&gt;</dt>
    1001. 

  1001.     <dd> 	Skip partition detection and specify your own (comma separated if 	more than one.) Only valid for SENDER mode (-s). <br>
    1002. 

  1002.     e.g.: 'mclone 	-s -p /dev/sda1,/dev/sda2'  	</dd>
    1003. 

  1003.     <dt> 	-c</dt>
    1004. 

  1004.     <dd>
    1005. 

  1005. Skip C/H/S check. This should not be necessary, but if you run into
    1006. 

  1006. troubles with booting, it might help, although the opposite is more
    1007. 

  1007. likely to be true </dd>
    1008. 

  1008.     <dt> 	-b</dt>
    1009. 

  1009.     <dd> 	Skip save bootsector. Should you not want to overwrite your 	bootsector, add this parameter.  	</dd>
    1010. 

  1010.     <dt> 	-t &lt;timeout&gt;</dt>
    1011. 

  1011.     <dd>
    1012. 

  1012. set the timeout between the first client to connect and the last one to
    1013. 

  1013. ride the train. This option is only used during actual image creation.
    1014. 

  1014. Default is 10 seconds. </dd>
    1015. 

  1015.     <dt> 	-r &lt;bitrate&gt;</dt>
    1016. 

  1016.     <dd style="margin-bottom: 0.2in;">
    1017. 

  1017. Set the maximum bitrate. Set it in kilobit (k) or megabit (m). This is
    1018. 

  1018. recommended when you are on a shared lan, because mclone will eat all
    1019. 

  1019. the available bandwidth. <br>
    1020. 

  1020.     e.g.: 'mclone -s -r 80m' sets a 	maximum of 80 megabit or 10 megabytes per second (which is ok on a 	100mbit switch)  	</dd>
    1021. 

  1021.     <dt> 	Optional arguments for <b>IMAGE SAVE MODE</b></dt>
    1022. 

  1022.     <dt> 	-w</dt>
    1023. 

  1023.     <dd>
    1024. 

  1024. Use network compression. This option uses more CPU but saves bandwidth
    1025. 

  1025. on your network. Use only on powerful machines. This option is
    1026. 

  1026. permanent when you store to an image file, i.e. when enabled at image
    1027. 

  1027. creation it will always be used during restore. </dd>
    1028. 

  1028.     <dt> 	-C &lt;compressor&gt;</dt>
    1029. 

  1029.     <dd style="margin-bottom: 0.2in;">
    1030. 

  1030. Save your image with compression. 3 compression methods are available
    1031. 

  1031. (specified as written here): gzip, bzip2 and 7-zip e.g.: 'mclone -o
    1032. 

  1032. /data/xp-image -C gzip' </dd>
    1033. 

  1033. </dl>
    1034. 

  1034. <p>&nbsp;
    1035. 

  1035. 

  1036. 

  1037.  	<style type="text/css">
    1038. 

  1038. 	<!--{12802443353151}-->
    1039. 

  1039. 	</style>         
    1040. 

  1040. 

  1041. </p>
    1042. 

  1042. <p>For the full documentation, refer to the online manpage:</p>
    1043. 

  1043. <p><a href="http://trinityhome.org/manpages/man8/mclone.8.html">http://trinityhome.org/manpages/man8/mclone.8.html</a></p><br><a name="VZX1W3W6015LZRZ127YCKFJS9LX59AAU0YKLR6IHYETNW" &nbsp;="" id="VZX1W3W6015LZRZ127YCKFJS9LX59AAU0YKLR6IHYETNW"></a><h1>2.4 Winclean</h1><p>
    1044. 

  1044. 

  1045. 

  1046.  	<style type="text/css">
    1047. 

  1047. 	<!--
    1048. 

  1048. 		@page { margin: 0.79in }
    1049. 

  1049. 		P { margin-bottom: 0.08in }
    1050. 

  1050. 		H2 { margin-bottom: 0.08in }
    1051. 

  1051. 	-->
    1052. 

  1052. 	</style>    
    1053. 

  1053. 

  1054. </p>
    1055. 

  1055. <p>With winclean you can easily clean out unnecessary files, such as
    1056. 

  1056. tempfiles or the contents of recycle bins, from a Windows based
    1057. 

  1057. computer. <br>
    1058. 

  1058. This utility will call upon mountallfs to search for all local filesystems. <br>
    1059. 

  1059. It can clean several types of (practically) useless files. <br>
    1060. 

  1060. The file location types are: <br>
    1061. 

  1061. -Tempfiles from every user, located in %TEMP% (e.g.
    1062. 

  1062. C:\Documents&nbsp;and&nbsp;Settings\Username\Local&nbsp;Settings\Temp)
    1063. 

  1063. and Temporary Internet Files from Internet Explorer. The contents of
    1064. 

  1064. the folder C:\Windows\Temp is also cleaned out. <br>
    1065. 

  1065. -Recycle Bins (of all users) can be emptied as well <br>
    1066. 

  1066. -Uninstall files from cumulative patches and service packs. <br>
    1067. 

  1067. This is only valid for Windows XP (and 2000), not Vista or Seven (there
    1068. 

  1068. it's interweaved in WinSXS and is too dangerous to touch). The removal
    1069. 

  1069. of these redundant files can provide a significant performance increase
    1070. 

  1070. since a lot of directory enumeration is done in the Windows system
    1071. 

  1071. folder and the more files and folders there are, the slower it becomes.
    1072. 

  1072. These folders are hidden by default in Windows explorer and are named
    1073. 

  1073. similar to $Uninstall-KB123456$ for example. <br>
    1074. 

  1074. -Dllcache: C:\Windows\system32\dllcache can contain more than 1000 files and take up several hundreds of megabytes. <br>
    1075. 

  1075. This folder has little use if your machine is running as it should. <br>
    1076. 

  1076. -Hanging printerjobs: sometimes spoolfiles are corrupt, or a printer
    1077. 

  1077. has been physically removed for a long time or a spooljob is hundreds
    1078. 

  1078. if not thousands of megabytes in size because someone tried to print a
    1079. 

  1079. 10 megapixel picture of 1200dpi. <br>
    1080. 

  1080. Winclean can remove all pending jobs. <br>
    1081. 

  1081. -Java cache: The cache files of java applications can take up hundreds
    1082. 

  1082. of megabytes, sometimes even more. These can be safely deleted. <br>
    1083. 

  1083. This option is currently only for Sun Java. &nbsp;</p>
    1084. 

  1084. <h2>USAGE</h2>
    1085. 

  1085. <p>winclean -d &lt;destination mount point&gt; -s &lt;value&gt; -v -R -f -a -t -r -u -c -p -j <br>
    1086. 

  1086. where: <br>
    1087. 

  1087. -d &lt;destination mount point&gt;: if not specified, mountallfs will be called <br>
    1088. 

  1088. -s &lt;value&gt;: safe deletion of only tempfiles older than &lt;value&gt; days. <br>
    1089. 

  1089. -v: verbose deletion of files <br>
    1090. 

  1090. -R: report first which files could be deleted <br>
    1091. 

  1091. -f: force continue without prompting <br>
    1092. 

  1092. -a: clean all categories or... <br>
    1093. 

  1093. -t: tempfiles <br>
    1094. 

  1094. -r: recycle bins <br>
    1095. 

  1095. -u: remove uninstall patches information <br>
    1096. 

  1096. -c: Windows dllcache <br>
    1097. 

  1097. -p: hanging printerjobs <br>
    1098. 

  1098. -j: java cache</p>
    1099. 

  1099. <p>
    1100. 

  1100. 

  1101. 

  1102.  	<style type="text/css">
    1103. 

  1103. 	<!--
    1104. 

  1104. 		@page { margin: 0.79in }
    1105. 

  1105. 		P { margin-bottom: 0.08in }
    1106. 

  1106. 	-->
    1107. 

  1107. 	</style>     
    1108. 

  1108. 

  1109. </p>
    1110. 

  1110. <p>For the full documentation, refer to the online manpage:&nbsp;</p>
    1111. 

  1111. <p><a href="http://trinityhome.org/manpages/man8/winclean.8.html">http://trinityhome.org/manpages/man8/winclean.8.html</a></p><br><a name="TTVJRRE5QQRJBVB2F61R719J0CHFRFVAZGJFXPBD4SM6D" &nbsp;="" id="TTVJRRE5QQRJBVB2F61R719J0CHFRFVAZGJFXPBD4SM6D"></a><h1>2.5 Mountallfs</h1><p>
    1112. 

  1112. 

  1113. 

  1114.  	<style type="text/css">
    1115. 

  1115. 	<!--
    1116. 

  1116. 		@page { margin: 0.79in }
    1117. 

  1117. 		P { margin-bottom: 0.08in }
    1118. 

  1118. 		H2 { margin-bottom: 0.08in }
    1119. 

  1119. 	-->
    1120. 

  1120. 	</style> 
    1121. 

  1121. 

  1122. </p>
    1123. 

  1123. <p>This script is about the most handy addon to TRK. It 's a script
    1124. 

  1124. that scans all local storage devices and mounts their filesystems to a
    1125. 

  1125. standard mountpoint, nl. the name of its device name.<br>
    1126. 

  1126. <br>
    1127. 

  1127. mountallfs is a script that searches all local partitions on all local
    1128. 

  1128. drives for any filesystem and tries to mount it. It supports all kernel
    1129. 

  1129. based filesystems as well as fuse-ntfs and ntfs-3g. Furthermore it has
    1130. 

  1130. support for LVM volumes. Currently it also supports pseudo-hardware
    1131. 

  1131. raid volumes found on many desktop sata controllers. umountallfs is its
    1132. 

  1132. counterpart and unmounts all filesystems mounted by mountallfs. Always
    1133. 

  1133. run umountallfs before resetting your computer if you don't intend to
    1134. 

  1134. do a clean shutdown.</p>
    1135. 

  1135. <dl>
    1136. 

  1136.     <dt>-g</dt>
    1137. 

  1137.     <dd> 	Mount your ntfs filesystems with the <b>ntfs-3g</b>
    1138. 

  1138. driver. This is the default behavior since build 338 because it allows
    1139. 

  1139. full read/write support on ntfs drives. Performancewise it has much
    1140. 

  1140. more cpu overhead than the kernel based ntfs driver. Most modern PCs
    1141. 

  1141. shouldn't have too many problems with it however. Please note that the
    1142. 

  1142. mount result will mark the ntfs filesystems mounted as 'fuseblk', since
    1143. 

  1143. this is a userland driver which interfaces with the kernel fuse module.
    1144. 

  1144. </dd>
    1145. 

  1145.     <dt> 	-f</dt>
    1146. 

  1146.     <dd> 	Mount your ntfs filesystems with the <b>ntfsmount fuse</b>
    1147. 

  1147. driver. This is somewhat the predecessor to ntfs-3g (hence ntfs-3g is
    1148. 

  1148. the third generation ntfs driver). This fuse option has more limited
    1149. 

  1149. write support than ntfs-3g and is deprecated over ntfs-3g. The mount
    1150. 

  1150. result also shows as being mounted as 'fuseblk'. </dd>
    1151. 

  1151.     <dt> 	-k</dt>
    1152. 

  1152.     <dd> 	Mount your ntfs filesystems with the <b>kernel ntfs</b>
    1153. 

  1153. driver. This is a read-only driver but uses less CPU resources and so
    1154. 

  1154. has better performance. This was the default behavior before build 338
    1155. 

  1155. and is now a new option. </dd>
    1156. 

  1156.     <dt> 	-l</dt>
    1157. 

  1157.     <dd> Activate
    1158. 

  1158. Logical Volume Management. This option is for computers with LVM
    1159. 

  1159. volumes and pseudo-hardware raid controllers. If you have such a
    1160. 

  1160. pseudo-hardware raid controller and you configured your disks in mirror
    1161. 

  1161. mode, ALWAYS use this option before doing any operation on your disk
    1162. 

  1162. because otherwise each mirror member might get mounted separately and
    1163. 

  1163. you <b>WILL</b> corrupt your filesystem on it. 	Default behavior for this option is also to mount ntfs volumes with 	ntfs-3g.  	</dd>
    1164. 

  1164.     <dt> 	-q | --quiet</dt>
    1165. 

  1165.     <dd style="margin-bottom: 0.2in;"> 	Do not display any output from the mount result.  	</dd>
    1166. 

  1166. </dl>
    1167. 

  1167. <p>
    1168. 

  1168. 

  1169. 

  1170.  	<style type="text/css">
    1171. 

  1171. 	<!--
    1172. 

  1172. 		@page { margin: 0.79in }
    1173. 

  1173. 		P { margin-bottom: 0.08in }
    1174. 

  1174. 	-->
    1175. 

  1175. 	</style>
    1176. 

  1176. </p><p>For the full documentation, refer to the online manpage:</p>
    1177. 

  1177. <a href="http://trinityhome.org/manpages/man8/mountallfs.8.html">http://trinityhome.org/manpages/man8/mountallfs.8.html&nbsp; </a><p></p>
    1178. 

  1178. <h2>REMARKS</h2>
    1179. 

  1179. <p>-If your filesystems were not found it might either mean they were
    1180. 

  1180. too corrupted to mount or your disk controller was not detected by TRK.
    1181. 

  1181. You might try more (scsi) drivers by typing 'tryscsi'. This is more the
    1182. 

  1182. case on servers with more advanced disk controllers. However, 'tryscsi'
    1183. 

  1183. might freeze your machine. Be warned! <br>
    1184. 

  1184. -Mountallfs might also warn you that your ntfs volumes have been
    1185. 

  1185. dismounted improperly. This is most likely the case when a Windows
    1186. 

  1186. session was shutdown improperly. Mountallfs will prompt you to
    1187. 

  1187. forcemount the ntfs volume, which invokes an ntfsfix and triggers a
    1188. 

  1188. chkdsk at next reboot into Windows. Please, let this chkdsk run. It
    1189. 

  1189. will solve about half of the possible problems that might occur on your
    1190. 

  1190. ntfs volumes. <br>
    1191. 

  1191. -Another thing you might encounter is that the volume (Windows) is
    1192. 

  1192. hibernated and a hiberfil.sys is present. In that case you will be
    1193. 

  1193. prompted to either remove the hiberfil.sys and forcemount the drive or
    1194. 

  1194. leave it alone. Mounting the drive and leaving the hiberfil.sys could
    1195. 

  1195. corrupt your Windows and make it crash when you resume from
    1196. 

  1196. hibernation. <br>
    1197. 

  1197. -/etc/mountallfstab is the separate config file mountallfs keeps after
    1198. 

  1198. mounting. It uses it for umountallfs to unmount all the volumes
    1199. 

  1199. previously mounted by mountallfs. Umountallfs also does a test that
    1200. 

  1200. there are no more open processes on the volumes (most of the times your
    1201. 

  1201. working directory of your shell). However, it does not take into
    1202. 

  1202. account any mountpoints under your mountallfs mounted volumes. So you
    1203. 

  1203. need to take care of those manually.</p>
    1204. 

  1204. <h2>EXAMPLES</h2>
    1205. 

  1205. <p>Command:'mountallfs -l' searches for LVM volumes and mounts the filesystems inside them.</p>
    1206. 

  1206. <dl>
    1207. 

  1207.     <dt style="margin-bottom: 0.2in;">Command:'mountallfs' without any 	option mounts all filesystems and remounts ntfs filesystems with 	ntfs-3g</dt>
    1208. 

  1208. </dl>
    1209. 

  1209. <p>&nbsp;</p><br><a name="HH1WPPJEI4DHJTAHXPSYR3637JMCUVX22NNH2YLBSPI18" &nbsp;="" id="HH1WPPJEI4DHJTAHXPSYR3637JMCUVX22NNH2YLBSPI18"></a><h1>2.6 Updatetrk</h1><p>
    1210. 

  1210. 

  1211. 

  1212.  	<style type="text/css">
    1213. 

  1213. 	<!--
    1214. 

  1214. 		@page { margin: 0.79in }
    1215. 

  1215. 		P { margin-bottom: 0.08in }
    1216. 

  1216. 		H2 { margin-bottom: 0.08in }
    1217. 

  1217. 	-->
    1218. 

  1218. 	</style>
    1219. 

  1219. </p><p>Trinity Rescue Kit  is able to <strong>update itself or better said, add features </strong>through
    1220. 

  1220. the script 'updatetrk'. This requires decent Internet connectivity,
    1221. 

  1221. direct, over a router or via a proxy server (in that case, run '.
    1222. 

  1222. setproxy' first)<br>
    1223. 

  1223. <br>
    1224. 

  1224. The script is very simple to handle:<br>
    1225. 

  1225. Suppose you 've booted from a PC with a Windows XP (2K or NT is also good), you can run updatetrk without any option.<br>
    1226. 

  1226. Since TRK 3.4, updatetrk uses a script called 'getswap' which looks for
    1227. 

  1227. extra virtual memory on local swap partitions and Windows pagefile.sys<br>
    1228. 

  1228. <br>
    1229. 

  1229. Updatetrk fetches external third party, non GPL software (fetches and
    1230. 

  1230. updates all AV engines for virusscan) and creates a new TRK isofile or
    1231. 

  1231. updates your TRK USB stick. It also saves any changes you made to your
    1232. 

  1232. running copy of TRK. It allows you to install tarballs and even rpms
    1233. 

  1233. and have it saved for the next time you run TRK. An example of such
    1234. 

  1234. software is IBM Tivoli Storage Manager client. Adding this software to
    1235. 

  1235. TRK allows you to do offline backup/restores from a TSM server. <br>
    1236. 

  1236. Updatetrk can create a new isofile which you can burn or directly
    1237. 

  1237. update your USB bootmedium. Given that you run TRK on a computer that
    1238. 

  1238. normally runs Windows, it will use the pagefile.sys as extra swapspace
    1239. 

  1239. on which to create its new image. &nbsp;</p>
    1240. 

  1240. <h2>USAGE</h2>
    1241. 

  1241. <p>updatetrk -b [BUILDTARGET] -i [TARGETISOFILE] (or) -u [TARGETUSBDEVICE] -s -a avs,bde,clam,fprot,va -f</p>
    1242. 

  1242. <dl>
    1243. 

  1243.     <dt>-b [BUILDTARGET]</dt>
    1244. 

  1244.     <dd> Build location where
    1245. 

  1245. intermediate files can be stored. Should be at least 1100mb. Make sure
    1246. 

  1246. no other files reside in that location, as they will be included as
    1247. 

  1247. well. If no build target is given, a script called 'getswap' will be
    1248. 

  1248. invoked which will search for swap partitions and Windows pagefile.sys
    1249. 

  1249. files. This pagefile will be added as swapspace and extend youir
    1250. 

  1250. working memory. This has no consequences for your Windows system
    1251. 

  1251. afterwards. It will just be reused. </dd>
    1252. 

  1252.     <dt> 	-i [TARGETISOFILE]</dt>
    1253. 

  1253.     <dd>
    1254. 

  1254. Target dir on which to create the isofile. There should be at least
    1255. 

  1255. 350Mb free on the target. The filename will be automatically given. If
    1256. 

  1256. this option is omitted, the file will be created in the same location
    1257. 

  1257. as the buildtarget. If the buildtarget is omitted, it will be created
    1258. 

  1258. in the temp dir of the drive containing the pagefile. In general this
    1259. 

  1259. will be&nbsp;&nbsp;c:\temp&nbsp;&nbsp;under Windows. </dd>
    1260. 

  1260.     <dt> 	-u [TARGETUSBDEVICE]</dt>
    1261. 

  1261.     <dd style="margin-bottom: 0.2in;">
    1262. 

  1262. Target USB filesystem to update. This performs a simple copy to the
    1263. 

  1263. location you specified. In general this is the partition from which you
    1264. 

  1264. booted TRK. </dd>
    1265. 

  1265.     <dd style="margin-bottom: 0.2in;"> Example 1:
    1266. 

  1266. 'updatetrk -b /hda1/temp/trkbuilding/ -i /hda1/Docs/' This will use
    1267. 

  1267. /hda1/temp/trkbuilding/&nbsp;&nbsp;as construction site and create
    1268. 

  1268. /hda1/Docs/trinity-rescue-kit-3.4-363u.iso </dd>
    1269. 

  1269.     <dd style="margin-bottom: 0.2in;">
    1270. 

  1270. Example 2: 'updatetrk -u /dev/sda4' will search for a local pagefile as
    1271. 

  1271. construction site and copy back the files to your USB device (or fixed
    1272. 

  1272. harddisc) <br> If you specify no options at all, TRK will always be
    1273. 

  1273. created on a local pagefile as an ISO in c:\temp. If no pagefile is
    1274. 

  1274. found, the script will exit. If you specified a specific buildtarget,
    1275. 

  1275. the files will remain there afterwards at your convenience. Remark:
    1276. 

  1276. option '-i' and '-u' are not useable together. </dd>
    1277. 

  1277.     <dt> 	-s avs,bde,clam,fprot,va</dt>
    1278. 

  1278.     <dd style="margin-bottom: 0.2in;"> 	Skip the inclusion of specific AV engines+updates. The syntax speaks 	for itself. <br>
    1279. 

  1279. If you skip all AVs, updatetrk will only apply what is currently
    1280. 

  1280. already modified on your running copy. -f Force updatetrk to build,
    1281. 

  1281. even if not enough tempspace is available. It is possible to assign
    1282. 

  1282. more of the swapspace to /dev/shm (the default volatile temporary
    1283. 

  1283. storage location of Linux). Running 'getswap -s 80' f.i. will assign
    1284. 

  1284. 80% of the total memory (ram+swap) available to /dev/shm. With 'df -h'
    1285. 

  1285. /dev/shm you can verify if you arrive at 1.1Gb free space on this
    1286. 

  1286. location. </dd>
    1287. 

  1287.     <dd style="margin-left: 0.38in; text-indent: -0.36in; margin-bottom: 0.2in;"> 	-a<br>
    1288. 

  1288. Copy contents of / (root) completely and “as is” instead of cleaning up
    1289. 

  1289. and omitting certain directories. This will include logs and
    1290. 

  1290. bash_history as well.</dd>
    1291. 

  1291. </dl>
    1292. 

  1292. <p><a name="lbAF"></a>&nbsp;</p>
    1293. 

  1293. <h2>EXAMPLES</h2>
    1294. 

  1294. <p>Example 1: 'updatetrk -b /hda1/temp/trkbuilding/ -i /hda1/Docs/'</p>
    1295. 

  1295. <p>This will use /hda1/temp/trkbuilding/ as construction site and create /hda1/Docs/trinity-rescue-kit-3.4-363u.iso</p>
    1296. 

  1296. <p>Example 2: 'updatetrk -u /dev/sda4'</p>
    1297. 

  1297. <p>This will search for a local pagefile as construction site and copy back the files to your USB device (or fixed harddisc)</p>
    1298. 

  1298. <p><a name="lbAG"></a>If you specify no options at all, TRK will always
    1299. 

  1299. be created on a local pagefile as an ISO in c:\temp. If no pagefile is
    1300. 

  1300. found, the script will exit. <br>
    1301. 

  1301. If you specified a specific buildtarget, the files will remain there afterwards at your convenience. &nbsp;</p>
    1302. 

  1302. <h2>REMARKS</h2>
    1303. 

  1303. <p>-Option '-i' and '-u' are not useable together.</p>
    1304. 

  1304. <p>-If you're behind a proxy server, run '. setproxy' first</p>
    1305. 

  1305. <p>-If you're updating your running USB stick, hard <b>RESET</b> your
    1306. 

  1306. computer as soon as updatetrk has finished, since the underlying
    1307. 

  1307. filesystems will have changed without having been remounted.</p>
    1308. 

  1308. <p>-TRK has an empty rpm database (except for 1 package that does some
    1309. 

  1309. basic “provides”), meaning that almost any RPM you install will protest
    1310. 

  1310. about missing dependencies. <br>
    1311. 

  1311. In many cases, the binaries would work anyway. <br>
    1312. 

  1312. The easiest way to test this is by installing the rpm in this way:</p>
    1313. 

  1313. <p>Type the command: 'rpm -ivh --nodeps &lt;package.rpm&gt;'</p>
    1314. 

  1314. <p>Then test it by executing the binaries. If it fails because certain
    1315. 

  1315. libraries are missing, run ldd /usr/bin/mybinary and check what library
    1316. 

  1316. is missing. Go and look for that library on rpmfind.net and install it.</p>
    1317. 

  1317. <p>Many commercial rpms are compiled in such a way that they are
    1318. 

  1318. compatible with most Linux distros. Most of them require glibc 2.2 or
    1319. 

  1319. higher. TRK is glibc 2.3.4.</p>
    1320. 

  1320. <p><a name="lbAH"></a>-If your CD/RW drive is currently available (booted from RAM or usb stick), you can directly record the isofile. <br>
    1321. 

  1321. For a blank cd, run f.i. 'cdrecord trinity-rescue-kit.3.4-build-363u.iso' <br>
    1322. 

  1322. If you still need to erase your rewritable CD, first run 'cdrecord -blank=fast'</p>
    1323. 

  1323. <p><br>
    1324. 

  1324. &nbsp;</p>
    1325. 

  1325. <p><br>
    1326. 

  1326. &nbsp;</p>
    1327. 

  1327. <h2>What will 'updatetrk' do?</h2>
    1328. 

  1328. <p><br>
    1329. 

  1329. &nbsp;</p>
    1330. 

  1330. <p>-First ask for license agreements to install commercial software</p>
    1331. 

  1331. <p>-Then, it downloads the latest engine + virus signatures for ClamAV<br>
    1332. 

  1332. <br>
    1333. 

  1333. -Next, it downloads F-Prot + updates<br>
    1334. 

  1334. <br>
    1335. 

  1335. -As third antivirus, it fetches Avast Antivirus + updates. You will need a valid license key handy (free registration on site)<br>
    1336. 

  1336. <br>
    1337. 

  1337. -4<sup>th</sup> antivirusscanner is BitDefender and starts the
    1338. 

  1338. installation procedure. This is BitDefender 's own install procedure,
    1339. 

  1339. just follow instructions on the screen, type "accept" for the license
    1340. 

  1340. agreement and leave everything to the default propositions.</p>
    1341. 

  1341. <p>-The last virusscanner it fetches is Vexira. No intervention is needed here.<br>
    1342. 

  1342. <br>
    1343. 

  1343. -Finally, it copies the complete contents of /bin, /sbin /etc and /lib
    1344. 

  1344. to your new TRK. This means that anything you modified or added in
    1345. 

  1345. these directories will be included in your new TRK. This gives you an
    1346. 

  1346. easy way to make small modifications/additions to TRK.</p>
    1347. 

  1347. <p>After that, updatetrk recreates its /usr filesystem squashfs image.
    1348. 

  1348. Since this image is orignally mounted with a pseudo read/write aufs
    1349. 

  1349. over it, volatile changes will be submitted in the new squashfs image.</p>
    1350. 

  1350. <p>Also the initrd is recreated and everything from /bin /sbin /etc
    1351. 

  1351. /lib and /var/lib is copied to it. Logfiles and session-based changes
    1352. 

  1352. are discarded, except if the option -a was added to the commandline.
    1353. 

  1353. Then everything will be copied back “as is”, including bash history f.i.<br>
    1354. 

  1354. <br>
    1355. 

  1355. This script can be run time after time to keep your antivirus signatures up-to-date.<br>
    1356. 

  1356. <br>
    1357. 

  1357. When no destination parameter was given to TRK and you 're running TRK
    1358. 

  1358. from CD, it will move the newly created isofile to the drive where it
    1359. 

  1359. found your pagefile.sys in directory 'temp'. Most likely this will be
    1360. 

  1360. C:\temp.</p>
    1361. 

  1361. <p>
    1362. 

  1362. 

  1363. 

  1364.  	<style type="text/css">
    1365. 

  1365. 	<!--
    1366. 

  1366. 		@page { margin: 0.79in }
    1367. 

  1367. 		P { margin-bottom: 0.08in }
    1368. 

  1368. 	-->
    1369. 

  1369. 	</style>
    1370. 

  1370. </p><p>To get complete and up to date info, please check out the online version of the manpage:</p>
    1371. 

  1371. <p></p>
    1372. 

  1372. <p><a href="http://trinityhome.org/manpages/man8/updatetrk.8.html">http://trinityhome.org/manpages/man8/updatetrk.8.html</a></p>
    1373. 

  1373. <p></p><br><a name="DNEHBFA6ISQPQUF15A9HX1XVYX82E8LIMQQNVRJ480INJ" &nbsp;="" id="DNEHBFA6ISQPQUF15A9HX1XVYX82E8LIMQQNVRJ480INJ"></a><h1>2.7 Trk2usb</h1><p>
    1374. 

  1374. 

  1375. 

  1376.  	<style type="text/css">
    1377. 

  1377. 	<!--
    1378. 

  1378. 		@page { margin: 0.79in }
    1379. 

  1379. 		P { margin-bottom: 0.08in }
    1380. 

  1380. 		H2 { margin-bottom: 0.08in }
    1381. 

  1381. 	-->
    1382. 

  1382. 	</style> 
    1383. 

  1383. 

  1384. </p>
    1385. 

  1385. <p>This utility puts your  <strong>Trinity Rescue Kit to a USB stick/disk</strong>
    1386. 

  1386. or even to a fixed harddisk. This is one of the two methods you can use
    1387. 

  1387. to get TRK running from USB. This is also the recommended and easiest
    1388. 

  1388. method of doing it. Only downside here is that you first have to burn
    1389. 

  1389. the iso version of TRK to CD, boot from it and run it from there.<br>
    1390. 

  1390. <br>
    1391. 

  1391. When given without the noformat option, it will destroy all data on the
    1392. 

  1392. destination device, create a fat filesystem in the 4th partition id of
    1393. 

  1393. the disk. This gives the best compatibility with most BIOSes. <br>
    1394. 

  1394. It is also possible to do a non-destructive transfer to your medium given the -n option. <br>
    1395. 

  1395. The destination medium has to be at least the size of the TRK isofile. Recommended is 256Mb minimum.</p>
    1396. 

  1396. <h2>USAGE</h2>
    1397. 

  1397. <p>trk2usb -d [DEVICE] -s [SIZE] -n</p>
    1398. 

  1398. <p>
    1399. 

  1399. </p><dl>
    1400. 

  1400.     <dt>-d [DEVICE]</dt>
    1401. 

  1401.     <dd style="margin-bottom: 0.2in;">
    1402. 

  1402. Specify the destination device. In case you use it without the noformat
    1403. 

  1403. option, you need to give the complete disk as argument, not a
    1404. 

  1404. partition. Your disk will be erased, zeroed out and formatted with one
    1405. 

  1405. partition as FAT16 of maximum 1Gb as the 4th primary partition. This is
    1406. 

  1406. for maximum compatibility. </dd>
    1407. 

  1407.     <dd style="margin-bottom: 0.2in;"> 	Example: trk2usb -d /dev/sdc  	</dd>
    1408. 

  1408.     <dt> 	-n</dt>
    1409. 

  1409.     <dd style="margin-bottom: 0.2in;">
    1410. 

  1410. Noformat. Use this option if your device is already correctly formatted
    1411. 

  1411. and you don't want to lose your data on it. This requires you to
    1412. 

  1412. specify the destination as a partition. </dd>
    1413. 

  1413.     <dd style="margin-bottom: 0.2in;"> 	Example: trk2usb -n -d /dev/sdc1  	</dd>
    1414. 

  1414.     <dt> 	-s</dt>
    1415. 

  1415.     <dd style="margin-bottom: 0.2in;">
    1416. 

  1416. Optionally, you can specify the size of the destination partition in
    1417. 

  1417. Mb. This allows you to add more partitions later. This option is not
    1418. 

  1418. combinable with -n </dd>
    1419. 

  1419. </dl>
    1420. 

  1420. <p></p>
    1421. 

  1421. <p>Read the full and updated manpage online here:</p>
    1422. 

  1422. <p><a href="http://trinityhome.org/manpages/man8/trk2usb.8.html">http://trinityhome.org/manpages/man8/trk2usb.8.html</a></p>
    1423. 

  1423. <p>&nbsp;</p><br><a name="WM8PAWXULFITSRN0X6I1YVCLB9IA41FQDD5E0TYBZ7VGP" &nbsp;="" id="WM8PAWXULFITSRN0X6I1YVCLB9IA41FQDD5E0TYBZ7VGP"></a><h1>2.8 Trk2iso</h1><p>On
    1424. 

  1424. special demand, I 've created this small utility that creates an ISO
    1425. 

  1425. file of your currently running TRK. It doesn 't update trk, it just
    1426. 

  1426. creates an isofile in the current directory from where the command was
    1427. 

  1427. launched. Here 's how to use it best:<br>
    1428. 

  1428. 'mountallfs -g' =&gt; suppose /dev/hda1 is your ntfs c:-drive<br>
    1429. 

  1429. 'mkdir /hda1/temp'<br>
    1430. 

  1430. 'cd /hda1/temp'<br>
    1431. 

  1431. 'trk2iso'<br>
    1432. 

  1432. &nbsp;<br>
    1433. 

  1433. Once the isofile created, you can reburn TRK to CD.</p><br><a name="EGNT0M1F9DJ7XUB34LIEU8DXZVGDWEW0K9IAMAFLDQJ09" &nbsp;="" id="EGNT0M1F9DJ7XUB34LIEU8DXZVGDWEW0K9IAMAFLDQJ09"></a><h1>2.9 Fileserver</h1><p>
    1434. 

  1434. 

  1435. 

  1436.  	<style type="text/css">
    1437. 

  1437. 	<!--
    1438. 

  1438. 		@page { margin: 0.79in }
    1439. 

  1439. 		P { margin-bottom: 0.08in }
    1440. 

  1440. 		H2 { margin-bottom: 0.08in }
    1441. 

  1441. 	-->
    1442. 

  1442. 	</style>   
    1443. 

  1443. 

  1444. </p>
    1445. 

  1445. <p>In short: <strong>share your drives like a windows fileserver</strong><br>
    1446. 

  1446. Fileserver is a bash script that calls mountallfs and creates Windows
    1447. 

  1447. fileshares from your mountallfs mounted volumes. It can run in
    1448. 

  1448. guest-mode or user secured mode. It can optionally also run read-only. <br>
    1449. 

  1449. The default netbios name will be "TRKSRV" and the workgroup will be
    1450. 

  1450. "WORKGROUP". The server will not register in any WINS or DNS servers,
    1451. 

  1451. so for it to appear in your network neighbourhood might take some time
    1452. 

  1452. because it will use broadcast. <br>
    1453. 

  1453. For quick access to it from an external PC running Windows, it's
    1454. 

  1454. recommended to go to start =&gt; run (or "Start Search" in Vista or
    1455. 

  1455. Seven) and type \\1.2.3.4 where 1.2.3.4 is the ip-address of your TRK.
    1456. 

  1456. Fileserver mentions the ip-address in green when it starts. Fileserver
    1457. 

  1457. calls mountallfs to search and mount all local filesystems.</p>
    1458. 

  1458. <p>Fileserver can be called in two modes: in <strong>secured</strong> or in <strong>guest </strong>mode (+ optionally read-only mode)<br>
    1459. 

  1459. <br>
    1460. 

  1460. -<strong>Secured mode</strong> is invoked with the command 'fileserver -s'<br>
    1461. 

  1461. This will prompt your for adding a user and a password that will have
    1462. 

  1462. access to your files remotely. Just follow instructions. Here 's how
    1463. 

  1463. the output would be if you ran it<br>
    1464. 

  1464. <br>
    1465. 

  1465. <font face="Courier New">Starting a username/password secured Samba fileserver and sharing all local filesystems<br>
    1466. 

  1466. Enter a username which will be created to have access to your local files:<br>
    1467. 

  1467. New SMB password:<br>
    1468. 

  1468. Retype new SMB password:<br>
    1469. 

  1469. Added user testuser.<br>
    1470. 

  1470. Mounting all your local filesystems using mountallfs -g<br>
    1471. 

  1471. These are the IP-addresses your fileserver will listen to:<br>
    1472. 

  1472. 192.168.81.5<br>
    1473. 

  1473. Starting SMB services:                                          [  OK  ]<br>
    1474. 

  1474. Starting NMB services:                                          [  OK  ]</font><br>
    1475. 

  1475. <br>
    1476. 

  1476. -<strong>Guest mode </strong>is invoked with the command 'fileserver -g'<br>
    1477. 

  1477. Use with caution, it allows everyone with network access to the
    1478. 

  1478. computer to go on the local harddiscs. Use only in a trusted
    1479. 

  1479. environment with a firewall or not connected to the Internet.</p>
    1480. 

  1480. <h2>USAGE</h2>
    1481. 

  1481. <dl>
    1482. 

  1482.     <dt>-s</dt>
    1483. 

  1483.     <dd> Start a secured samba server, i.e. one
    1484. 

  1484. that does not allow guest access. 'fileserver' will prompt you for a
    1485. 

  1485. username and a password. This is the default if no arguments are given.
    1486. 

  1486. </dd>
    1487. 

  1487.     <dt> 	-g</dt>
    1488. 

  1488.     <dd> Run a guest enabled samba server. This
    1489. 

  1489. will give anyone full access to the disks of your TRK running computer.
    1490. 

  1490. Use only in an environment you can trust! </dd>
    1491. 

  1491.     <dt> 	-r</dt>
    1492. 

  1492.     <dd> 	Shares are read-only.  	</dd>
    1493. 

  1493.     <dt> 	stop</dt>
    1494. 

  1494.     <dd style="margin-bottom: 0.2in;"> 	Stops the samba server and unmounts the local filesystems.  	</dd>
    1495. 

  1495. </dl>
    1496. 

  1496. <p><br>
    1497. 

  1497. &nbsp;</p>
    1498. 

  1498. <h2>EXAMPLE 1</h2>
    1499. 

  1499. <p>TRK to TRK use of fileserver. <br>
    1500. 

  1500. Suppose that we have two PCs both running TRK on the same network. <br>
    1501. 

  1501. We run fileserver on one PC which tells us that its ip-address is, for example, 1.2.3.4 in green characters. <br>
    1502. 

  1502. Then, from the other PC, we give the command: mount //1.2.3.4/hda1 /mnt1 ( fileserver started as guest )</p>
    1503. 

  1503. <dl>
    1504. 

  1504.     <dt>or<br>
    1505. 

  1505.     </dt>
    1506. 

  1506.     <dt><br>
    1507. 

  1507.     </dt>
    1508. 

  1508.     <dt>mount //1.2.3.4/hda1 /mnt1 -o user=your_user_name ( secured ) A 	password will be requested. <br>
    1509. 

  1509.     </dt>
    1510. 

  1510.     <dt>In guest mode, just hit the Enter 	key <br>
    1511. 

  1511.     </dt>
    1512. 

  1512.     <dt>In secured mode, enter the applicable password and hit 	Enter. <br>
    1513. 

  1513.     </dt>
    1514. 

  1514.     <dt>The selected partition (in this case hda1) of the remote 	PC (the fileserver) can now be accessed locally as /mnt1.</dt>
    1515. 

  1515. </dl>
    1516. 

  1516. <h2>EXAMPLE 2</h2>
    1517. 

  1517. <dl>
    1518. 

  1518.     <dt>TRK as seen from a Windows machine<br>
    1519. 

  1519.     </dt>
    1520. 

  1520.     <dt>Run the fileserver from the TRK&nbsp;3.4&nbsp;simple menu<br>
    1521. 

  1521.     </dt>
    1522. 

  1522.     <dt><br>
    1523. 

  1523.     </dt>
    1524. 

  1524.     <dt><img alt="" src="helpdocs_files/trk34_start_fileserver.png" width="[object Object]" align="middle"><br>
    1525. 

  1525.     </dt>
    1526. 

  1526.     <dt><br>
    1527. 

  1527.     </dt>
    1528. 

  1528.     <dt>On your windows machine, click Start =&gt;&nbsp;Run (Vista and 7 "Start" =&gt; "Search" or winkey +r)<br>
    1529. 

  1529.     </dt>
    1530. 

  1530.     <dt><br>
    1531. 

  1531.     </dt>
    1532. 

  1532.     <dt><img alt="" src="helpdocs_files/run-fileserver-unc.png" height="177" width="346" align="middle"><br>
    1533. 

  1533.     </dt>
    1534. 

  1534.     <dt><br>
    1535. 

  1535.     </dt>
    1536. 

  1536.     <dt>Browse the TRK&nbsp;fileserver, read and write access.<br>
    1537. 

  1537.     </dt>
    1538. 

  1538.     <dt><br>
    1539. 

  1539.     </dt>
    1540. 

  1540.     <dt><img alt="" src="helpdocs_files/fileserver-explorer.png" height="600" width="800" align="middle"><br>
    1541. 

  1541.     </dt>
    1542. 

  1542.     <dt><br>
    1543. 

  1543.     </dt>
    1544. 

  1544. </dl>
    1545. 

  1545. <p>&nbsp;</p><br><a name="20T4DLR6P2JZL5SVUKVM5FB7MQPKJQUCFC6INMF3FQSSK" &nbsp;="" id="20T4DLR6P2JZL5SVUKVM5FB7MQPKJQUCFC6INMF3FQSSK"></a><h1>2.10 Bridge</h1><p>
    1546. 

  1546. 

  1547. 

  1548.  	<style type="text/css">
    1549. 

  1549. 	<!--
    1550. 

  1550. 		@page { margin: 0.79in }
    1551. 

  1551. 		P { margin-bottom: 0.08in }
    1552. 

  1552. 		H1 { margin-bottom: 0.08in }
    1553. 

  1553. 		H1.western { font-family: "Times New Roman", serif }
    1554. 

  1554. 		H1.cjk { font-family: "Bitstream Vera Sans" }
    1555. 

  1555. 		H1.ctl { font-family: "Bitstream Vera Sans" }
    1556. 

  1556. 		H2 { margin-bottom: 0.08in }
    1557. 

  1557. 	-->
    1558. 

  1558. 	</style>
    1559. 

  1559. </p><p>Suppose you have a PC of which of which you like to know what
    1560. 

  1560. traffic it generates. Or suppose you have a router on which you like to
    1561. 

  1561. know what traffic passes by. Well, "bridge" will create you a <strong>transparent connection between ethernet cards</strong>
    1562. 

  1562. that passes all traffic and on which you can start sniffing what passes
    1563. 

  1563. by. You could use an old fashion hub that replicates all traffic to all
    1564. 

  1564. of its ports, but nowadays that is almost inexistent, almost any cheap
    1565. 

  1565. hub is in fact a switch that only replicates traffic to the port it is
    1566. 

  1566. needed. In that case, put a computer with TRK in between your
    1567. 

  1567. connection.<br>
    1568. 

  1568. <br>
    1569. 

  1569. <strong>What you need</strong><br>
    1570. 

  1570. <br>
    1571. 

  1571. is a computer with at least 2 network cards and the latest TRK to boot from.<br>
    1572. 

  1572. <br>
    1573. 

  1573. -Once the network cards are connected on both sides (on on the PC, one on the network), <strong>run 'bridge up'</strong>.
    1574. 

  1574. This will setup a bridge and traffic will transparently pass from one
    1575. 

  1575. side to the other. One note here which is quite important: make sure
    1576. 

  1576. only 1 network card has its own ip-address, let the other one without
    1577. 

  1577. (if they both have one, do an 'ifconfig eth1 down' f.i.). I will
    1578. 

  1578. explain this later.<br>
    1579. 

  1579. <br>
    1580. 

  1580. -Now, start sniffing with tcpdump. Run it like this: 'tcpdump -i eth0'
    1581. 

  1581. In this way, you see ALL traffic headers that pass by. If you need to
    1582. 

  1582. filter something specific, use "grep" to get it out. F.i. you need to
    1583. 

  1583. see all http traffic going to 10.0.1.20, run this: 'tcpdump -i eth0 |
    1584. 

  1584. grep 10.0.1.20 | grep http'<br>
    1585. 

  1585. <br>
    1586. 

  1586. About the single ip-address: I have noticed that if you connect two
    1587. 

  1587. network cards to the same network and let them both get an ip-address
    1588. 

  1588. through dhcp (which will subsequently be addresses in the same network
    1589. 

  1589. range) and afterwards connect one to a pc to start sniffing, tcpdump
    1590. 

  1590. will go berzerk and no output will be shown but your TRK will give the
    1591. 

  1591. impression of hanging and will not respond to a ctrl+c signal very
    1592. 

  1592. quickly. After about 10 seconds, it will stop. But you will have
    1593. 

  1593. noticed that sniffing doesn 't work. Well, if one card doesn 't have an
    1594. 

  1594. address, this problem doesn 't occur. So leave at least one nic down.
    1595. 

  1595. You can even leave both down, you don 't need an ip-address to sniff
    1596. 

  1596. the network, "bridge" will bring up both cards in promiscuous mode and
    1597. 

  1597. make a bridge interface "br0".<br>
    1598. 

  1598. <br>
    1599. 

  1599. To bring the bridge down, just type 'bridge down'</p>
    1600. 

  1600. <p>Also read the online manpage on this:</p>
    1601. 

  1601. <p><a href="http://trinityhome.org/manpages/man8/bridge.8.html">http://trinityhome.org/manpages/man8/bridge.8.html</a></p>
    1602. 

  1602. <p></p><br><a name="PSTEW6D05PZF2FK7VHGLCYWQZWP8T538NMCAJF0FVPLMV" &nbsp;="" id="PSTEW6D05PZF2FK7VHGLCYWQZWP8T538NMCAJF0FVPLMV"></a><h1>2.11 Setip</h1><p>Use this whenever you want to enter a fixed ip address for your network cards</p>
    1603. 

  1603. <h2>Usage</h2>
    1604. 

  1604. <p>setip &lt;interface&gt; | -h<br>
    1605. 

  1605. This command sets the ip information of your network card(s)<br>
    1606. 

  1606. Without an argument, it assumes your network card is eth0<br>
    1607. 

  1607. 'setip -h' shows the help output<br>
    1608. 

  1608. Here 's what&nbsp; the command does:<br>
    1609. 

  1609. <br>
    1610. 

  1610. '<font face="Courier New">setip eth1<br>
    1611. 

  1611. Enter the IP-address for eth1: 10.0.0.1<br>
    1612. 

  1612. Enter the subnet mask for eth1: 255.255.255.0<br>
    1613. 

  1613. Enter the default gateway, &lt;enter&gt; for none: 10.0.0.254<br>
    1614. 

  1614. Enter the IP-address of the DNS server you 'd like to use, &lt;enter&gt; for none: 10.0.0.3<br>
    1615. 

  1615. <br>
    1616. 

  1616. Setting ipaddress 10.0.0.1/255.255.255.0 on eth1<br>
    1617. 

  1617. Setting default gateway to 10.0.0.254<br>
    1618. 

  1618. Setting nameserver 10.0.0.3 in /etc/resolv.conf'</font></p>
    1619. 

  1619. <p>Also read the online manpage on this:</p>
    1620. 

  1620. <p><a href="http://trinityhome.org/manpages/man8/setip.8.html">http://trinityhome.org/manpages/man8/setip.8.html</a></p><br><a name="WU8QP3M0YGLR9XQ8V4MW69X4SZF6ZM1L701LTECHLNZLB" &nbsp;="" id="WU8QP3M0YGLR9XQ8V4MW69X4SZF6ZM1L701LTECHLNZLB"></a><h1>2.12 Setproxy</h1><p>
    1621. 

  1621. 

  1622. 

  1623.  	<style type="text/css">
    1624. 

  1624. 	<!--
    1625. 

  1625. 		@page { margin: 0.79in }
    1626. 

  1626. 		P { margin-bottom: 0.08in }
    1627. 

  1627. 	-->
    1628. 

  1628. 	</style>
    1629. 

  1629. </p><p>This script prompts you for proxy server settings, should you be
    1630. 

  1630. unable to go directly onto the Internet. Use it without any arguments,
    1631. 

  1631. it will prompt you for proxy ip-address or hostname, proxyport (usually
    1632. 

  1632. 8080) and optionally username and password (invisible). If no
    1633. 

  1633. username/password is required, just leave it blank and hit enter.<br>
    1634. 

  1634. <br>
    1635. 

  1635. This script can also be called upon startup in the bootmenu.<br>
    1636. 

  1636. <br>
    1637. 

  1637. Usage: 'setproxy'<br>
    1638. 

  1638. <br>
    1639. 

  1639. <br>
    1640. 

  1640. If you want your proxyserver to always be included, I recommend you set
    1641. 

  1641. up your LAN to be "TRK-aware", explained later in this documentation.<br>
    1642. 

  1642. <br>
    1643. 

  1643. Setproxy sets the proxy settings for these applications:<br>
    1644. 

  1644. <br>
    1645. 

  1645. -wget<br>
    1646. 

  1646. -links<br>
    1647. 

  1647. -ClamAv<br>
    1648. 

  1648. -F-prot<br>
    1649. 

  1649. -BitDefender<br>
    1650. 

  1650. -general http_proxy environment variable</p>
    1651. 

  1651. <p>Also available for reading is the online manpage:</p>
    1652. 

  1652. <p><a href="http://trinityhome.org/manpages/man8/setproxy.8.html">http://trinityhome.org/manpages/man8/setproxy.8.html</a></p>
    1653. 

  1653. <p><br>
    1654. 

  1654. &nbsp;</p>
    1655. 

  1655. <p></p><br><a name="C3E9S86L5Q2DV4J2X7FRSW3NCGQ426N40T3HR0UMGLR1F" &nbsp;="" id="C3E9S86L5Q2DV4J2X7FRSW3NCGQ426N40T3HR0UMGLR1F"></a><h1>2.19 Ntfsundeleteall</h1><p>This script is a simple wrapper for the utility 'ntfsundelete'<br>
    1656. 

  1656. <br>
    1657. 

  1657. What it does is <strong>find all deleted files on an ntfs volume and tries to recover them</strong>.
    1658. 

  1658. It does this by looking for traces in the ntfs Master File Table and
    1659. 

  1659. sees whether the file is still available on the disk (or partially
    1660. 

  1660. overwritten). It 's a good utility that recovers your files with the
    1661. 

  1661. original filename but without the relevant path in front. So to avoid
    1662. 

  1662. double recovered filenames, I 've written the script so that it
    1663. 

  1663. prepends the original inode (=internal number for the file on the
    1664. 

  1664. filesystem) before the filename, so you always have a unique filename.
    1665. 

  1665. It 's up to you to rename the files afterwards, but at least you have
    1666. 

  1666. the original name in the recovered filename.<br>
    1667. 

  1667. <br>
    1668. 

  1668. <strong>Here 's how the script works</strong><br>
    1669. 

  1669. <br>
    1670. 

  1670. Suppose you have the volume /dev/hda1 in ntfs from which you wish to recover files.<br>
    1671. 

  1671. Make sure this volume is NOT mounted<br>
    1672. 

  1672. Prepare a place to which you can store your recovered files. Recovered
    1673. 

  1673. files will never be written to the original partition from which you
    1674. 

  1674. recover them because the risk exists you will overwrite other files
    1675. 

  1675. that still need recovery. Let 's say you have space on a network volume
    1676. 

  1676. that you 've mounted on /mnt0 (for this procedure, see the section
    1677. 

  1677. "Getting around with commands"), with a subdir called "recovered"<br>
    1678. 

  1678. Here 's the syntax of ntfsundeleteall: <br>
    1679. 

  1679. ntfsundeleteall Device Savedir [minimum percentage] --force<br>
    1680. 

  1680. <br>
    1681. 

  1681. Now here 's how we do it in our example:<br>
    1682. 

  1682. 'ntfsundeleteall /dev/hda1 /mnt0/recovered'<br>
    1683. 

  1683. <br>
    1684. 

  1684. This is very simple, this will recover any file it finds, even if only
    1685. 

  1685. 1% of the file is recoverable. You 're probably not interested in that,
    1686. 

  1686. because these files are most likely to be corrupt and unusable, so you
    1687. 

  1687. add a parameter on the percentage you wish the file is recoverable. If
    1688. 

  1688. we only want 100% recoverability, make the command like this:<br>
    1689. 

  1689. <br>
    1690. 

  1690. 'ntfsundeleteall /dev/hda1 /mnt0/recovered 100'<br>
    1691. 

  1691. <br>
    1692. 

  1692. You will see the directory /mnt0/recovered filling up with recovered files, hopefully your file is in there.<br>
    1693. 

  1693. <br>
    1694. 

  1694. You might have noticed the parameter "--force". This will only skip the
    1695. 

  1695. check that your filesystem is ntfs, you can use this if you think your
    1696. 

  1696. filesystem is so badly damaged that it won 't even be recognized
    1697. 

  1697. anymore, but I doubt you will be even capable of recovering any files
    1698. 

  1698. then.<br>
    1699. 

  1699. <br>
    1700. 

  1700. Another recommendation I can give you is Photorec. Photorec is a third
    1701. 

  1701. party utility that is able to recover files in a unique way: it is
    1702. 

  1702. independent of the filesystem, it just does raw read of the disk (tries
    1703. 

  1703. to use as much info as it can from whatever filesystem there was on it)
    1704. 

  1704. and tries to recognize known document formats to recover whatever it
    1705. 

  1705. can find. Although the name implies it might only serve to recover
    1706. 

  1706. pictures, it can in fact recover any kind of important document,
    1707. 

  1707. including word and excel, but also file archives such as zip and tar.gz.<br>
    1708. 

  1708. <br>
    1709. 

  1709. The only thing you won 't get from this utility is the original
    1710. 

  1710. filename, so you 'll have to sort out your recovered documents one by
    1711. 

  1711. one.</p><br><a name="MFRIGTQ75RPR5IIC4TXNKUF95JATHDEUIV3PEIMA01RV9" &nbsp;="" id="MFRIGTQ75RPR5IIC4TXNKUF95JATHDEUIV3PEIMA01RV9"></a><h1>2.13 Getswap</h1><p>Find
    1712. 

  1712. swapspace in Windows pagefiles and swap partitions and use it as
    1713. 

  1713. tempspace. This script is called upon by virusscan and updatetrk to
    1714. 

  1714. find more working memory. In normal circumstances your available ram
    1715. 

  1715. should suffise. </p>
    1716. 

  1716. <p>Getswap will remount /dev/shm and make more shared memory available
    1717. 

  1717. (in e.g. /tmp/) Sometimes you have too little RAM, so a swapdisk is a
    1718. 

  1718. reasonable alternative to gain memory. </p>
    1719. 

  1719. <h2>USAGE  </h2>
    1720. 

  1720. <p>
    1721. 

  1721. 

  1722. 

  1723.  	<style type="text/css">
    1724. 

  1724. 	<!--
    1725. 

  1725. 		@page { margin: 0.79in }
    1726. 

  1726. 		P { margin-bottom: 0.08in }
    1727. 

  1727. 	-->
    1728. 

  1728. 	</style>
    1729. 

  1729. </p><p>getswap -s &lt;SIZE in % of total memory&gt; -d -f</p>
    1730. 

  1730. <p></p>
    1731. 

  1731. <p><size memory="" total="" of="" in="">-s SIZE: this parameter allows you to tweak how much of the ram will be made available for /dev/shm (=/tmp in TRK). <br>
    1732. 

  1732. Sometimes you need a huge amount of tempspace. With this parameter you
    1733. 

  1733. can specify the size in percentage of the total amount of memory
    1734. 

  1734. (RAM+swap). Default figure is 50%. </size></p>
    1735. 

  1735. <p><size memory="" total="" of="" in="">-d: disable swap usage and return to original memory situation if possible </size></p>
    1736. 

  1736. <p><size memory="" total="" of="" in="">-f: force disabling even if too much tempspace is used. Will not work if the tempspace is more than 100% of the amount of RAM. <br>
    1737. 

  1737. Will fail at even less.  </size></p><br><a name="U49HULJB0RZJRSQX054MZS1LH8P05M7QG7X0I628MRH48" &nbsp;="" id="U49HULJB0RZJRSQX054MZS1LH8P05M7QG7X0I628MRH48"></a><h1>2.14 Trinisup</h1><p>
    1738. 

  1738. 

  1739. 

  1740.  	<style type="text/css">
    1741. 

  1741. 	<!--
    1742. 

  1742. 		@page { margin: 0.79in }
    1743. 

  1743. 		P { margin-bottom: 0.08in }
    1744. 

  1744. 		H2 { margin-bottom: 0.08in }
    1745. 

  1745. 	-->
    1746. 

  1746. 	</style> 
    1747. 

  1747. 

  1748. </p>
    1749. 

  1749. <p>Trinisup is a tiny utility that connects to a remote server and sets
    1750. 

  1750. up a tunnel to your local TRK. It allows the TRK support team to
    1751. 

  1751. connect to your TRK and share a local console, allowing full access to
    1752. 

  1752. your computer. Trinisup uses ssh with a private key to connect as a
    1753. 

  1753. user to the remote trinityhome.org support server. This user is not
    1754. 

  1754. active until the support team has activated it. So in order to get
    1755. 

  1755. help, you will first have to contact the TRK guys, who can then
    1756. 

  1756. activate this user and provide assistance.</p>
    1757. 

  1757. <h2>USAGE</h2>
    1758. 

  1758. <p>Usage is very simple. Just run 'trinisup'. By default it maps port
    1759. 

  1759. 30000 to your local port 22 (which runs an ssh server). If port 30000
    1760. 

  1760. is already occupied, you can specify an alternate port as an argument
    1761. 

  1761. to trinisup. <br>
    1762. 

  1762. For example: 'trinisup 30001' <br>
    1763. 

  1763. Once the connection is established, you will get a non-interactive message displaying that you are connected. <br>
    1764. 

  1764. Hitting &lt;enter&gt; will disconnect this session as long as no one is
    1765. 

  1765. connected to your computer. If a session is still in progress, this
    1766. 

  1766. connection will only exit as soon as the session is terminated or you
    1767. 

  1767. press ctrl+c <br>
    1768. 

  1768. You need tcp port 443 to be open to the outside world. All other connections happen inside the tunnel.</p>
    1769. 

  1769. <p>A shared local console can be accessed by tapping alt+F6</p>
    1770. 

  1770. <p>&nbsp;</p><br><a name="FKJT61FZ5GVCPWKXWTXSLUF6CQM3YVP36YM2QSRKZCNEY" &nbsp;="" id="FKJT61FZ5GVCPWKXWTXSLUF6CQM3YVP36YM2QSRKZCNEY"></a><h1>2.15 Pi - automated backup wrapper script originally for Partition Image</h1><p>Pi
    1771. 

  1771. is a third party tool contributed by a few great guys (also responsible
    1772. 

  1772. for the TRK&nbsp;menu) who wish to remain anonymous.&nbsp;Below is the
    1773. 

  1773. (elaborate) manpage.</p>
    1774. 

  1774. <h2>NAME</h2>
    1775. 

  1775. <p>pi - automated backup wrapper script originally for Partition Image</p>
    1776. 

  1776. <h2>SYNOPSIS</h2>
    1777. 

  1777. <p>pi -c -i [CONFIG FILE] -a -k [NUMBER OF COPIES] -d&nbsp;</p>
    1778. 

  1778. <h2>DESCRIPTION</h2>
    1779. 

  1779. <p>The pi script was designed for:</p>
    1780. 

  1780. <p>make possible a fully automated backup system.  <br>
    1781. 

  1781. facilitate the use of partimage.&nbsp;</p>
    1782. 

  1782. <h2>OPTIONS</h2>
    1783. 

  1783. <p>Type pi then &lt;RETURN&gt; to launch interactive mode.</p>
    1784. 

  1784. <dl compact="compact">
    1785. 

  1785.     <dt><b>-c :</b></dt>
    1786. 

  1786.     <dd> <b>search a
    1787. 

  1787. pi.cfg configuration file and loads it if found. If this file contains
    1788. 

  1788. the parameter AUTO=1, the backup will run automatically. </b></dd>
    1789. 

  1789.     <dt><b>-a :</b></dt>
    1790. 

  1790.     <dd> <b>Starts the backup automatically (same as AUTO=1 in pi.cfg) </b></dd>
    1791. 

  1791.     <dt><b>-k # :</b></dt>
    1792. 

  1792.     <dd> <b>This option (keep) sets the number of copies of the image to be kept. See details in Section </b><i>Old backups</i> below </dd>
    1793. 

  1793.     <dt><b>-d :</b></dt>
    1794. 

  1794.     <dd> <b>debug
    1795. 

  1795. mode. The backup will not be actually launched and the command that
    1796. 

  1796. would have launched partimage is only displayed on the screen </b></dd>
    1797. 

  1797.     <dt><b>Trick :</b></dt>
    1798. 

  1798.     <dd> <b>If you execute pi with -c -d, you will see which partition(s) and destination are selected from the found pi.cfg file.<br>
    1799. 

  1799.     </b>     </dd>
    1800. 

  1800. </dl>
    1801. 

  1801. <h2>FILES</h2>
    1802. 

  1802. <dl compact="compact">
    1803. 

  1803.     <dt><b>pi.cfg :</b></dt>
    1804. 

  1804.     <dd> <b>pi can use a configuration file. This file is not needed in interactive mode. This file has two purposes : </b>
    1805. 

  1805.     <dl compact="compact">
    1806. 

  1806.         <dt><br>
    1807. 

  1807.         </dt>
    1808. 

  1808.         <dd>
    1809. 

  1809.         <dl compact="compact">
    1810. 

  1810.             <dt><b>Add menu entries
    1811. 

  1811.             <dd> pi automatically creates the list of your local drives. If you want to backup to a network drive, you must add it in pi.cfg </dd>
    1812. 

  1812.             </b></dt>
    1813. 

  1813.             <dt><b>Automatic mode
    1814. 

  1814.             <dd>
    1815. 

  1815. All selections can be set in pi.cfg and then pi can run without any
    1816. 

  1816. user intervention A pi.cfg file corresponding to your backup is created
    1817. 

  1817. in the destination directory each time a backup is successful. </dd>
    1818. 

  1818.             </b></dt>
    1819. 

  1819.         </dl>
    1820. 

  1820.         </dd>
    1821. 

  1821.     </dl>
    1822. 

  1822.     </dd>
    1823. 

  1823.     <dt><b>partition_info.txt :</b></dt>
    1824. 

  1824.     <dd> <b>Each time you make a backup, a file named </b><i>partition_info.txt</i>
    1825. 

  1825. is created in the destination directory. This file contains information
    1826. 

  1826. on your partitions (all partitions of all local drives, even USB disks
    1827. 

  1827. or USB keys). This may be useful in case you have to repartition your
    1828. 

  1828. disk after a crash. <br>
    1829. 

  1829.     <b>WARNING :</b> partimage is unable to
    1830. 

  1830. restore an image on a partition smaller than the original partition.
    1831. 

  1831. See the documentation of partimage for details. Therefore it is very
    1832. 

  1832. important to know the size of the partition that an image contains.
    1833. 

  1833. unpi, the complementary script of pi, will give this information but
    1834. 

  1834. you can also find it in partition_info.txt. </dd>
    1835. 

  1835.     &nbsp;</dl>
    1836. 

  1836.     <h2>MOUNT POINT</h2>
    1837. 

  1837.     <p>pi mounts the backup unit you have chosen on /sysbackup&nbsp;</p>
    1838. 

  1838.     <h2>RELATED SCRIPTS</h2>
    1839. 

  1839.     <p>Well, you have make an image not only for the fun, you may want to restore it one day. You can use partimage or <b>unpi</b> the little brother of pi which will help you for restore in the same way that pi helps you for backup.&nbsp;</p>
    1840. 

  1840.     <h2>INTERACTIVE MODE</h2>
    1841. 

  1841.     <p>If the pi script is run with the <b>-c</b>
    1842. 

  1842. option, and there is a pi.cfg file in the root directory of any disk in
    1843. 

  1843. the machine, or in /trk/trk3/pi or in /etc/pi and all options necessary
    1844. 

  1844. are set, then pi is launched automatically, using the pi.cfg
    1845. 

  1845. parameters. If pi.cfg is not found or uncomplete, pi exits immediatly.</p>
    1846. 

  1846.     <dl compact="compact">
    1847. 

  1847.         <dt>*</dt>
    1848. 

  1848.         <dd> If the pi script is run without the <b>-c</b> option then pi is launched interactively and three successive menus ask the user to select: </dd>
    1849. 

  1849.         <dt>*</dt>
    1850. 

  1850.         <dd> The unit or units to save. </dd>
    1851. 

  1851.         <dt>*</dt>
    1852. 

  1852.         <dd> The destination disk that store the backup (local drive or network) </dd>
    1853. 

  1853.         <dt>*</dt>
    1854. 

  1854.         <dd> The destination disk list may be customized using MENU_UNIT[], MENU_LOGIN[] and MENU_PASS[] in pi.cfg file.  </dd>
    1855. 

  1855.         <dt>*</dt>
    1856. 

  1856.         <dd> The destination directory          </dd>
    1857. 

  1857.         <br>
    1858. 

  1858.     </dl>
    1859. 

  1859.     <dl compact="compact">
    1860. 

  1860.         <dt>a) The partitions to save</dt>
    1861. 

  1861.         <dd>Here
    1862. 

  1862. you can select a partition in the list of partitions found by the
    1863. 

  1863. system, or select "information on partitions" for more information on
    1864. 

  1864. your partitions, or select "select several partitions”. In this case
    1865. 

  1865. you must type the names of the partitions to save as they appear in the
    1866. 

  1866. list, separated by spaces. For example: <br>
    1867. 

  1867.         hda1 sda1 </dd>
    1868. 

  1868.         <dt>b) The destination drive (the one on which the backup will be saved).</dt>
    1869. 

  1869.         <dd>A
    1870. 

  1870. list presents successively the units defined in pi.cfg and the units
    1871. 

  1871. that the system finds on local disks. After selecting the unit, the
    1872. 

  1872. script will attempt to mount the disk. If it fails, an error message is
    1873. 

  1873. sent and the script stops. Possible causes include, among others: <dl compact="compact">
    1874. 

  1874.             <dt><br>
    1875. 

  1875.             </dt>
    1876. 

  1876.             <dd>
    1877. 

  1877.             <dl compact="compact">
    1878. 

  1878.                 <dt> <br>
    1879. 

  1879.                 </dt>
    1880. 

  1880.                 <dd>1.
    1881. 

  1881. You have chosen an NTFS partition and Windows has been put in hibernate
    1882. 

  1882. state on the disk. In this case, NTFS partitions are not closed and
    1883. 

  1883. they cannot be mounted rread/write, you can only read. It is possible
    1884. 

  1884. to make a backup of such partition, but you cannot use it as the
    1885. 

  1885. destination unit. To avoid this error, completely shut down Windows
    1886. 

  1886. before starting TRK Autobackup. Since TRK revision 3.4 : hibernated
    1887. 

  1887. partition cannot be written, but the state of other not closed
    1888. 

  1888. partitions is normally solved by ntfs-3g which is able to successfully
    1889. 

  1889. mount them for writing. However it is always better to properly shut
    1890. 

  1890. down Windows before making a backup. </dd>
    1891. 

  1891.                 <dt> <br>
    1892. 

  1892.                 </dt>
    1893. 

  1893.                 <dd>2.
    1894. 

  1894. The system also put in the list extended partitions, which can disturb.
    1895. 

  1895. An extended partition is a mere container and cannot receive files. For
    1896. 

  1896. information on how your partitions are made, use the "information about
    1897. 

  1897. partitions" option of the main menu. </dd>
    1898. 

  1898.                 <dt> <br>
    1899. 

  1899.                 </dt>
    1900. 

  1900.                 <dd>3.
    1901. 

  1901. You have selected a network drive and the network connection is not
    1902. 

  1902. good, or your LOGIN and PASSWORD parameters are incorrect. </dd>
    1903. 

  1903.             </dl>
    1904. 

  1904.             <p>&nbsp;</p>
    1905. 

  1905.             </dd>
    1906. 

  1906.         </dl>
    1907. 

  1907.         </dd>
    1908. 

  1908.         <dt>c) The destination directory</dt>
    1909. 

  1909.         <dd>In
    1910. 

  1910. the destination device previously defined, the script can either use
    1911. 

  1911. the existing directories that are presented here, or a new directory:
    1912. 

  1912. in this case select the last option and type a directory name <b>without spaces in its name.</b> We are in Linux which does not accept spaces in the names of directories and files. <br>
    1913. 

  1913.         Then the script will present you a summary of your choices that you can confirm or reject by <b>y</b>(es). or <b>n</b>(o).
    1914. 

  1914. In the last case the script closes. Finally before running the backup a
    1915. 

  1915. last message information is presented. You can again interrupt the
    1916. 

  1916. process by pressing any key other than SPACE or ENTER, or type on ENTER
    1917. 

  1917. to immediately start the backup, or let the script look after himself.
    1918. 

  1918. After 15 seconds, if you do nothing, it will launch the backup. </dd>
    1919. 

  1919.     </dl>
    1920. 

  1920.     <h2>AUTOMATIC MODE</h2>
    1921. 

  1921.     <p>To
    1922. 

  1922. enable automatic operation, you must file a pi.cfg in the root
    1923. 

  1923. directory of a partition of the machine (all mountable partitions are
    1924. 

  1924. scanned) or in /trk/trk3/pi (for TRK users) or in /etc/pi and the
    1925. 

  1925. script must be launched with option <b>-c</b>. The first file found will be used.  <br>
    1926. 

  1926. If the file is found, the parameters are loaded and the backup is
    1927. 

  1927. started. This backup will be excuted without any user intervention if
    1928. 

  1928. all necessary parameters are set in the file and if AUTO has been set
    1929. 

  1929. to 1. but there are two confirmation messages which are displayed for
    1930. 

  1930. 10 or 15 seconds, and during this time you may stop the process before
    1931. 

  1931. the backup starts. If AUTO=0, then a confirmation is requested from the
    1932. 

  1932. user. If you add the command pi <b>-c</b>
    1933. 

  1933. to your trklocscript file in the trk3 directory, then you can have a CD
    1934. 

  1934. or USB key which will backup the partitions you have defined without
    1935. 

  1935. any intervention of the operator : just boot on the CD or the USB key,
    1936. 

  1936. and you are done. This is handy if you want users who don't know
    1937. 

  1937. anything about computers to be able to save their system disk from time
    1938. 

  1938. to time.</p>
    1939. 

  1939.     <p>&nbsp;</p>
    1940. 

  1940.     <p>To setup automatic mode, the recommended steps are :</p>
    1941. 

  1941.     <p>&nbsp;</p>
    1942. 

  1942.     <dl compact="compact">
    1943. 

  1943.         <dt>*</dt>
    1944. 

  1944.         <dd> Use pi in normal interactive mode to make your first backup. </dd>
    1945. 

  1945.         <dt>*</dt>
    1946. 

  1946.         <dd>
    1947. 

  1947. Once you are satisfied and anything works as you want, locate the the
    1948. 

  1948. pi.cfg file which has been created in your successful backup directory </dd>
    1949. 

  1949.         <dt>*</dt>
    1950. 

  1950.         <dd>
    1951. 

  1951. Copy this file in the root of your first drive (any other drive can be
    1952. 

  1952. chosen, but it is more easy to use the first one, generally sda1 or c:)
    1953. 

  1953. </dd>
    1954. 

  1954.         <dt>*</dt>
    1955. 

  1955.         <dd>You can edit this file in Linux or
    1956. 

  1956. Windows if you want to change something, Windows end of lines are
    1957. 

  1957. supported. Complete description of this file format is explained below
    1958. 

  1958. in the section <i>CONFIGURATION FILE</i>. </dd>
    1959. 

  1959.         <dt>*</dt>
    1960. 

  1960.         <dd> At this point, if you run <b>pi -c</b> your backup will start automatically. You will have two occasions offered to you to stop it.
    1961. 

  1961.         <p>If
    1962. 

  1962. you add the command pi -c in the trklocscript file in the trk3
    1963. 

  1963. directory of your TRK disk, then it is possible to start a backup by
    1964. 

  1964. just booting on this disk, without any further intervention.
    1965. 

  1965. Complementary details are found in the FAQ. $$$</p>
    1966. 

  1966.         </dd>
    1967. 

  1967.     </dl>
    1968. 

  1968.     <h2>FILES CREATED</h2>
    1969. 

  1969.     <p>Pi creates three files (or file set) in the destination directory :</p>
    1970. 

  1970.     <dl compact="compact">
    1971. 

  1971.         <dt>*</dt>
    1972. 

  1972.         <dd> The partimage files with extension .000, .001 .002 etc. </dd>
    1973. 

  1973.         <dt>*</dt>
    1974. 

  1974.         <dd> a pi.cfg file with the configuration you have just used and which can be used for automatic process.  </dd>
    1975. 

  1975.         <dt>*</dt>
    1976. 

  1976.         <dd>a
    1977. 

  1977. partition-info.txt file, which contains the details of your hard disks
    1978. 

  1978. configuration. It may be very useful in case you must reformat your
    1979. 

  1979. disk <p>&nbsp;</p>
    1980. 

  1980.         </dd>
    1981. 

  1981.     </dl>
    1982. 

  1982.     <h2>BACKUP SCREEN</h2>
    1983. 

  1983.     <p>During
    1984. 

  1984. the backup, partimage shows a screen that displays the progress of the
    1985. 

  1985. operation. Despite the message that is displayed at the bottom of the
    1986. 

  1986. screen, it is unfortunately not possible to interrupt a backup because
    1987. 

  1987. the * option does not work. This is a bug in partimage. If you want to
    1988. 

  1988. stop anyway, you can do a ctrl+alt+del. You will just need to think
    1989. 

  1989. about delete the created files.<br>
    1990. 

  1990.     &nbsp;</p>
    1991. 

  1991.     <h2>OLD BACKUPS</h2>
    1992. 

  1992.     <p>The
    1993. 

  1993. script handles the number of copies of your partitions you want to
    1994. 

  1994. keep. The default is 2 (the copy you just made, and one older). This
    1995. 

  1995. value can be changed with the option -k. 4 will mean : the image just
    1996. 

  1996. made + 3 older copies (total : 4 copies). Examples :</p>
    1997. 

  1997.     <dl compact="compact">
    1998. 

  1998.         <dt><br>
    1999. 

  1999.         </dt>
    2000. 

  2000.         <dd> -k1 : One image : all older images are deleted <br>
    2001. 

  2001.         -k2 : The last image + 1 older image  (default) <br>
    2002. 

  2002.         -k3 : The last image + 2 older images <br>
    2003. 

  2003.         <br>
    2004. 

  2004.         -kn : The last image + (n-1) older images <br>
    2005. 

  2005.         <br>
    2006. 

  2006. -k0 : Special mode (see below : IN CASE OF LOW SPACE IN THE
    2007. 

  2007. DESTINATION) The digit does not mean the number of older copies but the
    2008. 

  2008. total number : -k2 will not keep two older copies but one. </dd>
    2009. 

  2009.     </dl>
    2010. 

  2010.     <p>The behaviour is the following :</p>
    2011. 

  2011.     <dl compact="compact">
    2012. 

  2012.         <dt><br>
    2013. 

  2013.         </dt>
    2014. 

  2014.         <dd>
    2015. 

  2015.         <dl compact="compact">
    2016. 

  2016.             <dt> <br>
    2017. 

  2017.             </dt>
    2018. 

  2018.             <dd>a) the current backup is performed into temporary files. </dd>
    2019. 

  2019.             <dt> <br>
    2020. 

  2020.             </dt>
    2021. 

  2021.             <dd>b) these temporary backup files are renamed with their final backup filenames, like 20YY-MM-DD-X-hda1.000 </dd>
    2022. 

  2022.             <dt> <br>
    2023. 

  2023.             </dt>
    2024. 

  2024.             <dd>c)
    2025. 

  2025. a sub-directory is created with the following name:
    2026. 

  2026. 20YY-MM-DD-saved_partition, for example: 2010-06-22-hda2 and the
    2027. 

  2027. current backup files of this partition are transferred under this
    2028. 

  2028. sub-directory. </dd>
    2029. 

  2029.             <dt> <br>
    2030. 

  2030.             </dt>
    2031. 

  2031.             <dd>d)
    2032. 

  2032. depending of the number specified with the k option, old backups are
    2033. 

  2033. deleted: for example, if user has specified pi -c -k 4 and there are
    2034. 

  2034. already 3 existing 20YY-MM-DD-saved_partition sub-directories, the
    2035. 

  2035. oldest one will be automatically removed once the current backup will
    2036. 

  2036. have successfully completed. </dd>
    2037. 

  2037.             &nbsp;</dl>
    2038. 

  2038.             </dd>
    2039. 

  2039.         </dl>
    2040. 

  2040.         <p>&nbsp;</p>
    2041. 

  2041.         <h2>CONFIGURATION FILE (pi.cfg)</h2>
    2042. 

  2042.         <p>&nbsp;</p>
    2043. 

  2043.         <p>CAUTION: The name of the configuration file is pi.cfg or PI.CFG or Pi.cfg.  ALL OTHER SPELLINGS WILL BE IGNORED.</p>
    2044. 

  2044.         <p>Spaces are not allowed in file names or directory (replace them by _ or -)</p>
    2045. 

  2045.         <p>When
    2046. 

  2046. you have completed a backup, the destination directory contains a
    2047. 

  2047. pi.cfg file corresponding to the options you had choosed. Here is a
    2048. 

  2048. possible example :</p>
    2049. 

  2049.         <p>&nbsp;</p>
    2050. 

  2050.         <p>___________________________________________________________________</p>
    2051. 

  2051.         <p># No space before and after the = sign  <br>
    2052. 

  2052.         # The names are case-sensitive  <br>
    2053. 

  2053.         # No backslashs: \, only slashs/</p>
    2054. 

  2054.         <p>&nbsp;</p>
    2055. 

  2055.         <p># MENU_UNIT[x]=//192.168.1.4/sysbackup specify a network disc to be displayed in the interactive choice of BACKUPDRIVE <br>
    2056. 

  2056. # MENU_LOGIN[x]=//192.168.1.4/sysbackup specify login of the network
    2057. 

  2057. disc[x] displayed in the interactive choice of BACKUPDRIVE <br>
    2058. 

  2058. # MENU_PASS[x]=//192.168.1.4/sysbackup specify password of a network
    2059. 

  2059. disc[x] displayed in the interactive choice of BACKUPDRIVE <br>
    2060. 

  2060.         # x index start at number 1. Several network discs may be specified using different indexes. <br>
    2061. 

  2061.         # Destination automatic backup unit. It may be a network drive, for example:  <br>
    2062. 

  2062.         # BACKUPDRIVE =//192.168.1.4/sysbackup  <br>
    2063. 

  2063.         # In this case the parameters LOGIN and PASSWORD are required  <br>
    2064. 

  2064.         # Or a local unit such as BACKUPDRIVE=/sdb1  <br>
    2065. 

  2065.         BACKUPDRIVE=//192.168.1.4/sysbackup  <br>
    2066. 

  2066.         LOGIN=mylogin  <br>
    2067. 

  2067.         PASSWORD=mypass</p>
    2068. 

  2068.         <p># Backup directory in automatic mode  <br>
    2069. 

  2069.         DEST=Lawrence</p>
    2070. 

  2070.         <p># Beginning of backup files' names; <br>
    2071. 

  2071.         # pi will generate 20YY-MM-DD-X- prefix in the filename of the unit to backup <br>
    2072. 

  2072.         # (X=A for automatic and I for Interactive) and partimage will add the extension 000, 001 and so on.  <br>
    2073. 

  2073.         # Example : in Automatic mode, the resulting file should be : <br>
    2074. 

  2074.         # “<b>20YY-MM-DD-A-hda1.000</b>”  <br>
    2075. 

  2075.         # Example : in Intercative mode, the resulting file should be : <br>
    2076. 

  2076.         # “<b>20YY-MM-DD-I-hda1.000</b>”</p>
    2077. 

  2077.         <p># Partitions to backup in automatic mode  <br>
    2078. 

  2078.         # If there are multiple partitions, separate them by spaces,  <br>
    2079. 

  2079.         # and put it between quotation marks  <br>
    2080. 

  2080.         # Example PARTITION="sda1 sda5"  <br>
    2081. 

  2081.         PARTITION="sda1"</p>
    2082. 

  2082.         <p># If AUTO=1 and a pi.cfg configuration file was found,  <br>
    2083. 

  2083.         # the backup is done without any user intervention  <br>
    2084. 

  2084.         AUTO=1  <br>
    2085. 

  2085.         KEEP=2</p>
    2086. 

  2086.         <p>___________________________________________________________________</p>
    2087. 

  2087.         <p>&nbsp; </p>
    2088. 

  2088.         <p><b>Remarks: </b></p>
    2089. 

  2089.         <p>Always
    2090. 

  2090. use the forward slash and not the backslash: we are in Linux and not in
    2091. 

  2091. Windows. Long before Microsoft existed, the backslash was an escape
    2092. 

  2092. character on Unix. Only Microsoft's commitment to be "like no other"
    2093. 

  2093. has led to ignore this meaning and use the backslash in directories'
    2094. 

  2094. path. Linux meets Unix standards. There are never spaces before or
    2095. 

  2095. after the equal sign under penalty of non-functioning of the script.
    2096. 

  2096. The parameters' names are always written in uppercase.</p>
    2097. 

  2097.         <p><b>BACKUPDRIVE:</b></p>
    2098. 

  2098.         <p>You
    2099. 

  2099. may indicate a network drive, and in this case it will be also
    2100. 

  2100. mandatory to specify LOGIN and PASSWORD. The format will be:
    2101. 

  2101. //xxx.xxx.xxx.xxx/shared_directory_name. This can also be a local drive
    2102. 

  2102. and in this case the format will be, for instance: /dev/sda1. It is
    2103. 

  2103. prudent to use the complete device names returned by info on
    2104. 

  2104. partitions. /sda1 should work too, but /dev/sda1 is safer.</p>
    2105. 

  2105.         <p><b>DEST:</b></p>
    2106. 

  2106.         <p>This
    2107. 

  2107. is the destination directory to be used (and possibly created) in the
    2108. 

  2108. unit selected by BACKUPDRIVE. It is possible to select a subdirectory,
    2109. 

  2109. but in this case it is mandatory that the directory already exists.
    2110. 

  2110. Example:</p>
    2111. 

  2111.         <p>&lt;FILE&gt; - &lt;partition&gt; .000 DEST=backup/system/unite_c</p>
    2112. 

  2112.         <p>If the saved partitions are hda1 and hda5, the following files are created (X=A or I):</p>
    2113. 

  2113.         <p>20YY-MM-DD-X-hda1.000  20YY-MM-DD-X-hda5.000</p>
    2114. 

  2114.         <p><b>PARTITION:</b></p>
    2115. 

  2115.         <p>This parameter contains the names of the partitions to backup. If there is one partition, you can simply specify it as follows: <br>
    2116. 

  2116.         &nbsp; PARTITION=hda1 <br>
    2117. 

  2117.         &nbsp; If there are multiple partitions, they must be separated by spaces and put  between quotation marks: <br>
    2118. 

  2118.         &nbsp; PARTITION="hda1 hda5" <br>
    2119. 

  2119. &nbsp; It is allowed to have spaces between quotation marks but it is
    2120. 

  2120. prohibited outside. PARTITION= "hda1 hda5" will not work because you
    2121. 

  2121. should never have a space before and after the = sign <br>
    2122. 

  2122.         &nbsp; Note the different syntax from BACKUPDRIVE. There's no slash or /dev/.</p>
    2123. 

  2123.         <p>&nbsp;</p>
    2124. 

  2124.         <p><b>AUTO:</b></p>
    2125. 

  2125.         <p>AUTO=1
    2126. 

  2126. enables automatic backup and a delay is placed on the confirmation
    2127. 

  2127. messages. It is possible to interrupt the process by pressing any key
    2128. 

  2128. other than SPACE or ENTER during the period. After the delay and
    2129. 

  2129. without user intervention, backup is started.</p>
    2130. 

  2130.         <p>&nbsp;</p>
    2131. 

  2131.         <p>&nbsp;</p>
    2132. 

  2132.         <p><b>KEEP:</b></p>
    2133. 

  2133.         <p>This parameter has the same meaning as the parameter -k (see the section "Old backups" above). The default value is 2.</p>
    2134. 

  2134.         <p>&nbsp;</p>
    2135. 

  2135.         <h2>IN CASE OF LOW SPACE ON THE DESTINATION</h2>
    2136. 

  2136.         <p>using -k0 option</p>
    2137. 

  2137.         <p>In
    2138. 

  2138. the normal process described above, there is a moment where you have
    2139. 

  2139. two images of your partition : one that is currently on temporary files
    2140. 

  2140. and one which is in the normal directory. If you do not have enough
    2141. 

  2141. space on your disk for this, you can use the <b>-k</b> option with a value of 1 or 0</p>
    2142. 

  2142.         <p>&nbsp;</p>
    2143. 

  2143.         <dl compact="compact">
    2144. 

  2144.             <dt><b>-k1 </b></dt>
    2145. 

  2145.             <dd> <b>If
    2146. 

  2146. you have enough disc space for two copies of the image but want to keep
    2147. 

  2147. only the last, this parameter will cause the following behaviour: </b>
    2148. 

  2148.             <dl compact="compact">
    2149. 

  2149.                 <dt><br>
    2150. 

  2150.                 </dt>
    2151. 

  2151.                 <dd>
    2152. 

  2152.                 <p><b>a) creation of the new image in temporary files <br>
    2153. 

  2153.                 b) if the image was successful, the old image is erased <br>
    2154. 

  2154.                 c) the new image files are renamed. <br>
    2155. 

  2155. If the image had failed, temporary files remain on the disk. They will
    2156. 

  2156. be overwritten by the new image when you will try again to make one.
    2157. 

  2157. You can also delete them yourself. </b></p>
    2158. 

  2158.                 </dd>
    2159. 

  2159.             </dl>
    2160. 

  2160.             </dd>
    2161. 

  2161.             <dt><b>-k0</b></dt>
    2162. 

  2162.             <dd> <b>If you have just the place for an image, this parameter will give the following behavior:  </b>
    2163. 

  2163.             <dl compact="compact">
    2164. 

  2164.                 <dt><br>
    2165. 

  2165.                 </dt>
    2166. 

  2166.                 <dd> <b>a) erase the existing image <br>
    2167. 

  2167.                 b) creation of the new image <br>
    2168. 

  2168. Warning: this mode is not secure because if the creation of the new
    2169. 

  2169. image fails, the old image has already been erased. </b></dd>
    2170. 

  2170.             </dl>
    2171. 

  2171.             </dd>
    2172. 

  2172.         </dl>
    2173. 

  2173.         <p>&nbsp;</p>
    2174. 

  2174.         <h2>FAQ</h2>
    2175. 

  2175.         <dl compact="compact">
    2176. 

  2176.             <dt> <br>
    2177. 

  2177.             </dt>
    2178. 

  2178.             <dd>Q: How can I make a fully automatic image system for my hard disk ?  </dd>
    2179. 

  2179.             <dt> <br>
    2180. 

  2180.             </dt>
    2181. 

  2181.             <dd>A:
    2182. 

  2182. The first step is to setup a pi.cfg file which will do what you want :
    2183. 

  2183. save your system partition or all your partitions to a given
    2184. 

  2184. destination. <br> Once this is done and you can run pi -c and get the
    2185. 

  2185. result you want, the hardest part is done. See above for all
    2186. 

  2186. informations on this step. <br>
    2187. 

  2187.             Now you have to run this automatically when TRK starts. This is easy :
    2188. 

  2188.             <dl compact="compact">
    2189. 

  2189.                 <dt><br>
    2190. 

  2190.                 </dt>
    2191. 

  2191.                 <dd>
    2192. 

  2192.                 <dl compact="compact">
    2193. 

  2193.                     <dt>*</dt>
    2194. 

  2194.                     <dd> Add a file with the name "trklocscript" in the trk3 directory of your TRK USB key or your TRK CD.  </dd>
    2195. 

  2195.                     <dt>*</dt>
    2196. 

  2196.                     <dd> In this file add this line : <br>
    2197. 

  2197.                     pi -c <br>
    2198. 

  2198.                     You are done.  </dd>
    2199. 

  2199.                 </dl>
    2200. 

  2200.                 </dd>
    2201. 

  2201.             </dl>
    2202. 

  2202.             </dd>
    2203. 

  2203.             <dt> <br>
    2204. 

  2204.             </dt>
    2205. 

  2205.             <dd>Q: My computer does not boot on an USB device and I must boot on CD. I cannot copy a file to a CD.  </dd>
    2206. 

  2206.             <dt> <br>
    2207. 

  2207.             </dt>
    2208. 

  2208.             <dd>A:
    2209. 

  2209. When you burn your TRK CD, be careful to let the session open. This can
    2210. 

  2210. be configured if you are using CdBurnerXP on windows. Some versions of
    2211. 

  2211. Nero automatically close the session and don't let you add anything. <br>
    2212. 

  2212.             - Open your CD in a CD burner program <br>
    2213. 

  2213.             - Choose the option to continue the CD  <br>
    2214. 

  2214.             - add trklocscript as described above in the trk3 directory <br>
    2215. 

  2215.             - burn your cd <br>
    2216. 

  2216.             - Run it. You are done.  </dd>
    2217. 

  2217.             <dt> <br>
    2218. 

  2218.             </dt>
    2219. 

  2219.             <dd>Q: And what will happen with this CD/USB key ? </dd>
    2220. 

  2220.             <dt> <br>
    2221. 

  2221.             </dt>
    2222. 

  2222.             <dd>A:
    2223. 

  2223. Just boot a computer which has a valid pi.cfg file in the root
    2224. 

  2224. directory of one of its disks, and the backup defined in that pi.cfg
    2225. 

  2225. file will be performed. If you had set AUTO=1, just sit back and relax
    2226. 

  2226. the job will be done automatically. If you are suspicious and want to
    2227. 

  2227. know what happens before it is performed, then set AUTO=0 and you will
    2228. 

  2228. have a confirmation screen. </dd>
    2229. 

  2229.             <dt> <br>
    2230. 

  2230.             </dt>
    2231. 

  2231.             <dd>Q: I am lazy and I want a simpler solution </dd>
    2232. 

  2232.             <dt> <br>
    2233. 

  2233.             </dt>
    2234. 

  2234.             <dd>A: OK. You must first create a TRK USB key with trk2usb.  <br>
    2235. 

  2235.             Add trklocsript to the trk3 directory of this key <br>
    2236. 

  2236. Ask a friend who has a computer which starts on USB key to start his
    2237. 

  2237. computer on your TRK USB key and to run the command : <br>
    2238. 

  2238.             trk2iso <br>
    2239. 

  2239.             N.B. He must first change to a directory with at least 150 Mo of free space <br>
    2240. 

  2240.             Then ask him to give you the iso file created.  <br>
    2241. 

  2241.             Burn it and you are done.  </dd>
    2242. 

  2242.             <dt> <br>
    2243. 

  2243.             </dt>
    2244. 

  2244.             <dd>Q: This is not so simple </dd>
    2245. 

  2245.             <dt> <br>
    2246. 

  2246.             </dt>
    2247. 

  2247.             <dd>A:
    2248. 

  2248. At first, yes. But once you have your USB key it is very easy to modify
    2249. 

  2249. it, and then ask your friend to create the new iso. If he is patient
    2250. 

  2250. enough, it is a good solution. <br>
    2251. 

  2251.             </dd>
    2252. 

  2252.             <dt> <br>
    2253. 

  2253.             </dt>
    2254. 

  2254.             <dd>Q: I don't want to run always pi on startup. Is it possible to have this feature enabled on a computer and not on another ?  </dd>
    2255. 

  2255.             <dt> <br>
    2256. 

  2256.             </dt>
    2257. 

  2257.             <dd>A:
    2258. 

  2258. Yes, it is easy : with the pi -c command in the trklocscript file, if a
    2259. 

  2259. computer has a pi.cfg file, pi will run when TRK starts. If a computer
    2260. 

  2260. does not have this file, then pi will appear for 3 seconds, then
    2261. 

  2261. disappear and the TRK menu will be shown. <dl compact="compact">
    2262. 

  2262.                 <dt><br>
    2263. 

  2263.                 </dt>
    2264. 

  2264.             </dl>
    2265. 

  2265.             </dd>
    2266. 

  2266.         </dl>
    2267. 

  2267.         <h2>LICENSE</h2>
    2268. 

  2268.         <p>Public domain</p>
    2269. 

  2269.         <h2>AUTHORS</h2>
    2270. 

  2270.         <p>Frank Michel (for the menus), Gaston and Averell</p><br><a name="3HU5ZWWY8SYP7AEGNHT9CEDCSWG7RQEJXZELK1AJJYYGZ" &nbsp;="" id="3HU5ZWWY8SYP7AEGNHT9CEDCSWG7RQEJXZELK1AJJYYGZ"></a><h1>2.20 Clonexp (obsoleted by mclone)</h1><p>
    2271. 

  2271. 

  2272. 

  2273.  	<style type="text/css">
    2274. 

  2274. 	<!--
    2275. 

  2275. 		@page { margin: 0.79in }
    2276. 

  2276. 		P { margin-bottom: 0.08in }
    2277. 

  2277. 	-->
    2278. 

  2278. 	</style> 
    2279. 

  2279. 

  2280. </p>
    2281. 

  2281. <p>Clonexp clones an ntfs partition to another computer over the
    2282. 

  2282. network. Both PCs must be running the same version of TRK.. The one who
    2283. 

  2283. is receiving the data must run with sshd enabled (triggerable from the
    2284. 

  2284. simple TRK menu)<br>
    2285. 

  2285. <br>
    2286. 

  2286. Basically what it does is run ntfsclone in save mode to stdout at one
    2287. 

  2287. computer and restore mode from stdin on the other, piping over ssh
    2288. 

  2288. between eachother.<br>
    2289. 

  2289. <br>
    2290. 

  2290. When running clonexp, make sure your source partition is smaller or
    2291. 

  2291. equal to what can fit on the destination. Ntfsclone (and subsequently
    2292. 

  2292. clonexp) cannot dynamically resize a partition, so it 's a good thing
    2293. 

  2293. to make the destination partition equal or bigger in size than the
    2294. 

  2294. source. Do this easily with parted, supplied on TRK. If your maximum
    2295. 

  2295. possible destination size is smaller than your source, try making your
    2296. 

  2296. source smaller with parted. At least, if the data on it is less than
    2297. 

  2297. the destination and the volume is not too fragmented.<br>
    2298. 

  2298. <br>
    2299. 

  2299. Also make sure neither of the local nor remote filesystems are mounted, or the script will exit.<br>
    2300. 

  2300. <br>
    2301. 

  2301. Clonexp can run in two modes: without any arguments, it runs in
    2302. 

  2302. interactive mode and prompts you for source device, destination host
    2303. 

  2303. and destination device. It will each time test whether these things
    2304. 

  2304. exist.<br>
    2305. 

  2305. <br>
    2306. 

  2306. You can also run it in a single commandline, in this way (drop the &lt;&gt;):<br>
    2307. 

  2307. clonexp &lt;sourcedevice&gt; &lt;destinationhost&gt;:&lt;destinationdevice&gt;<br>
    2308. 

  2308. e.g. 'clonexp /dev/hda1 192.168.0.7:/dev/hda1'<br>
    2309. 

  2309. <br>
    2310. 

  2310. It will prompt you once for the password you have entered on the remote
    2311. 

  2311. TRK machine and then start copying the data. There is also the option
    2312. 

  2312. '--bkupbr', which will first backup your partition bootrecord and later
    2313. 

  2313. save that as a file on your newly created partition. Although it may
    2314. 

  2314. never really serve, I give this opportunity should you ever be unable
    2315. 

  2315. to boot from the partition and you want to play around a bit with your
    2316. 

  2316. old bootrecord. This might as well completely obliterate your
    2317. 

  2317. partition, so use with caution (backups 'n stuff ready...)<br>
    2318. 

  2318. I was once able to make a cloned unbootable partition bootable this way
    2319. 

  2319. by afterwards running from the Windows XP recovery console and do a
    2320. 

  2320. chkdsk.<br>
    2321. 

  2321. It 's recommended you use clonexp only between computers which have the
    2322. 

  2322. same disk layout, or even better, are exactly the same hardware.<br>
    2323. 

  2323. Clonexp is obsoleted by mclone, which is more efficient, more bugfree and multiclient capable</p>
    2324. 

  2324. <p>&nbsp;</p><br><a name="4WP777Y6KKDSK5E2140SK6QED0J74GSY26W03JWEV0X5V" &nbsp;="" id="4WP777Y6KKDSK5E2140SK6QED0J74GSY26W03JWEV0X5V"></a><h1>3. Procedures</h1><p>Let
    2325. 

  2325. 's talk a little on what actions you should take in time of need, how
    2326. 

  2326. to best use TRK to perform troubleshooting, or how you even might work
    2327. 

  2327. with tools other than TRK.</p><br><a name="LIAT4IG4QYXT3EP1K2EVX276MK95G33SC3B7CH1S6NBZT" &nbsp;="" id="LIAT4IG4QYXT3EP1K2EVX276MK95G33SC3B7CH1S6NBZT"></a><h1>3.1 Rescueing files of dying harddiscs (mounting network =&gt; cp, ddrescue)</h1><p>
    2328. 

  2328. 

  2329. 

  2330.  	<style type="text/css">
    2331. 

  2331. 	<!--
    2332. 

  2332. 		@page { margin: 0.79in }
    2333. 

  2333. 		P { margin-bottom: 0.08in }
    2334. 

  2334. 		H2 { margin-bottom: 0.08in }
    2335. 

  2335. 	-->
    2336. 

  2336. 	</style>
    2337. 

  2337. </p><h2 lang="en-GB">Cool it!</h2>
    2338. 

  2338. <p style="margin-bottom: 0.17in;" lang="en-GB">When you have a
    2339. 

  2339. harddrive that is starting to die on you (bad clusters, physical
    2340. 

  2340. damage), it is imperative that you "upset" the disk as little as
    2341. 

  2341. possible. In most cases the cause of your dieing disk is heat: hard
    2342. 

  2342. drives can get very hot, especially when heavily used and poorly
    2343. 

  2343. cooled. A good consideration is to make sure that your disks are placed
    2344. 

  2344. freely floating so heat can get away easily. Also make sure that all of
    2345. 

  2345. your fans in your computer blow in the same direction. A standard here
    2346. 

  2346. is that fans in the front "inhale" air, while fans in the back of your
    2347. 

  2347. computer "exhale". If you are considering placing a fan inside your
    2348. 

  2348. computer directly on your disk, it is best practice to let it blow away
    2349. 

  2349. from the disk. This way you create a vacuum and no air anywhere, not
    2350. 

  2350. even in the smallest holes, can sustain in a vacuum.<br>
    2351. 

  2351. <br>
    2352. 

  2352. Another good practice is to attach your disks firmly to the computer,
    2353. 

  2353. so the iron from the chassis can guide away heat from the disk. Note:
    2354. 

  2354. Do this only by attaching the sides of the harddisks to the chassis.<br>
    2355. 

  2355. <br>
    2356. 

  2356. Now, in case it is already too late and your disk is dieing, it may be
    2357. 

  2357. that it works fine initially and then starts to make funny noises
    2358. 

  2358. afterwards: probably the bearings have worn out or the platters are
    2359. 

  2359. starting to distort and the heads are grating on the surface of the
    2360. 

  2360. disk.</p>
    2361. 

  2361. <h2 lang="en-GB">The most important thing here is to hurry up and get those files off that disk.</h2>
    2362. 

  2362. <p style="margin-bottom: 0in;"><span lang="en-GB">One suggestion I might give here might sound weird, but it worked for me already in many cases:<br>
    2363. 

  2363. </span><strong><span lang="en-GB">put the disk in the fridge</span></strong><span lang="en-GB">
    2364. 

  2364. for a while and then boot it up! Really, I'm not kidding. However,
    2365. 

  2365. don't freeze it, that will only make it worse. Put it in a normal
    2366. 

  2366. refrigerator and let it cool down in there. Also put a towel around it
    2367. 

  2367. to avoid condensation.<br>
    2368. 

  2368. Another possibility here is to connect your disk externally through a
    2369. 

  2369. disk-to-USB cable that you can buy for 20$ or less at your local
    2370. 

  2370. computer shop. (or connect the disk to an IDE cable that hangs out of
    2371. 

  2371. your PC like guts)<br>
    2372. 

  2372. Now, should you have that, go and look for that wine cooler pack you
    2373. 

  2373. got for your birthday, you know, those plastic things you put around a
    2374. 

  2374. bottle to keep it cool (or go and buy it at your local grocery store).
    2375. 

  2375. A gelpack to ease the muscles can also do the trick, but don't get it
    2376. 

  2376. out of the freezer where it's minus 18° Celsius, that is far too cold
    2377. 

  2377. and might damage your disk even more. Always wrap a towel around your
    2378. 

  2378. disk first.<br>
    2379. 

  2379. <br>
    2380. 

  2380. Now, once this is in place, you will have a better time window to start recovering files.</span></p>
    2381. 

  2381. <h2 lang="en-GB">What you can try, from good to bad to worst case scenario.</h2>
    2382. 

  2382. <p style="margin-bottom: 0in;" lang="en-GB">In the best case you will be still able to mount the filesystem on the disk. Use mountallfs to search for all local filesystems.<br>
    2383. 

  2383. <br>
    2384. 

  2384. Make sure you have a location to which you can copy your recovered
    2385. 

  2385. files. This can be another local disk or a remote network filesystem
    2386. 

  2386. such as a Windows share. How you should reach this safe haven is
    2387. 

  2387. explained earlier in this document (Getting around with commands).<br>
    2388. 

  2388. <br>
    2389. 

  2389. So let's assume a few things:<br>
    2390. 

  2390. <br>
    2391. 

  2391. -mountallfs manages to mount your filesystems on your dieing disk<br>
    2392. 

  2392. -you mount a remote network share:</p>
    2393. 

  2393. <p style="margin-bottom: 0in;" lang="en-GB">'mount -o username=administrator,password=mypassword //10.0.0.5/c$ /mnt0'<br>
    2394. 

  2394. -'cd /hda1' where hda1 is your dieing disk<br>
    2395. 

  2395. -do an 'ls' to see that you can still see files there.<br>
    2396. 

  2396. -go to the directory from which you would like to recover documents.
    2397. 

  2397. Don't start to try and copy all files, your time here is limited and it
    2398. 

  2398. is very likely that your disk is damaged in places where it has read
    2399. 

  2399. and written many times. In the case of a Windows system, this is the
    2400. 

  2400. WINDOWS system directory. Stay out of it, there are normally no
    2401. 

  2401. documents there.<br>
    2402. 

  2402. <br>
    2403. 

  2403. More likely you will do something like this:</p>
    2404. 

  2404. <p style="margin-bottom: 0in;" lang="en-GB">'cd /hda1/Documents\ and\ Settings/John\ Doe/My\ Documents'<br>
    2405. 

  2405. <br>
    2406. 

  2406. -If you don't know how many documents you are going to save, do an 'ls
    2407. 

  2407. -l'. If you see there are many subfolders, do an 'ls -lR' or 'du -h'.
    2408. 

  2408. 'ls -lR' is the equivalent of a dos 'dir /s', but it is better to do
    2409. 

  2409. 'du -h'. This will tell you how much data there is in this folder,
    2410. 

  2410. whether there are big files, small files, many files, etc...<br>
    2411. 

  2411. -Once you know this, estimate what you have to rescue. Listen to what
    2412. 

  2412. the disk has to say, if it starts making funny noises already, try to
    2413. 

  2413. save important data first.<br>
    2414. 

  2414. -Let's say all is well, start a copy (first make a remote dir to save your files to):<br>
    2415. 

  2415. 'mkdir /mnt0/recovered'<br>
    2416. 

  2416. 'cp -rvf * /mnt0/recovered' <br>
    2417. 

  2417. This command starts a copy of all files (*) to /mnt0/recovered, all
    2418. 

  2418. subdirs (r), shows the progress file by file (v) and forces overwriting
    2419. 

  2419. files on the remote location (f).<br>
    2420. 

  2420. <br>
    2421. 

  2421. If this works out: good for you.</p>
    2422. 

  2422. <h2 lang="en-GB">Otherwise...</h2>
    2423. 

  2423. <p style="margin-bottom: 0in;" lang="en-GB">If your disk starts to make funny noises and you see error messages such as</p>
    2424. 

  2424. <p style="margin-bottom: 0in;" lang="en-GB">"Disk Seek Complete Error",
    2425. 

  2425. this means we are running into bad clusters and your copy operation
    2426. 

  2426. will probably slow down dramatically.<br>
    2427. 

  2427. In this case, try to start copying files or folders more separately.
    2428. 

  2428. Skip the files first on which it runs into errors. There are other
    2429. 

  2429. means to (maybe) recover them later.<br>
    2430. 

  2430. If that works out, but you still need the other files, let's try something else.</p>
    2431. 

  2431. <p style="margin-bottom: 0in;" lang="en-GB">I recommend you let the
    2432. 

  2432. disk rest for a while by turning it off for about 20 minutes and put it
    2433. 

  2433. in the fridge wrapped in a towel.<br>
    2434. 

  2434. Once you've started it up again, you might have another go at copying
    2435. 

  2435. the bad files again, but cancel it as soon as you run into the same
    2436. 

  2436. problems again.<br>
    2437. 

  2437. <br>
    2438. 

  2438. In this case go over to using ddrescue.<br>
    2439. 

  2439. <br>
    2440. 

  2440. ddrescue takes an input file and copies it to an output file, just as a
    2441. 

  2441. normal dd would do. In this case, however, there are a few differences:
    2442. 

  2442. it tries to copy raw data from a file, but it will not try for too long
    2443. 

  2443. when it runs into bad, completely unreadable clusters; it will fill up
    2444. 

  2444. the unreadable spaces with zeroes.<br>
    2445. 

  2445. Example: 'ddrescue /hda1/Documents\ and\ Settings/John\ Doe/My\ Documents\outlook.pst /mnt0/recovered/outlook.pst'<br>
    2446. 

  2446. You can see here that the rescue is file by file. Here is a quick oneliner to rescue a complete directory.<br>
    2447. 

  2447. 'cd /hda1/Documents\ and\ Settings/John\ Doe/My\ Documents\; for i in *; do ddrescue "$i" "/mnt0/recovered/$i; done"'<br>
    2448. 

  2448. <br>
    2449. 

  2449. Another way of trying to rescue your data is to go and copy complete
    2450. 

  2450. disks or partitions. Just so you can be able to use Windows' chkdsk
    2451. 

  2451. later on the rescued filesystem, ddrescue the contents to another
    2452. 

  2452. partition on another disk. It is also possible to rescue the filesystem
    2453. 

  2453. to a file and try to mount the file as a loopback device from
    2454. 

  2454. Linux/TRK, but you won't be able to let Windows access it.<br>
    2455. 

  2455. So here goes an example (make sure nothing is mounted, neither source nor destination): 'ddrescue /dev/hda1 /dev/hdb1'<br>
    2456. 

  2456. In this case you will raw copy the complete contents of your partition
    2457. 

  2457. /dev/hda1 to /dev/hdb1. Make sure /dev/hdb1 is equal or bigger than
    2458. 

  2458. /dev/hda1<br>
    2459. 

  2459. Boot into Windows and let it run a chkdsk on it (or use the Windows install CD in recovery mode).<br>
    2460. 

  2460. If your filesystem is native Linux, such as an ext2 filesystem, you can
    2461. 

  2461. rescue it to a normal file somewhere and run e2fsck on it like that. <br>
    2462. 

  2462. Example: 'ddrescue /dev/hda1 /mnt0/rootfilesystem.img logfile-hda1'<br>
    2463. 

  2463. <br>
    2464. 

  2464. If ddrescue was unable to rescue all of your hda1 because it had to
    2465. 

  2465. skip certain sectors, try going into raw mode, which will bypass your
    2466. 

  2466. kernel disk i/o layer and read sector per sector. In raw mode it is
    2467. 

  2467. much slower, but ddrescue keeps its already completed work in a logfile
    2468. 

  2468. and only does the sectors that were skipped. <br>
    2469. 

  2469. Use it then like this: <br>
    2470. 

  2470. 'modprobe raw' <br>
    2471. 

  2471. 'raw /dev/raw/raw1 /dev/hda1' <br>
    2472. 

  2472. 'ddrescue -r3 /dev/raw/raw1 /mnt0/recovered-hda1.img logfile-hda1' <br>
    2473. 

  2473. Once you have this, restore the image to another disk that boots into a
    2474. 

  2474. normal PC into Windows and try running chkdsk against it.<br>
    2475. 

  2475. <br>
    2476. 

  2476. If it was a Linux filesystem (ext2 for example), there is no need to restore it:<br>
    2477. 

  2477. <br>
    2478. 

  2478. 'e2fsck -v -f /mnt0/ rootfilesystem.img'<br>
    2479. 

  2479. 'mount -o loop /mnt0/rootfilesystem.img /mnt1'<br>
    2480. 

  2480. &lt;= check your files...<br>
    2481. 

  2481. <br>
    2482. 

  2482. NOTE: it is not recommended to try and perform a filesystem check that
    2483. 

  2483. starts having physical I/O errors. It will probably make things even
    2484. 

  2484. more unrecoverable.</p>
    2485. 

  2485. <p></p><br><a name="QVQWIA3HK45X8M47KB6N7V5KDDAWB7HSSYD1Y78814V0G" &nbsp;="" id="QVQWIA3HK45X8M47KB6N7V5KDDAWB7HSSYD1Y78814V0G"></a><h1>3.2 Recovering deleted files or files from formatted drives (ntfsundeleteall, photorec)</h1><p>
    2486. 

  2486. 

  2487. 

  2488.  	<style type="text/css">
    2489. 

  2489. 	<!--
    2490. 

  2490. 		@page { margin: 0.79in }
    2491. 

  2491. 		P { margin-bottom: 0.08in }
    2492. 

  2492. 		H2 { margin-bottom: 0.08in }
    2493. 

  2493. 		A:link { so-language: zxx }
    2494. 

  2494. 	-->
    2495. 

  2495. 	</style>
    2496. 

  2496. </p><p style="margin-bottom: 0in;" lang="en-GB">In TRK, there are
    2497. 

  2497. several ways you can use to undelete files. What you should use depends
    2498. 

  2498. on the state of your harddisk/filesystem and the success of recovery
    2499. 

  2499. can vary between various methods.</p>
    2500. 

  2500. <h2 lang="en-GB">Ntfsundeleteall</h2>
    2501. 

  2501. <p style="margin-bottom: 0in;"><span lang="en-GB">The first method already explained earlier is </span><a href="http://trinityhome.org/Home/index.php?wpid=53&amp;front_id=12"><font color="#0000ff"><span lang="en-GB"><u>ntfsundeleteall (section 2.8)</u></span></font></a><span lang="en-GB">,
    2502. 

  2502. so I'm not going to re-explain this. What I should mention about this
    2503. 

  2503. method is that it has a high recoverability ratio on recently deleted
    2504. 

  2504. files (deleted in a normal way, not because of a crash or filesystem
    2505. 

  2505. corruption). It does however a poor job on drives that have already had
    2506. 

  2506. more write I/O over them. It is completely unusable on formatted drives.</span></p>
    2507. 

  2507. <h2 lang="en-GB">Photorec</h2>
    2508. 

  2508. <p style="margin-bottom: 0in;" lang="en-GB">In all other cases, you can
    2509. 

  2509. try the photorec utility, which tries to recover any important kind of
    2510. 

  2510. document from any filesystem. Be sure to run it by first changing to a
    2511. 

  2511. place where you can write your stuff, because it saves its recovered
    2512. 

  2512. output to a subfolder relative from where it was launched. Example:<br>
    2513. 

  2513. 'mount //10.0.0.1/share /mnt0'<br>
    2514. 

  2514. 'cd /mnt0'<br>
    2515. 

  2515. 'photorec' <br>
    2516. 

  2516. <br>
    2517. 

  2517. If you suspect that your filesystem is corrupt, I would first try to
    2518. 

  2518. run a chkdsk on it and see what it recovers. Then afterwards, see what
    2519. 

  2519. shows up and, depending on what has become visible, use the ntfs
    2520. 

  2520. capabilities of TRK or use photorec... But do not run a chkdsk if your
    2521. 

  2521. disk is physically dieing!!! Try to do as little I/O possible on that
    2522. 

  2522. disk. Running a chkdsk will probably render it even more unusable in
    2523. 

  2523. that case.</p>
    2524. 

  2524. <h2 lang="en-GB">Maybe ddrescue first</h2>
    2525. 

  2525. <p style="margin-bottom: 0in;" lang="en-GB">If photorec is unable to recover because of too many corrupt sectors, you can try ddrescue.<br>
    2526. 

  2526. This util tries to recover files and filesystems that are on locations
    2527. 

  2527. with bad sectors. If it is really unable to read the bad sectors, it
    2528. 

  2528. will pad them with zeroes. Your files will possibly be corrupted, but
    2529. 

  2529. at least you will have saved whatever there is to save. If you ddrescue
    2530. 

  2530. a complete filesystem (e.g. 'ddrescue if=/dev/hda1
    2531. 

  2531. of=/mnt0/rescued-image.img), you can afterwards mount that image as a
    2532. 

  2532. loopback filesystem ('mount -o loop /mnt0/rescued-image.img /mnt1') and
    2533. 

  2533. rescue/undelete files like that.</p>
    2534. 

  2534. <p></p><br><a name="7PFVZK0Q4R5TZMDJ351RJA8VHEBE66K4KQP91EPVWKEKX" &nbsp;="" id="7PFVZK0Q4R5TZMDJ351RJA8VHEBE66K4KQP91EPVWKEKX"></a><h1>3.3 Recovering lost partitions (testdisk, gpart, fdisk)</h1><p>
    2535. 

  2535. 

  2536. 

  2537.  	<style type="text/css">
    2538. 

  2538. 	<!--
    2539. 

  2539. 		@page { margin: 0.79in }
    2540. 

  2540. 		P { margin-bottom: 0.08in }
    2541. 

  2541. 		H2 { margin-bottom: 0.08in }
    2542. 

  2542. 		A:link { so-language: zxx }
    2543. 

  2543. 	-->
    2544. 

  2544. 	</style>
    2545. 

  2545. </p><p style="margin-bottom: 0in;" lang="en-GB">It can happen that you
    2546. 

  2546. did something stupid or something inexplicable happened and your
    2547. 

  2547. partition table has gone or is corrupted.<br>
    2548. 

  2548. <br>
    2549. 

  2549. To recover your partition tables, there are a few methods.</p>
    2550. 

  2550. <h2 lang="en-GB">Fdisk</h2>
    2551. 

  2551. <p style="margin-bottom: 0in;" lang="en-GB">I'm not referring to the Microsoft dos version of fdisk, but to the fdisk on Linux.<br>
    2552. 

  2552. Actually what you do with this is to manually redesign your partition
    2553. 

  2553. table. Of course, the risk here is that you have absolutely no idea how
    2554. 

  2554. your partition table looked before or even if you had more than one
    2555. 

  2555. partition. So this is a good strategy in the case of a disk having only
    2556. 

  2556. a single partition.<br>
    2557. 

  2557. Let us say, in this case, that the partition contains an NTFS filesystem on /dev/hda1<br>
    2558. 

  2558. Make sure nothing is mounted (run umountallfs)<br>
    2559. 

  2559. Run fdisk:<br>
    2560. 

  2560. -'fdisk /dev/hda'<br>
    2561. 

  2561. -In fdisk: press 'p' to print your actual partition table<br>
    2562. 

  2562. If your actual partition table is a bad one, erase by removing each
    2563. 

  2563. partition with 'd' and answer with the right partition number (in case
    2564. 

  2564. of logical drives, first remove everything equal and above 5).<br>
    2565. 

  2565. -'n' for new partition<br>
    2566. 

  2566. Choose primary partition, press enter for start and end sector. Fdisk automatically assigns it as a Linux native partition.<br>
    2567. 

  2567. -'t' to toggle the partition type. Ntfs is '7'<br>
    2568. 

  2568. -'a' to make it active (choose '1'), since it's probably the bootpartition<br>
    2569. 

  2569. -'w' to write your changes<br>
    2570. 

  2570. <br>
    2571. 

  2571. If this was your previous partition layout, you should now already be
    2572. 

  2572. able to mount the ntfs partition. If not, you probably won't be able to
    2573. 

  2573. boot from it either. But it should be, since this is the way to do it
    2574. 

  2574. when the problem was simply a lost partition table.</p>
    2575. 

  2575. <h2 lang="en-GB">Testdisk</h2>
    2576. 

  2576. <p style="margin-bottom: 0in;"><span lang="en-GB">This is the more
    2577. 

  2577. advanced method of recovering partitions. Run 'testdisk' at the command
    2578. 

  2578. line, the rest speaks for itself (Intel partition table =&gt; Analyze
    2579. 

  2579. =&gt; etc.). Read the testdisk documentation at</span><a href="http://www.cgsecurity.org/"><font color="#0000ff"><span lang="en-GB"><u>www.cgsecurity.org</u></span></font></a><span lang="en-GB"> <br>
    2580. 

  2580. Testdisk is also very nice to repair bootsectors. Just play with it a
    2581. 

  2581. little on a test machine to see what it all does. I have played around
    2582. 

  2582. with it myself, and although there is no guarantee that you will be
    2583. 

  2583. able to repair the bootsector every time, it still did a pretty good
    2584. 

  2584. job where others failed. <br>
    2585. 

  2585. Another thing I can recommend to you about testdisk: if it does not
    2586. 

  2586. find all of your partitions in the first minute, there is probably not
    2587. 

  2587. much left but some free disk space without a valid filesystem. It is
    2588. 

  2588. safe to cancel already if you think it found all you need.</span></p>
    2589. 

  2589. <h2 lang="en-GB">Cfdisk</h2>
    2590. 

  2590. <p style="margin-bottom: 0in;" lang="en-GB">A menu based fdisk replacement, easier to use than the standard fdisk</p>
    2591. 

  2591. <h2 lang="en-GB">Gpart</h2>
    2592. 

  2592. <p style="margin-bottom: 0in;" lang="en-GB">Guess partitions: a utility
    2593. 

  2593. that might recover your partitions too. However, it has not been
    2594. 

  2594. maintained for a few years and I have not yet tested it myself.</p>
    2595. 

  2595. <p></p><br><a name="L5ICUK4HDV6QAJA1ISR37W4DEYAHUY95TI8CT3KXNHCPR" &nbsp;="" id="L5ICUK4HDV6QAJA1ISR37W4DEYAHUY95TI8CT3KXNHCPR"></a><h1>3.4 Bootsector repair</h1><p>
    2596. 

  2596. 

  2597. 

  2598.  	<style type="text/css">
    2599. 

  2599. 	<!--
    2600. 

  2600. 		@page { margin: 0.79in }
    2601. 

  2601. 		P { margin-bottom: 0.08in }
    2602. 

  2602. 		H2 { margin-bottom: 0.08in }
    2603. 

  2603. 	-->
    2604. 

  2604. 	</style> 
    2605. 

  2605. 

  2606. </p>
    2607. 

  2607. <h2 lang="en-GB">About bootrecords</h2>
    2608. 

  2608. <p style="margin-bottom: 0in;" lang="en-GB">Several utilities can be applied to repair a bootsector and there is a lot that can be said about it.<br>
    2609. 

  2609. I will only describe a few procedures for Windows and Linux bootsectors.<br>
    2610. 

  2610. <br>
    2611. 

  2611. In a PC style (x86) environment there are 2 ways a machine can boot
    2612. 

  2612. from a harddisk: Either from the MBR (Master Boot Record) OR from the
    2613. 

  2613. bootsector on the active partition. Historically, Windows has always
    2614. 

  2614. booted from the active partition bootsector, but it also writes some
    2615. 

  2615. stuff to the MBR of the disk. I don't know all the internals of the
    2616. 

  2616. different bootprocesses, so please correct me if this documentation has
    2617. 

  2617. it wrong.<br>
    2618. 

  2618. Continuing: Linux can boot in the two different ways: Either it writes
    2619. 

  2619. its code to the MBR (e.g. /dev/hda), OR it writes it to the active
    2620. 

  2620. partition (e.g. /dev/hda1).</p>
    2621. 

  2621. <h2 lang="en-GB">Check partitioning</h2>
    2622. 

  2622. <p style="margin-bottom: 0in;" lang="en-GB">Sometimes the failure to
    2623. 

  2623. boot can simply be a partitioning problem. In that case, refer to the
    2624. 

  2624. previous section. If you rebuild your partitioning as it was before, it
    2625. 

  2625. most likely will boot again.</p>
    2626. 

  2626. <p style="margin-bottom: 0in;"><strong><span lang="en-GB">Never forget to set the correct active partition!</span></strong></p>
    2627. 

  2627. <h2 lang="en-GB">Windows boot</h2>
    2628. 

  2628. <p style="margin-bottom: 0in;"><span lang="en-GB">Let's take a quick look at procedures on how to repair Windows bootrecords.<br>
    2629. 

  2629. As I already said, Windows booting depends on both the MBR and the partition bootrecord code.<br>
    2630. 

  2630. <br>
    2631. 

  2631. -</span><strong><span lang="en-GB">ms-sys</span></strong><span lang="en-GB"><b><br>
    2632. 

  2632. </b></span><span lang="en-GB">This utility can write new MBR code to
    2633. 

  2633. your disk. Type 'ms-sys -h' to obtain some help on the different
    2634. 

  2634. parameters, but in most cases you run it first to analyse your disk.
    2635. 

  2635. 'ms-sys /dev/hda', will tell you about your MBR.<br>
    2636. 

  2636. 'ms-sys -m /dev/hda' will write an XP style MBR to your disk.<br>
    2637. 

  2637. Remember that this utility deals only with the MBR. </span></p>
    2638. 

  2638. <p style="margin-bottom: 0in;"><span lang="en-GB">For the windows bootsectors you must refer to other utils.<br>
    2639. 

  2639. <br>
    2640. 

  2640. -</span><strong><span lang="en-GB">testdisk</span></strong><span lang="en-GB"><br>
    2641. 

  2641. I've tried testdisk to write new MBR code and it worked like a charm
    2642. 

  2642. for me. What is also nice about it is that, when you go into advanced
    2643. 

  2643. mode, you can also analyse the bootsector of the partitions and repair
    2644. 

  2644. them if needed.<br>
    2645. 

  2645. <br>
    2646. 

  2646. -</span><strong><span lang="en-GB">the Windows bootcd way</span></strong><span lang="en-GB"><br>
    2647. 

  2647. It might happen that none of these methods get you back into booting
    2648. 

  2648. Windows, then there is one last method that you can try, which actually
    2649. 

  2649. has nothing to do with TRK. Boot from the Windows XP cd and go to the
    2650. 

  2650. recovery console. Make sure you know the password of the Windows system
    2651. 

  2651. on the local disk. Otherwise, reset it first with 'winpass' on TRK.<br>
    2652. 

  2652. -Now, once booted into the recovery console, it is a good thing to run checkdisk first: <br>
    2653. 

  2653. 'chkdsk c: /p'<br>
    2654. 

  2654. -Next run 'fixboot'<br>
    2655. 

  2655. -And finally run 'fixmbr'<br>
    2656. 

  2656. -'exit' to reboot<br>
    2657. 

  2657. <br>
    2658. 

  2658. -</span><strong><span lang="en-GB">if really nothing worked: FAT32</span></strong><span lang="en-GB"><br>
    2659. 

  2659. Finally, if nothing did the trick, it means something is wrong in some
    2660. 

  2660. way, I don't know, your disk geometry was laid out, filesystem were
    2661. 

  2661. created, etc, etc. Sometimes it is even a mystery to me why a Windows
    2662. 

  2662. will not boot when everything else says that it should. However, it
    2663. 

  2663. often happens after I have cloned a PC with clonexp or Partition Image.
    2664. 

  2664. Sometimes it works, sometimes it does not. </span></p>
    2665. 

  2665. <p style="margin-bottom: 0in;"><span lang="en-GB">In that case there is one last resort: </span><strong><span lang="en-GB">recreate your Windows on a fat32 partition</span></strong><span lang="en-GB">.<br>
    2666. 

  2666. For documentation on that, see the section:</span><strong><span lang="en-GB">3.5 Manually cloning a Windows installation. </span></strong><span lang="en-GB"><br>
    2667. 

  2667. <br>
    2668. 

  2668. </span><strong><span lang="en-GB">-ntfsreloc</span></strong></p>
    2669. 

  2669. <p style="margin-bottom: 0in;"><span lang="en-GB">Very handy tool if
    2670. 

  2670. your bootsector geometry does not correspond to what the bios claims it
    2671. 

  2671. to be (the bios is actually wrong). Yet Windows bootsector&nbsp; finds
    2672. 

  2672. it important it corresponds to the bios specifications. <br>
    2673. 

  2673. This utility is invoked by mclone after cloning to make sure the
    2674. 

  2674. bootsectors are exactly the same as they were (Linux adjusts them to
    2675. 

  2675. LBA).<br>
    2676. 

  2676. </span></p>
    2677. 

  2677. <p style="margin-bottom: 0in;"><span lang="en-GB">Here 's the help output of ntfsreloc 0.7:<br>
    2678. 

  2678. adjust filesystem geometry for a NTFS partition<br>
    2679. 

  2679. Usage: ntfsreloc [-h # -t #] [-s start [-b]] [-w] [-f] [-p] device<br>
    2680. 

  2680. where device points to an NTFS partition<br>
    2681. 

  2681. <br>
    2682. 

  2682. Options:<br>
    2683. 

  2683. -w:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Write new start sector to the partition.<br>
    2684. 

  2684. -h # -t #:&nbsp;&nbsp;&nbsp; Specify number of heads and number of sectors per track<br>
    2685. 

  2685. &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; If omitted, determined via ioctl.<br>
    2686. 

  2686. -s start:&nbsp;&nbsp;&nbsp; New start sector to write.<br>
    2687. 

  2687. &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; If omitted, determined via ioctl.<br>
    2688. 

  2688. -b:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Proceed even if the specified device is not a<br>
    2689. 

  2689. &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; partition (e.g. a regular file)<br>
    2690. 

  2690. -f:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Force the operation to occur even if device does not look<br>
    2691. 

  2691. &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; like a valid NTFS partition or values are equal.<br>
    2692. 

  2692. -p:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Print debug information (values read, values requested etc.)<br>
    2693. 

  2693. <br>
    2694. 

  2694. This utility displays the current starting sector as defined by the<br>
    2695. 

  2695. the filesystem.&nbsp; No change will actually be made without the -w<br>
    2696. 

  2696. option.<br>
    2697. 

  2697. <br>
    2698. 

  2698. Exit status is 2 if an error occured, 1 if a change was made or is needed<br>
    2699. 

  2699. or 0 if the filesystem already has the correct values.<br>
    2700. 

  2700. </span></p>
    2701. 

  2701. <p>&nbsp;</p><br><a name="UHPDX3JS857PC91QX5QDU7JHMFX9NFZ8NECA7MT6HQKJQ" &nbsp;="" id="UHPDX3JS857PC91QX5QDU7JHMFX9NFZ8NECA7MT6HQKJQ"></a><h1>3.5 Manually cloning a Windows installation</h1><p>
    2702. 

  2702. 

  2703. 

  2704.  	<style type="text/css">
    2705. 

  2705. 	<!--
    2706. 

  2706. 		@page { margin: 0.79in }
    2707. 

  2707. 		P { margin-bottom: 0.08in }
    2708. 

  2708. 		H2 { margin-bottom: 0.08in }
    2709. 

  2709. 		A:link { so-language: zxx }
    2710. 

  2710. 	-->
    2711. 

  2711. 	</style>
    2712. 

  2712. </p><p style="margin-bottom: 0in;" lang="en-GB">This method describes
    2713. 

  2713. how you can migrate a Windows installation to another computer and be
    2714. 

  2714. sure it will boot as long as the Windows installation itself is not
    2715. 

  2715. corrupt. Additionally, I will also describe how you could make your
    2716. 

  2716. system bootable again with only a single computer/disk available.<br>
    2717. 

  2717. <br>
    2718. 

  2718. The way we approach this type of "cloning" is very simple: we create a
    2719. 

  2719. fat32 partition, copy all data from the NTFS partition to it, let the
    2720. 

  2720. Windows bootcd repair the MBR and bootsectors and Windows boots.
    2721. 

  2721. Afterwards you can convert the filesystem back to ntfs from Windows.</p>
    2722. 

  2722. <h2 lang="en-GB">The procedure</h2>
    2723. 

  2723. <p style="margin-bottom: 0in;" lang="en-GB">Let's assume a few things
    2724. 

  2724. first: you have two harddisks attached to 1 PC one of which might be
    2725. 

  2725. dieing or chkdsk does not repair it and you can not use any cloning
    2726. 

  2726. tool because it finds errors and exits (happens with Ghost and PQ Drive
    2727. 

  2727. Image). In the case of a laptop computer, you do not have the
    2728. 

  2728. possibility to attach a second disk unless via an external USB
    2729. 

  2729. enclosure, which is not recognized under dos based utils. <br>
    2730. 

  2730. In TRK you can either mount a remote disk with two PCs running TRK of
    2731. 

  2731. which one is running in fileserver or secure shell server mode (see
    2732. 

  2732. other sections on how to do that). The possibilities are myriad. <br>
    2733. 

  2733. But our example here works with two local disks, the source disk being
    2734. 

  2734. an NTFS partition, the destination disk empty or erasable. <br>
    2735. 

  2735. Disks are respectively /dev/hda and /dev/hdb, the NTFS partition is /dev/hda1<br>
    2736. 

  2736. -Make a large enough vfat filesystem on /dev/hdb. Use qtparted to do it graphically or use…</p>
    2737. 

  2737. <p style="margin-bottom: 0in;"><span lang="en-GB">'fdisk /dev/hdb', <br>
    2738. 

  2738. -'n' to create a new primary partition<br>
    2739. 

  2739. -'1'<br>
    2740. 

  2740. -'t' to toggle, code 'c'<br>
    2741. 

  2741. -'a' set active '1'<br>
    2742. 

  2742. -'p' to print all that is about to be done to the screen<br>
    2743. 

  2743. -'w' to write and quit the partition table<br>
    2744. 

  2744. -'mkdosfs -F 32 /dev/hdb1'<br>
    2745. 

  2745. -mountallfs<br>
    2746. 

  2746. -cp -a /hda1/* /hdb1<br>
    2747. 

  2747. -Shutdown the PC, change the harddisks so your new disk becomes the primary (/dev/hda)<br>
    2748. 

  2748. -Now, reboot with the Windows CD so we can make the disk bootable (I have found it to be the best way).<br>
    2749. 

  2749. Follow the procedure described in </span><a href="http://trinityhome.org/Home/index.php?wpid=62&amp;front_id=12"><font color="#0000ff"><span lang="en-GB"><u>3.4 Bootsector repair</u></span></font></a><span lang="en-GB"> .i.e. fixboot and fixmbr.<br>
    2750. 

  2750. <br>
    2751. 

  2751. Your Windows should now start. Once booted into windows, go to a command line and run 'convert c: /fs:ntfs'<br>
    2752. 

  2752. Reboot and let your disk convert to ntfs <br>
    2753. 

  2753. <br>
    2754. 

  2754. I have noticed that the Linux 'cp' makes the windows systemdir (in most
    2755. 

  2755. cases named WINDOWS) into lowercase. It is good practice to make it
    2756. 

  2756. uppercase afterwards. Although Windows is supposed to be case
    2757. 

  2757. independent (but still case aware), I've noticed that some services
    2758. 

  2758. would not start until I uppercased it<br>
    2759. 

  2759. -'cd /hdb1'<br>
    2760. 

  2760. -'mv windows/ WINDOWS/'<br>
    2761. 

  2761. <br>
    2762. 

  2762. </span><strong><span lang="en-GB">One note here</span></strong><span lang="en-GB">:</span><strong><span lang="en-GB"> Windows XP will not boot from FAT 32 partitions larger than 32Gb</span></strong><span lang="en-GB">.
    2763. 

  2763. So do not create them bigger than this. If you have more data to copy,
    2764. 

  2764. I suggest you move your big files somewhere into a directory that you
    2765. 

  2765. then omit copying.</span></p>
    2766. 

  2766. <p></p><br><a name="JVI22F4QK5AFSUR3MHQC9ZW33AWHWA05W9XNES3PN4V5N" &nbsp;="" id="JVI22F4QK5AFSUR3MHQC9ZW33AWHWA05W9XNES3PN4V5N"></a><h1>3.6 Hardware testing</h1><p>
    2767. 

    2768. 

    2769. 

  2769.  	<style type="text/css">
    2770. 

  2770. 	<!--
    2771. 

  2771. 		@page { margin: 0.79in }
    2772. 

  2772. 		P { margin-bottom: 0.08in }
    2773. 

  2773. 		H2 { margin-bottom: 0.08in }
    2774. 

  2774. 		A:link { so-language: zxx }
    2775. 

  2775. 	-->
    2776. 

  2776. 	</style>
    2777. 

  2777. </p><p style="margin-bottom: 0in;"><span lang="en-GB">Although TRK does
    2778. 

  2778. not claim to be the best hardware test method there can be, there are
    2779. 

  2779. still a few utilities and procedures you can use to test the health of
    2780. 

  2780. your computer.<br>
    2781. 

  2781. <br>
    2782. 

  2782. A lot of information about hardware and resulting errors can already be
    2783. 

  2783. obtained by reading out the boot procedure and system information,
    2784. 

  2784. described in section </span><a href="http://trinityhome.org/Home/index.php?wpid=57&amp;front_id=12"><font color="#0000ff"><span lang="en-GB"><u>1.4 Reading information about your PC (dmesg, /proc/partitions)</u></span></font></a><span lang="en-GB">. Be sure to read that first. <br>
    2785. 

  2785. <br>
    2786. 

  2786. Here we are going to put ourselves a little more into stress testing.</span></p>
    2787. 

  2787. <h2 lang="en-GB">Harddisk testing: Bonnie</h2>
    2788. 

  2788. <p style="margin-bottom: 0in;" lang="en-GB">Bonnie is a utility that
    2789. 

  2789. stress tests the I/O of your harddisks. If you want to measure
    2790. 

  2790. performance or you just want your disk to run very hot, merely
    2791. 

  2791. mountallfs your filesystems (for ntfs volumes run 'mountallfs -g') cd
    2792. 

  2792. to a dir on the filesystem (e.g. 'cd /hda1') and execute 'bonnie'<br>
    2793. 

  2793. Here is what it could show you:<br>
    2794. 

  2794. <font face="Courier New, monospace">[root@trk]:(/hda1)# bonnie<br>
    2795. 

  2795. File './Bonnie.3078', size: 104857600<br>
    2796. 

  2796. Writing with putc()...done<br>
    2797. 

  2797. Rewriting...done<br>
    2798. 

  2798. Writing intelligently...done<br>
    2799. 

  2799. Reading with getc()...done<br>
    2800. 

  2800. Reading intelligently... done<br>
    2801. 

  2801. Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done...<br>
    2802. 

  2802. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-------Sequential
    2803. 

  2803. Output-------- ---Sequential Input-- --Random--<br>
    2804. 

  2804. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-Per
    2805. 

  2805. Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---<br>
    2806. 

  2806. Machine&nbsp;&nbsp;MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU/sec %CPU<br>
    2807. 

  2807. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1004500 16.368208.359559.59151 11.699855.1 132.01.5<br>
    2808. 

  2808. [root@trk]:(/hda1)#<br>
    2809. 

  2809. </font><br>
    2810. 

  2810. Bonnie tests a number of write operations on your disk.<br>
    2811. 

  2811. If you want it to run infinitely, just type 'run-bonnie'</p>
    2812. 

  2812. <h2 lang="en-GB">CPU testing: burnP6</h2>
    2813. 

  2813. <p style="margin-bottom: 0in;" lang="en-GB">This is a tool for
    2814. 

  2814. overclockers and anyone who likes to know that their computer does not
    2815. 

  2815. crash under heavy CPU load. It uses 100% cpu and makes bad cpus go mad
    2816. 

  2816. (probably).</p>
    2817. 

  2817. <h2 lang="en-GB">Network testing</h2>
    2818. 

  2818. <p style="margin-bottom: 0in;" lang="en-GB">Actually, a real network
    2819. 

  2819. testing utility is not included, but you can put a lot of stress on
    2820. 

  2820. your network card just by transferring large files.</p>
    2821. 

  2821. <h2 lang="en-GB">Memory testing</h2>
    2822. 

  2822. <p style="margin-bottom: 0in;" lang="en-GB">The latest version of
    2823. 

  2823. memtest+ is included. Just select it from the start menu of TRK (scroll
    2824. 

  2824. down all the way to the bottom). It tells you information about your
    2825. 

  2825. memory speed performance and tests to find any possible errors.</p>
    2826. 

  2826. <p></p><br><a name="4PL88HNFBZGXK7BHVL44UCJIPXXUD8I7MU5L2JR38YRJW" &nbsp;="" id="4PL88HNFBZGXK7BHVL44UCJIPXXUD8I7MU5L2JR38YRJW"></a><h1>3.7 Virus scanning</h1><p>See section <a href="http://trinityhome.org/Home/index.php?wpid=40&amp;front_id=12">2.1 Virusscan</a> for all the information you need on virusscanning your PC with TRK.</p><br><a name="AKDLI8WEFV4L96NMKIKSXE2ZQWDFRHLSTQ42PQ6UB16AX" &nbsp;="" id="AKDLI8WEFV4L96NMKIKSXE2ZQWDFRHLSTQ42PQ6UB16AX"></a><h1>3.8 Manual PC cleaning</h1><p>Use winclean, described in section 2.4&nbsp;Winclean</p><br><a name="ZTZJTNZS1Z028YDFIX59T2IQNHU57JDW236KHV38JU1IH" &nbsp;="" id="ZTZJTNZS1Z028YDFIX59T2IQNHU57JDW236KHV38JU1IH"></a><h1>4. Boot time options and triggers</h1><p>This
    2827. 

  2827. section gives you more info on the internals of TRK, how and why to use
    2828. 

  2828. the differen boot menu options and the triggers TRK has builtin for
    2829. 

  2829. customisation. <br>
    2830. 

  2830. For advanced users who want to automate more or need alternate ways of booting.</p><br><a name="Z034WGIXRNSS0HJZYHKU5ED0RRGXKGQA7I4TQDF6RYPH6" &nbsp;="" id="Z034WGIXRNSS0HJZYHKU5ED0RRGXKGQA7I4TQDF6RYPH6"></a><h1>4.1 Boot menu options</h1><p>The
    2831. 

  2831. boot options of the latest TRK 3.4 contain a lot of&nbsp; different
    2832. 

  2832. things, but most of the time the default startup will do.<br>
    2833. 

  2833. <br>
    2834. 

  2834. Nevertheless, here are the options explained<br>
    2835. 

  2835. &nbsp; <img alt="" src="helpdocs_files/trk34-b365-bootmenu.png" hspace="2" vspace="2"> <br>
    2836. 

  2836. <br>
    2837. 

  2837. <strong> -Default startup:</strong><br>
    2838. 

  2838. This will run TRK 3.4 with all the default options enabled. This means
    2839. 

  2839. it will run partly from CD/usb/network, keeping your CD/usb stick
    2840. 

  2840. unavailable for other things in the meantime, but will boot faster.
    2841. 

  2841. Keyboard will be default qwerty and fontsize about 3/4 of a normal font
    2842. 

  2842. in a screensize of 800x600 in VESA compatible framebuffermode. Some
    2843. 

  2843. videocards are not so VESA compliant and can therefore not benefit from
    2844. 

  2844. the graphical possibilities of TRK (like the Intel 815 chipset). They
    2845. 

  2845. will have to run in textmode, preventing them from using qtparted and
    2846. 

  2846. links (and my nice background logo).&nbsp;When booting from network,
    2847. 

  2847. you cannot unplug the network cable in this mode.<br>
    2848. 

  2848. <br>
    2849. 

  2849. &nbsp;<strong><br>
    2850. 

  2850. 1) TRK 3.4 in failsafe mode (No menu, VGA, noacpi, noapic)</strong><br>
    2851. 

  2851. In this mode, TRK&nbsp;will run with a few failsafe options by not
    2852. 

  2852. employing the APIC chip nor the ACPI. Also framebuffer mode will be
    2853. 

  2853. disabled, resulting in lower graphics and lack of background graphics
    2854. 

  2854. that "soothen your jengled nerves". Use only in case of normal startup
    2855. 

  2855. failure.</p>
    2856. 

  2856. <p><br>
    2857. 

  2857. <strong> 2) TRK 3.4 running from RAM (best &gt;= 512mb, 256mb min)</strong><br>
    2858. 

  2858. This option will run Trinity Rescue Kit completely from RAM, which
    2859. 

  2859. means it copies all of its files into memory so your CD or usb stick
    2860. 

  2860. becomes available for disconnection. In the case of PXE booted TRKs,
    2861. 

  2861. you could disconnect the network at that moment. This requires at least
    2862. 

  2862. 256Mb RAM, but recommended is 512Mb and more. Especially updated TRK
    2863. 

  2863. versions require about 250Mb more because of the included
    2864. 

  2864. antivirusccanners..<br>
    2865. 

  2865. <strong><br>
    2866. 

  2866. 3)&nbsp; TRK 3.4 - Run 'mclone' in client mode (!)</strong><br>
    2867. 

  2867. On startup, TRK&nbsp;will mclone in client (i.e. RECEIVER) mode.&nbsp;<strong>Use with caution!</strong>
    2868. 

  2868. This allows you complete local disk to be overwritten by a standard
    2869. 

  2869. mclone in SENDER mode. This option is for people wanting to perform
    2870. 

  2870. massive PC&nbsp;replication</p>
    2871. 

  2871. <p>&nbsp;<strong><br>
    2872. 

  2872. 4) TRK 3.4 in simple VGA mode (debugging of kernel output)</strong><br>
    2873. 

  2873. If you know your machine won 't boot in framebuffer mode. As I said
    2874. 

  2874. before: no links and no qtparted. This option is also useful in case
    2875. 

  2875. your TRK doesn 't initiate any output on the screen and you suspect it
    2876. 

  2876. to hang on kernel initialisation. Many times it means there 's a
    2877. 

  2877. problem with the ACPI interface of the machine. I 've noticed this
    2878. 

  2878. quite regularly on HP/Compaq machines.<br>
    2879. 

  2879. <strong><br>
    2880. 

  2880. 5) TRK 3.4 with Belgian keyboard (use menu for other)</strong><br>
    2881. 

  2881. Since me, Harakiri, is a Belgian, I&nbsp;include my own keyboard as a
    2882. 

  2882. menu option. Other keyboards can be selected from the startup
    2883. 

  2883. menu.&nbsp;Internationalisation is set to UTF-8, which should now
    2884. 

  2884. really be fixed since TRK&nbsp;3.4<br>
    2885. 

  2885. <strong><br>
    2886. 

  2886. 6) TRK 3.4 - Virusscan all drives (Clamav, non interactive)</strong><br>
    2887. 

  2887. Runs virusscan on all your drives. Stupid option actually, but this is
    2888. 

  2888. about the only thing you can do that is set-and-forget without the need
    2889. 

  2889. for any interaction. This runs virusscan without any arguments, so with
    2890. 

  2890. ClamAV. You will get no login as long as this is running. Nice option
    2891. 

  2891. for sysadmins who want to set and forget it. But you can equllay wait
    2892. 

  2892. for startup and select a few other virusscan arguments from the
    2893. 

  2893. TRK&nbsp;menu.<br>
    2894. 

  2894. <br>
    2895. 

  2895. <strong> 7) TRK 3.4 - Try more pcmcia and usb nics (when not detected)</strong><br>
    2896. 

  2896. I found that kudzu is not really good with PCMCIA cards and USB stuff
    2897. 

  2897. and I found out that the easiest way fix this was to just have support
    2898. 

  2898. for pcmcia bridges compiled in my kernel, start cardmgr and try every
    2899. 

  2899. module I find until success. Same with USB nics. This will only try
    2900. 

  2900. this for PCMCIA and USB ethernet cards/adapters.<br>
    2901. 

  2901. <br>
    2902. 

  2902. <strong> 8) TRK 3.4 - Try more SCSI drivers (when disks not detected)</strong></p>
    2903. 

  2903. <p>Same argument as with the latter: if your local disks are not found,
    2904. 

  2904. try this option to try and load every other more exotic driver
    2905. 

  2905. module.&nbsp;Be warned: this might lock up your computer.</p>
    2906. 

  2906. <p><strong> 9) TRK 3.4 with a secure shell server enabled</strong><br>
    2907. 

  2907. Run a ssh server, a very nice feature, giving you the ability to
    2908. 

  2908. remotely work on a machine that your nexter has started up for you.<br>
    2909. 

  2909. For security reasons, you will first get prompted to create/change the
    2910. 

  2910. password, after which in green will be displayed the IP-addresses your
    2911. 

  2911. TRK will listen to. However, if you're running an updated TRK&nbsp;on
    2912. 

  2912. which you have changed the root password (which by default is 'trk'),
    2913. 

  2913. you will not be prompted anymore for a password change and your
    2914. 

  2914. TRK&nbsp;will be immediately accessible over ssh.&nbsp;Your user will
    2915. 

  2915. just have to inform you the ip-address.<br>
    2916. 

  2916. <br>
    2917. 

  2917. <strong> 10)&nbsp; TRK 3.4 - Execute local scripts on harddrive of PC</strong><br>
    2918. 

  2918. Run local scripts from ./trk/trk3local.conf found on any local
    2919. 

  2919. filesystem. In this way you can make computer specific scripts and put
    2920. 

  2920. them on the harddisk. More info, see section "Triggers"<br>
    2921. 

  2921. <strong><br>
    2922. 

  2922. 11)&nbsp; TRK 3.4 as bootserver to boot other TRK clients<br>
    2923. 

  2923. </strong>This option is magic: it makes your local copy of TRK run as a
    2924. 

  2924. server to have itself booted over the network.&nbsp;Read more on
    2925. 

  2925. trkbootnet ins the section Network booting</p>
    2926. 

  2926. <p><strong> 12)&nbsp; TRK 3.4 - Fileshare all drives as guest, no security</strong><br>
    2927. 

  2927. This is the same as the previous option, but this will share all your
    2928. 

  2928. drives without any security boundary or username. Be careful with this,
    2929. 

  2929. use only in a trusted environment.<br>
    2930. 

  2930. <br>
    2931. 

  2931. <strong> 13) TRK 3.4 - Single user mode (no menu)</strong><br>
    2932. 

  2932. Starts TRK in very basic mode, sometimes useful when your PC hangs or crashes on hardware detection or some other error.<br>
    2933. 

  2933. <br>
    2934. 

  2934. <strong> </strong><strong>14) TRK 3.4 - Acpi=off, noapic&nbsp; PCI=^bios (Alternate boot 1)</strong><br>
    2935. 

  2935. Some problematic machines with lousy ACPI controls might boot with this
    2936. 

  2936. option. Happens regularly on some older Compaq machines. This will
    2937. 

  2937. disable acpi and apic and will use the bios' PCI routing table. Try
    2938. 

  2938. this when TRK hangs on early startup.<br>
    2939. 

  2939. <strong><br>
    2940. 

  2940. 15) TRK 3.4 - Acpi=off, noapic PCI=any (Alternate boot 2)</strong><br>
    2941. 

  2941. This is almost the same option as the previous one, but I let the
    2942. 

  2942. kernel decide what PCI mode should be used. I needed this mode on the
    2943. 

  2943. brand new HP DC7700 machines with Intel Duo Core because it hung on
    2944. 

  2944. kernel initialisation in the PCI part.<br>
    2945. 

  2945. <br>
    2946. 

  2946. <strong>16) TRK 3.4 - PCI=conf2 (Alternate boot 3)</strong><br>
    2947. 

  2947. Another option you can try on PC's with strange PCI&nbsp;bridgings.</p>
    2948. 

  2948. <p><br>
    2949. 

  2949. <strong> 17) <strong>TRK 3.4 - </strong><strong>Verbose startup for debugging</strong> (no menu)</strong><br>
    2950. 

  2950. I use this to see what scripts are doing or sometimes your PC might
    2951. 

  2951. hang on something but you don 't know what: try this, but don 't get
    2952. 

  2952. frightened by all the output.<br>
    2953. 

  2953. <strong><br>
    2954. 

  2954. 18) TRK 3.4 - SSH, boot- and guest fileserver, run from RAM</strong><br>
    2955. 

  2955. This is a combination of a few options This is a quite common
    2956. 

  2956. combination you would need when cloning PCs from 1 TRK to another and
    2957. 

  2957. you only have one TRK cd handy.</p>
    2958. 

  2958. <p><strong>19) TRK 3.4 - Run from RAM, run mclone as client</strong><br>
    2959. 

  2959. Another combination that explains itself</p>
    2960. 

  2960. <p><strong>20) TRK 3.4 with proxyserver support enabled</strong><br>
    2961. 

  2961. Start TRK with default options and prompts you for a proxyserver. In
    2962. 

  2962. fact, it just calls for "setproxy", which prompts you for the proxy
    2963. 

  2963. server address (hostname or ip), portnumber and optionally username and
    2964. 

  2964. password (leave blank for none)</p>
    2965. 

  2965. <p><strong>21) TRK 3.4 - All devices set to read-only</strong><br>
    2966. 

  2966. This is an option for forensic researchers who don't want to touch
    2967. 

  2967. anything on the local computer but don't have a hardware write blocking
    2968. 

  2968. device. This sets all of your disks to read-only on a kernel level.</p>
    2969. 

  2969. <p><strong> 22) Memory tester memtest+ v1.65</strong><br>
    2970. 

  2970. Almost every distribution comes with this on startup, but this way it
    2971. 

  2971. 's included in this one too. Nice to test your memory banks with, but
    2972. 

  2972. real life tests are still much more certain. Still, it might do the
    2973. 

  2973. trick for you and find you a bad module.</p><br><a name="EUGBVSAKSIDQ4SSW21D1CDTZC5RKS0DXKJY51ZFJ7J022" &nbsp;="" id="EUGBVSAKSIDQ4SSW21D1CDTZC5RKS0DXKJY51ZFJ7J022"></a><h1>4.2 Triggers</h1><p>TRK contains a number of so called "triggers", things it checks for and reacts upon when existing.<br>
    2974. 

  2974. Very handy for regular TRK users who want to customise it a little.</p><br><a name="9PAH415576DS0RB2Z5DH8AQ1XFD42G21V39QU4LS1P9S6" &nbsp;="" id="9PAH415576DS0RB2Z5DH8AQ1XFD42G21V39QU4LS1P9S6"></a><h1>4.2.1 The TRK options server: make your lan TRK aware</h1><p>TRK
    2975. 

  2975. has quite a few ways you can customise it or have custom scripts be
    2976. 

  2976. run. These scripts can run automatically because I 've built in
    2977. 

  2977. numerous placeholders for them which I call "triggers"<br>
    2978. 

  2978. <br>
    2979. 

  2979. If you are a regular user of Trinity Rescue Kit, you might find it
    2980. 

  2980. useful to have some default parameters set according to your
    2981. 

  2981. environment i.e. lan<br>
    2982. 

  2982. Ever since TRK 3.1, there 's a feature that makes your lan "TRK-aware"
    2983. 

  2983. since a system administrator can configure his lan in a way any TRK3
    2984. 

  2984. can take advantage of it in terms of proxy configurations and user
    2985. 

  2985. optional script executing, a much wanted feature from the past, but
    2986. 

  2986. hard to implement since you 're working with read-only media.<br>
    2987. 

  2987. Finally, the solution is kind of revolutionary: by activating an
    2988. 

  2988. otherwise unused parameter in you DHCP server, you can have a TRK point
    2989. 

  2989. to a server where it can find its config and scripts.<br>
    2990. 

  2990. This option is from an obsolete RFC from 1983 called 'Resource location
    2991. 

  2991. server', which was a UDP protocol that could tell you where to find
    2992. 

  2992. things like routes and smtp servers. I 'm using it now to provide TRK
    2993. 

  2993. with an IP-address where it can find a simple webserver on which
    2994. 

  2994. resides /trk/trk3options.conf<br>
    2995. 

  2995. If you 're running ISC dhcpd, add this line to /etc/dhcpd.conf:<br>
    2996. 

  2996. option resource-location-servers your-trk-webserver-ip-address;<br>
    2997. 

  2997. On a Windows server, go to Administrative tools=&gt;DHCP =&gt; go to
    2998. 

  2998. your scope =&gt; scope options =&gt; option 11 Resource Location
    2999. 

  2999. Servers.<br>
    3000. 

  3000. I wouldn 't worry too much about enabling this option to break
    3001. 

  3001. something in your network. I 've been running this for some time now at
    3002. 

  3002. my office where there are about 100 Windows PCs on dhcp. Nobody hasn 't
    3003. 

  3003. complained so far.<br>
    3004. 

  3004. <br>
    3005. 

  3005. Anyway, when a TRK 3.2 boots and finds a '<strong>resource location server</strong>' from DHCP, it will indeed look for resources from this configuration file.<br>
    3006. 

  3006. Below is an example of such config file, it more or less speaks for itself.<br>
    3007. 

  3007. The file is /var/www/html/trk/trk3options.conf on my local webserver<br>
    3008. 

  3008. <br>
    3009. 

  3009. <font face="Courier New"> TRKSECTION WGET BEGIN<br>
    3010. 

  3010. http_proxy=http://10.34.5.201:8080<br>
    3011. 

  3011. proxy_user=johndoe<br>
    3012. 

  3012. proxy_passwd=doesinc<br>
    3013. 

  3013. timeout = 10<br>
    3014. 

  3014. tries = 2<br>
    3015. 

  3015. TRKSECTION WGET END<br>
    3016. 

  3016. <br>
    3017. 

  3017. TRKSECTION LINKS BEGIN<br>
    3018. 

  3018. http_proxy 10.34.5.201:8080<br>
    3019. 

  3019. TRKSECTION LINKS END<br>
    3020. 

  3020. <br>
    3021. 

  3021. TRKSECTION CHECKUPDATESARGS BEGIN<br>
    3022. 

  3022. -proxy-server=http://10.34.5.201:8080<br>
    3023. 

  3023. -proxy-username=johndoe<br>
    3024. 

  3024. -proxy-password=doesinc<br>
    3025. 

  3025. TRKSECTION CHECKUPDATESARGS END<br>
    3026. 

  3026. <br>
    3027. 

  3027. TRKSECTION TRKSCRIPT BEGIN<br>
    3028. 

  3028. #!/bin/bash<br>
    3029. 

  3029. # <br>
    3030. 

  3030. if [ -f /etc/proxy.conf ]; then<br>
    3031. 

  3031. echo "Setting proxy params in freshclam.conf"<br>
    3032. 

  3032. if [ ! -f /etc/freshclam.conf.bak ]; then<br>
    3033. 

  3033. cp -f /etc/freshclam.conf /etc/freshclam.conf.bak<br>
    3034. 

  3034. fi<br>
    3035. 

  3035. <br>
    3036. 

  3036. if ! [ "rjohndoe" = "r" ]; then <br>
    3037. 

  3037. sed "s/# Proxy settings/\nHTTPProxyServer 10.34.5.201\nHTTPProxyPort
    3038. 

  3038. 8080\nHTTPProxyUsername johndoe\nHTTPProxyPassword doesinc/"
    3039. 

  3039. /etc/freshclam.conf &gt; /etc/fresclam.conf~<br>
    3040. 

  3040. else <br>
    3041. 

  3041. sed "s/# Proxy settings/\nHTTPProxyServer 10.34.5.201\nHTTPProxyPort 8080/" /etc/freshclam.conf &gt; /etc/fresclam.conf~<br>
    3042. 

  3042. fi;<br>
    3043. 

  3043. mv -f /etc/fresclam.conf~ /etc/freshclam.conf<br>
    3044. 

  3044. chmod 700 /etc/freshclam.conf<br>
    3045. 

  3045. if [ -f /etc/avg.conf ]; then<br>
    3046. 

  3046. echo "Setting proxy params in avg.conf"<br>
    3047. 

  3047. if [ -f /etc/avg.conf.bak ]; then<br>
    3048. 

  3048. # Take a backup of the original avg.conf if necessary<br>
    3049. 

  3049. cp -f /etc/avg.conf /etc/avg.conf.bak<br>
    3050. 

  3050. fi;<br>
    3051. 

  3051. sed -e s'/proxy = off/proxy = 10.34.5.201:8080/' /etc/avg.conf &gt; /etc/avg.conf~<br>
    3052. 

  3052. mv -f /etc/avg.conf~ /etc/avg.conf<br>
    3053. 

  3053. chmod 700 /etc/avg.conf<br>
    3054. 

  3054. sed -e s'/proxyLogin = off/proxyLogin = johndoe:doesinc/' /etc/avg.conf &gt; /etc/avg.conf~<br>
    3055. 

  3055. mv -f /etc/avg.conf~ /etc/avg.conf<br>
    3056. 

  3056. fi;<br>
    3057. 

  3057. <br>
    3058. 

  3058. if [ -f /opt/BitDefender-scanner/etc/bdscan.conf ]; then<br>
    3059. 

  3059. echo "Setting proxy params in bdscan.conf"<br>
    3060. 

  3060. if [ ! -f /opt/BitDefender-scanner/etc/bdscan.conf.bak ]; then<br>
    3061. 

  3061. cp -f&nbsp; /opt/BitDefender-scanner/etc/bdscan.conf /opt/BitDefender-scanner/etc/bdscan.conf.bak 2&gt;/dev/null<br>
    3062. 

  3062. sed "s/#HttpProxy =/\nHttpProxy = johndoe:doesinc@10.34.5.201:8080/"
    3063. 

  3063. /opt/BitDefender-scanner/etc/bdscan.conf &gt;
    3064. 

  3064. /opt/BitDefender-scanner/etc/bdscan.conf~ <br>
    3065. 

  3065. mv /opt/BitDefender-scanner/etc/bdscan.conf~ /opt/BitDefender-scanner/etc/bdscan.conf<br>
    3066. 

  3066. <br>
    3067. 

  3067. fi;<br>
    3068. 

  3068. fi;<br>
    3069. 

  3069. fi; <br>
    3070. 

  3070. TRKSECTION TRKSCRIPT END</font>      <br>
    3071. 

  3071. <br>
    3072. 

  3072. <br>
    3073. 

  3073. -TRKSCRIPT is a section where you can do basically anything you want,
    3074. 

  3074. so be very carefull with what you put in here because it will have an
    3075. 

  3075. effect on any machine you boot with TRK3 . It will basically execute as
    3076. 

  3076. a script in the same environment from the last script run by TRK,
    3077. 

  3077. /etc/init.d/trklocal<br>
    3078. 

  3078. What I put in the example here is to download an adapted version of the
    3079. 

  3079. ClamAV config file 'freshclam.conf'. Refer to the ClamAV manpages for
    3080. 

  3080. help on this file, but in here I 've put my proxy parameters too.<br>
    3081. 

  3081. I don 't need to tell you what other opportunities this opens up.<br>
    3082. 

  3082. <br>
    3083. 

  3083. If you think this file is too complicated for you to create, don 't
    3084. 

  3084. worry: just start a TRK, run 'setproxy' and this will generate the file
    3085. 

  3085. /etc/trk3options.conf<br>
    3086. 

  3086. Copy this file to your webserver and you 're all set.<br>
    3087. 

  3087. <br>
    3088. 

  3088. If you run setproxy afterwards, you will override alls settings given by your trk3optionsserver.</p><br><a name="CA4YM8MPTJ078B4RZR3V7NZDL7WUM33Q4XDGWQVE0KCZM" &nbsp;="" id="CA4YM8MPTJ078B4RZR3V7NZDL7WUM33Q4XDGWQVE0KCZM"></a><h1>4.2.2 Scripts on the computer's local harddisks</h1><p>Another
    3089. 

  3089. trigger is to have a script executed from the computer 's local
    3090. 

  3090. harddisk, allowing you to run commands specifically for the computer.
    3091. 

  3091. It is in the same format as the trk3options.conf: you have TRKSECTION
    3092. 

  3092. TRKSCRIPT (only this section) where you write your parameters. This
    3093. 

  3093. will be generated into a script called /bin/trklocscript-&lt;name of
    3094. 

  3094. the drive&gt; (f.i. /bin/trklocscript-hda1) and executed at the end of
    3095. 

  3095. the TRK startup procedure.<br>
    3096. 

  3096. The location of this script has to be in the folder .trk (dot trk) on
    3097. 

  3097. the root of the local partition. In this folder you put the file called
    3098. 

  3098. trk3local.conf.<br>
    3099. 

  3099. A sample trk3local.conf could look like this:<br>
    3100. 

  3100. <font face="Courier New"><br>
    3101. 

  3101. TRKSECTION TRKSCRIPT BEGIN<br>
    3102. 

  3102. <br>
    3103. 

  3103. #!/bin/bash<br>
    3104. 

  3104. # Script for maintenance and backup on Windows machines<br>
    3105. 

  3105. # Clean up this drive a little and do a virusscan on it<br>
    3106. 

  3106. cd /hda1/Documents\ and\ Settings<br>
    3107. 

  3107. for i in *; do rm -rf "$i"\Local\ Settings\Temp\*; rm -rf "$i"\Local\ Settings\Temporary Internet Files\*;<br>
    3108. 

  3108. done;<br>
    3109. 

  3109. virusscan -a fprot<br>
    3110. 

  3110. # Now back up the userdata of all local profiles to a network drive<br>
    3111. 

  3111. mount -o username=john,password=doe //10.0.0.5/backups /mnt0<br>
    3112. 

  3112. for i in *; do mkdir /mnt0/"$i" 2&gt;/dev/null;&nbsp; echo "Backing up
    3113. 

  3113. documents of $i"; cp -rvf "$i"/My\ Documents /mnt0/"$i"; done<br>
    3114. 

  3114. umountallfs<br>
    3115. 

  3115. <br>
    3116. 

  3116. TRKSECTION TRKSCRIPT END</font></p><br><a name="B8MI3TRVGJ2SY2XHN562I89WYSUF20I4ZWCSETDL364RY" &nbsp;="" id="B8MI3TRVGJ2SY2XHN562I89WYSUF20I4ZWCSETDL364RY"></a><h1>4.2.3 Script on the TRK medium</h1><p>If
    3117. 

  3117. you want some modifications to TRK and don 't want to fiddle directly
    3118. 

  3118. into TRK's own scripts, you can add a script to the CD/usb stick/NFS
    3119. 

  3119. share as&nbsp; /trk3/trklocscript. Unlike the previous trigger, this
    3120. 

  3120. has to be a normal bash script.<br>
    3121. 

  3121. The advantage of having scripts outside the TRK files is that you can
    3122. 

  3122. upgrade your TRK afterwards, without having to redo your work every
    3123. 

  3123. time: in case of a USB stick or NFS share, you just leave the script
    3124. 

  3124. where it is, in case of a CD, you re-add the trklocscript to the
    3125. 

  3125. multisession bootcd.<br>
    3126. 

  3126. From this script you can trigger any other script you like, f. i. adding more software to your TRK.<br>
    3127. 

  3127. Example trklocscript:<br>
    3128. 

  3128. <br>
    3129. 

  3129. <font face="Courier New">#!/bin/bash<br>
    3130. 

  3130. # Go to /tmp, which is on virtual shared memory, about half the size of your RAM<br>
    3131. 

  3131. cd /tmp<br>
    3132. 

  3132. mkdir /tmp/extrabin<br>
    3133. 

  3133. cd extrabin<br>
    3134. 

  3134. # Use the variable $TRKMOUNTDIR so you always copy/execute from the right location<br>
    3135. 

  3135. tar xzf $TRKMOUNTDIR/trk3/extrabinaries.tar.gz<br>
    3136. 

  3136. # This will set the PATH globally<br>
    3137. 

  3137. export PATH=$PATH:/tmp/extrabin</font></p><br><a name="SMFWK0I2J980KIYM9IK3CSPF1J06UQ3C29YDZ75874YID" &nbsp;="" id="SMFWK0I2J980KIYM9IK3CSPF1J06UQ3C29YDZ75874YID"></a><h1>5. Upgrade, update and change of bootmedia procedures</h1><p>TRK 3.4 is able to boot from more than CD alone. You can <strong>boot it from a USB</strong> stick, USB disk, even a fixed harddisk if you like. And the most nifty feature: <strong>boot it from network over PXE!</strong><br>
    3138. 

  3138. This part of the documentation describes how to change over to different bootmethods, upgrade and customise more of TRK.<br>
    3139. 

  3139. Putting TRK to a USb stick shouldn 't take more than 5 minutes.<br>
    3140. 

  3140. Ad hoc booting from network is even simpler: make sure your network has
    3141. 

  3141. a running dhcp server (a standard home router will do), boot TRK on
    3142. 

  3142. 1&nbsp;computer and run trkbootnet.&nbsp;Next boot the other
    3143. 

  3143. computer(s), select the network card as the bootdevice and voilà: a TRK
    3144. 

  3144. booting from another TRK</p>
    3145. 

  3145. <p><br>
    3146. 

  3146. Making TRK run from PXE takes a little longer to set up, but it 's
    3147. 

  3147. worthwhile when you have a big lan to manage. Once set up, upgrading to
    3148. 

  3148. new versions is piece of cake.</p>
    3149. 

  3149. <p>In the next sections you will find instructions on how to set up a
    3150. 

  3150. bootserver under Linux and there 's also a contributed documentation on
    3151. 

  3151. how to do it on a Windows machine.</p><br><a name="VCMNDG08JQ9JED3YXFLITGXVHLRRQIXBL9PPFEMQUMZZR" &nbsp;="" id="VCMNDG08JQ9JED3YXFLITGXVHLRRQIXBL9PPFEMQUMZZR"></a><h1>5.1 TRK on CD</h1><p>TRK
    3152. 

  3152. is in the first place known as a BOOTCD. So even if burning an isofile
    3153. 

  3153. to a CD is about the simplest thing to do, I&nbsp;will nevertheless
    3154. 

  3154. commit a piece on how you can get TRK on a cd properly.</p>
    3155. 

  3155. <p>If you really want a no brainer, try the executable, self burning
    3156. 

  3156. version of TRK from the download section. You don't need any burn
    3157. 

  3157. software to be installed on your computer, but it does require that you
    3158. 

  3158. have administrator rights.<br>
    3159. 

  3159. And how to do it: download, save locally and double click <span class="postbody">trinity-rescue-kit.3.4-build-366.exe
    3160. 

  3160. (or the latest version), answer "Yes" after you made sure you have a
    3161. 

  3161. blank CD-R in your CD writer and just sit back and relax.<br>
    3162. 

  3162. </span></p>
    3163. 

  3163. <p><span class="postbody">If you want to burn TRK&nbsp; from the isofile, there are several options and programs.<br>
    3164. 

  3164. For Windows 7 users it's easy: right click on the file and select the option to burn it to CD.<br>
    3165. 

  3165. All other users have several possibilities.</span><br>
    3166. 

  3166. 1 free and rather easy possibility is to <span class="postbody">use MagicIso, which is free for isos up to 300mb.&nbsp;At the end of this document you will find it explained in screenshots.<br>
    3167. 

  3167. Another free alternative is CD&nbsp;Burner XP&nbsp;Pro, which is a very
    3168. 

  3168. good and full fledged CD&nbsp;burning software as a whole by the way.<br>
    3169. 

  3169. </span></p><br><a name="FIRS44G0F6QRJDGPU467B1R5DHKC3QV9ZCRU6XJBUZS43" &nbsp;="" id="FIRS44G0F6QRJDGPU467B1R5DHKC3QV9ZCRU6XJBUZS43"></a><h1>5.2 How to install/upgrade your USB media to run the latest version of TRK</h1><h2>Installing from Windows</h2>
    3170. 

  3170. <p>This procedure is also valid for new TRK installations on any bootable media that has:<br>
    3171. 

  3171. -been formatted as FAT16 or FAT32 (Syslinux documentation recommends FAT16, but FAT32 is tested and works as well)<br>
    3172. 

  3172. -smaller or equal than 1Gb (=max 16k clusters). Bigger (and fat32) is
    3173. 

  3173. allowed but is subject to less compatibility. Please report me on any
    3174. 

  3174. PC that refused to boot in that way.<br>
    3175. 

  3175. -this partition made active <br>
    3176. 

  3176. -<strong>TRK_3-4</strong>
    3177. 

  3177. as a volume label (exactly like this). Another volume label (e.g.
    3178. 

  3178. RESCUEDISK is possible, but than you would have to add
    3179. 

  3179. "vollabel=RESCUEDISK" after each line that says "append initrd=..." in
    3180. 

  3180. /syslinux.cfg</p>
    3181. 

  3181. <p>But this is not guaranteed to boot from any PC that can boot USB.
    3182. 

  3182. Better is to use trk2usb from TRK itself (when booted from CD of
    3183. 

  3183. course).<br>
    3184. 

  3184. <br>
    3185. 

  3185. The rest of the installation course is like upgrading, so follow the
    3186. 

  3186. guidelins below. If you 're unable to bring it to a success using this
    3187. 

  3187. procedure, I recommend you download the ISO version of TRK, burn and
    3188. 

  3188. start from that, plug in your USB stick and run <a href="http://trinityhome.org/Home/index.php?wpid=50&amp;front_id=12">trk2usb</a></p>
    3189. 

  3189. <h2>Upgrading (and installing continued) from Windows&nbsp;</h2>
    3190. 

  3190. <p>Prerequisites: 7-zip or any archive application that can open iso files.<br>
    3191. 

  3191. -Download trinity-rescue-kit.3.4-build-366.iso (or the latest version)<br>
    3192. 

  3192. -Plug in your USB stick with the old version of TRK <br>
    3193. 

  3193. -Open the file trinity-rescue-kit.3.4-build-366.iso and extract it to
    3194. 

  3194. your USB drive root (we will call it the G: drive in this case)<br>
    3195. 

  3195. -Open a command prompt&nbsp; 'cmd'<br>
    3196. 

  3196. -Go to your USB drive: 'G:'<br>
    3197. 

  3197. -'cd trk3'<br>
    3198. 

  3198. -'syslinux G:' ('syslinux -f G:' if it refuses because windows reports it to be a fixed drive)<br>
    3199. 

  3199. -'exit'<br>
    3200. 

  3200. -eject the device and try booting from it (use the 'safely remove hardware' from the system tray)</p>
    3201. 

  3201. <h2>Installing from Linux</h2>
    3202. 

  3202. <p>I 'm not describing in detail how you should install TRK from Linux,
    3203. 

  3203. since it might require you to install special packages and perform
    3204. 

  3204. complicated operations. Someone who doesn 't fear this will have enough
    3205. 

  3205. with this short procedure<br>
    3206. 

  3206. Here goes:<br>
    3207. 

  3207. -prerequisites: mtools, syslinux 3.31<br>
    3208. 

  3208. -figure out your USB stick device (most of the time /dev/sda)<br>
    3209. 

  3209. -run 'mkdiskimage -4 /dev/sda -s 0 64 32' (from the syslinux package).
    3210. 

  3210. This will completely erase and format your drive to maximum 1Gb. If you
    3211. 

  3211. want to pass this limit, use fdisk and mkvfat -f 32 /dev/sda1, but
    3212. 

  3212. beware this can be less compatible.<br>
    3213. 

  3213. -edit /etc/mtools.conf and add the line: <font face="Courier New">drive c: file="/dev/sda4" </font><br>
    3214. 

  3214. -'mlabel c:TRK_3-4'<br>
    3215. 

  3215. -the next steps are the same as upgrading from Linux, so read below</p>
    3216. 

  3216. <h2>Upgrading from Linux</h2>
    3217. 

  3217. <p>-Download trinity-rescue-kit.3.4-build-366.iso (or the latest version)<br>
    3218. 

  3218. -Plug in your USB stick with the old version of TRK 3.4<br>
    3219. 

  3219. -Check what device id it has been assigned using 'dmesg | tail'<br>
    3220. 

  3220. -Assuming your USB stick is /dev/sda and your TRK partition /dev/sda4
    3221. 

  3221. and we use /mnt/disk1 as mountpoint: 'mount /dev/sda4 /mnt/disk1'<br>
    3222. 

  3222. -'cd /mnt/disk1'<br>
    3223. 

  3223. -assuming trinity-rescue-kit.3.4-build-366.iso is downloaded to /home/user and the mount point /mnt/disk2 exists/:<br>
    3224. 

  3224. -'mount -o loop /home/user/trinity-rescue-kit.3.4-build-366.iso /mnt/disk2'<br>
    3225. 

  3225. -'cd /mnt/disk2'<br>
    3226. 

  3226. -'cp -avf *&nbsp;/mnt/disk1/<br>
    3227. 

  3227. -'cd trk3'<br>
    3228. 

  3228. -'umount /mnt/disk1'<br>
    3229. 

  3229. -'./syslinux&nbsp; /dev/sda4'</p><br><a name="DJQBVW3TV8F9F6T9P2QZJ9WFCCVH0HU3SA5CWYWHX2G2Z" &nbsp;="" id="DJQBVW3TV8F9F6T9P2QZJ9WFCCVH0HU3SA5CWYWHX2G2Z"></a><h1>5.3 Setting up your PXE boot environment</h1><p>Ever
    3230. 

  3230. wondered what you could do with that PXE stuff from your network card
    3231. 

  3231. at boot time? Well you could run a TRK on your network.</p>
    3232. 

  3232. <h2>1. Prerequisites</h2>
    3233. 

  3233. <p>Here 's what you need:<br>
    3234. 

  3234. -the latest TRK<br>
    3235. 

  3235. -A (wired) local area network<br>
    3236. 

  3236. -Computers with PXE compliant hardware<br>
    3237. 

  3237. -A decent configurable dhcp server<br>
    3238. 

  3238. -A Linux machine or any OS that can run an NFS server (not Windows, or else a third party soft)<br>
    3239. 

  3239. -A TFTP server (these last 3 things can all run on the same server)<br>
    3240. 

  3240. <br>
    3241. 

  3241. <br>
    3242. 

  3242. Time to install and configure everything: 15 minutes (if you understand everything directly)</p>
    3243. 

  3243. <h2>2. Put the TRK files somewhere</h2>
    3244. 

  3244. <p>Download the latest tar.gz distributed TRK version (version 275 and
    3245. 

  3245. up) and unpack it somewhere on your Linux nfs/tftp server. In this case
    3246. 

  3246. we 're going to assume unpacking it to /home/trkfiles. User and group
    3247. 

  3247. ownership is ok for root, just make sure it 's world readable (is
    3248. 

  3248. normally ok, but just in case)<br>
    3249. 

  3249. commands:<br>
    3250. 

  3250. 'cd /home/trkfiles'<br>
    3251. 

  3251. 'tar xzf /tmp/trinity-rescue-kit-3.2-build-275.tar.gz'<br>
    3252. 

  3252. <br>
    3253. 

  3253. You can also copy your files from your TRK CD, usb stick or mount the
    3254. 

  3254. iso file with a loopback device and copy everything from there.<br>
    3255. 

  3255. <br>
    3256. 

  3256. <strong>Keep in mind:</strong> This is the location where all of your
    3257. 

  3257. TRK files will reside. The folder you are about to use will be the same
    3258. 

  3258. for your TFTP server as for your NFS share. Make sure they are the
    3259. 

  3259. same, not a subfolder of the other!<br>
    3260. 

  3260. <br>
    3261. 

  3261. There 's another thing you should do, that 's generating a default
    3262. 

  3262. pxelinux config file&nbsp; (/home/trkfiles/pxelinux.cfg/default). I 've
    3263. 

  3263. created a small script that does it for you, based on the normal
    3264. 

  3264. isolinux/syslinux config files. This is something you need to do
    3265. 

  3265. everytime you upgrade TRK<br>
    3266. 

  3266. -Go to /home/trkfiles/trk3 'cd /home/trkfiles/trk3'<br>
    3267. 

  3267. -'./mkpxelinux'<br>
    3268. 

  3268. The script will prompt you for an nfs path to specify. This is the
    3269. 

  3269. ip-address of your server combined with the path where TRK resides.
    3270. 

  3270. This is necessary for the secondary startup phase of TRK. If you omit
    3271. 

  3271. this, you will get weird results when booting.<br>
    3272. 

  3272. An example you could fill in is '192.168.81.5:/home/trkfiles'</p>
    3273. 

  3273. <h2>3. Setting up DHCP</h2>
    3274. 

  3274. <p>I 'm going to discuss 2 DHCP servers.<br>
    3275. 

  3275. <br>
    3276. 

  3276. <strong>First the ISC dhcp server</strong>, which is about the standard in most Linux distributions.<br>
    3277. 

  3277. Here 's what the dhcp.conf should more or less look like, depending on your site configuration.<br>
    3278. 

  3278. It 's what 's in bold that 's important.<br>
    3279. 

  3279. Note that in this situation ALL of your machines will be able to boot from PXE.<br>
    3280. 

  3280. If you omit the PXE parameters ('next-server' which is your TFTP server
    3281. 

  3281. and 'filename') from the general dhcp parameters and put them in the
    3282. 

  3282. section 'group' (what' s commented out with #), you can specify PXE
    3283. 

  3283. booting per host based on the host's mac address.<br>
    3284. 

  3284. <br>
    3285. 

  3285. <font face="Courier New"> allow booting;<br>
    3286. 

  3286. allow bootp;<br>
    3287. 

  3287. ddns-update-style none;<br>
    3288. 

  3288. subnet 192.168.81.0 netmask 255.255.255.0 {<br>
    3289. 

  3289. &nbsp;&nbsp;&nbsp; # default gateway<br>
    3290. 

  3290. &nbsp;&nbsp;&nbsp; option routers 192.168.81.2;<br>
    3291. 

  3291. &nbsp;&nbsp;&nbsp; option subnet-mask 255.255.255.0;<br>
    3292. 

  3292. <br>
    3293. 

  3293. &nbsp;&nbsp;&nbsp; option domain-name "trinityhome.local";<br>
    3294. 

  3294. &nbsp;&nbsp;&nbsp; option broadcast-address 192.168.81.255;<br>
    3295. 

  3295. <br>
    3296. 

  3296. &nbsp;&nbsp;&nbsp; # Seting up an ip address is better here<br>
    3297. 

  3297. &nbsp;&nbsp;&nbsp; option domain-name-servers 192.168.81.2;<br>
    3298. 

  3298. &nbsp;&nbsp;&nbsp; option nis-domain "trinityhome.local";<br>
    3299. 

  3299. <br>
    3300. 

  3300. &nbsp;&nbsp;&nbsp; range dynamic-bootp 192.168.81.128 192.168.81.254;<br>
    3301. 

  3301. &nbsp;&nbsp;&nbsp; default-lease-time 21600;<br>
    3302. 

  3302. &nbsp;&nbsp;&nbsp; max-lease-time 43200;<br>
    3303. 

  3303. &nbsp;&nbsp;&nbsp; # PXE directives<br>
    3304. 

  3304. &nbsp;&nbsp;&nbsp; next-server 192.168.81.5;<br>
    3305. 

  3305. &nbsp;&nbsp;&nbsp; filename "/pxelinux.0";<br>
    3306. 

  3306. <br>
    3307. 

  3307. #&nbsp;&nbsp;&nbsp; group {<br>
    3308. 

  3308. #&nbsp;&nbsp;&nbsp; host testtrk {<br>
    3309. 

  3309. #&nbsp;&nbsp;&nbsp; hardware ethernet 00:0C:29:A1:E9:E5;<br>
    3310. 

  3310. #&nbsp;&nbsp;&nbsp; fixed-address 192.168.81.253;<br>
    3311. 

  3311. #&nbsp;&nbsp;&nbsp; next-server 192.168.81.5;<br>
    3312. 

  3312. #&nbsp;&nbsp;&nbsp; filename "/pxelinux.0";<br>
    3313. 

  3313. #&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
    3314. 

  3314. #&nbsp;&nbsp;&nbsp; }</font>    <br>
    3315. 

  3315. &nbsp;<br>
    3316. 

  3316. <strong>Second DHCP server is with a Microsoft DHCP</strong>.<br>
    3317. 

  3317. -Run&nbsp; the DHCP snap-in<br>
    3318. 

  3318. -Go to&nbsp; your active scope =&gt; scope options =&gt; right click in it and select&nbsp; 'Configure options'<br>
    3319. 

  3319. -Activate option '066 Bootserver hostname' and option '067 Bootfile Name'. <br>
    3320. 

  3320. -Put for hostname the IP-address of your TFTP server alltogether. <br>
    3321. 

  3321. -For bootfilename '/pxelinux.0'</p>
    3322. 

  3322. <h2>4. Setting up a TFTP server (primary bootprocess)</h2>
    3323. 

  3323. <p>I 'm using the tftp-hpa-0.43a TFTP server, which is recommended by
    3324. 

  3324. the syslinux developer. Download it from kernel.org:
    3325. 

  3325. http://www.kernel.org/pub/software/network/tftp/<br>
    3326. 

  3326. Download, unpack, configure and make &amp;&amp; make install it.<br>
    3327. 

  3327. It 's also possible it was already in your distribution, so you don 't need to compile it.<br>
    3328. 

  3328. To have the tftp server run from the commandline as a daemon, using
    3329. 

  3329. /home/trkfiles as the dir where your TRK resides, type 'in.ftpd -l -s
    3330. 

  3330. /home/trkfiles'<br>
    3331. 

  3331. In fact, this whole procedure so far is also explained on the syslinux homepage.<strong><br>
    3332. 

  3332. </strong></p>
    3333. 

  3333. <h2>5. Setting up NFS (secondary bootprocess)</h2>
    3334. 

  3334. <p>This is for a very basic NFS setup. TRK only needs read only access
    3335. 

  3335. on NFS, so there 's no big security issue for this simple setup.<br>
    3336. 

  3336. NFS relies on 1 configuration file for its shares: /etc/exports<br>
    3337. 

  3337. Edit /etc/exports and add the next line, again assuming /home/trkfiles
    3338. 

  3338. is where your TRK resides. This is the same folder as your TFTP server
    3339. 

  3339. root!<br>
    3340. 

  3340. '/home/trkfiles&nbsp;&nbsp; *(ro,no_root_squash)'<br>
    3341. 

  3341. Restart your NFS service.<br>
    3342. 

  3342. <br>
    3343. 

  3343. <br>
    3344. 

  3344. That 's it, you 're all set. Take a machine in your lan, power it on,
    3345. 

  3345. press F12 and boot from network with TRK. It should boot even faster
    3346. 

  3346. than from CD or disk.<br>
    3347. 

  3347. When a newer version of TRK appears, all you need to do is download and
    3348. 

  3348. unpack in the same dir where it resided before and regenerate your PXE
    3349. 

  3349. config with mkpxelinux<br>
    3350. 

  3350. <br>
    3351. 

  3351. In the event you gave wrong parameters or your NFS has any problem at
    3352. 

  3352. all to get mounted, TRK will drop to a basic shell allowing you to
    3353. 

  3353. debug what's happened.</p>
    3354. 

  3354. <h2>6. Custom security and triggers</h2>
    3355. 

  3355. <p><strong>Setting it up</strong><br>
    3356. 

  3356. <br>
    3357. 

  3357. In some cases you cannot have the physical console of a machine, but it
    3358. 

  3358. can be remotely booted from network with TRK&nbsp; on PXE.<br>
    3359. 

  3359. You could run a ssh server, but TRK by default will not run one because
    3360. 

  3360. there would be no security (the default password for root is 'trk').<br>
    3361. 

  3361. In this case I 've developed a possibility to have a custom shadow file
    3362. 

  3362. (=holds encrypted versions of passwords on a Linux machine) or even
    3363. 

  3363. better the use of RSA public keys.<br>
    3364. 

  3364. Furthermore, there 's also a check for a custom, per host
    3365. 

  3365. trk3options.conf file, should you not have a trk3optionsserver
    3366. 

  3366. environment (feature since TRK 3.1).<br>
    3367. 

  3367. Also it will look for a custom trklocscript, so you can launch anything else you like.<br>
    3368. 

  3368. Here 's the way to set it up:<br>
    3369. 

  3369. -In the directory where your TRK files reside, create a directory called 'pxeconfig'<br>
    3370. 

  3370. -in the directory pxeconfig, create directories named according the mac-address of your custom hosts.<br>
    3371. 

  3371. If your hosts network card is 00:0C:29:A1:B9:E5, then create that
    3372. 

  3372. directory, but use hyphens instead of colons, just to avoid filesystems
    3373. 

  3373. that don 't accept colons. So in this case create directory
    3374. 

  3374. '00-0C-29-A1-B9-E5'<br>
    3375. 

  3375. <br>
    3376. 

  3376. <strong>Security and other triggers</strong><br>
    3377. 

  3377. <br>
    3378. 

  3378. -Per host shadow file<br>
    3379. 

  3379. In the mac-address based directory you can now put a custom shadow
    3380. 

  3380. file. This will be detected upon startup of TRK on the host with the
    3381. 

  3381. matching network interface and copied locally.<br>
    3382. 

  3382. Once copied, TRK will start a secure shell server allowing remote
    3383. 

  3383. control of the machine with the matching root password from the custom
    3384. 

  3384. shadow file.<br>
    3385. 

  3385. <br>
    3386. 

  3386. -Per host authorized_keys file<br>
    3387. 

  3387. Another way of&nbsp; having custom security for ssh is the use of rsa
    3388. 

  3388. key authentication. This is fairly easy to setup. The method of
    3389. 

  3389. public/private key authentication is standard secure shell and is
    3390. 

  3390. explained anywhere on the internet. I will therefore not explain how
    3391. 

  3391. you should generate a public/private keypair.<br>
    3392. 

  3392. What 's important is that you copy the public key of the root user to a
    3393. 

  3393. file called 'authorized_keys'. In general, one key is enough, so it 's
    3394. 

  3394. ok to copy the file id_rsa.pub or identity.pub to 'authorized_keys'
    3395. 

  3395. into our /&lt;trkpxefiles&gt;/pxeconfig/&lt;mac-addres&gt;/ directory.<br>
    3396. 

  3396. Upon startup, this file will be detected and gets precedence over a
    3397. 

  3397. custom shadow file. Once this file is copied, TRK will disable password
    3398. 

  3398. based authentication, so you can only login with your private key<br>
    3399. 

  3399. <br>
    3400. 

  3400. -Per host or general trk3options.conf and trklocscript file<br>
    3401. 

  3401. Just like with a trkoptionsserver, you can have a custom
    3402. 

  3402. trk3options.conf file in which you can specify custom proxy settings or
    3403. 

  3403. a complete script. Just put the file in
    3404. 

  3404. /&lt;trkpxefiles&gt;/pxeconfig/&lt;mac-addres&gt;/&nbsp; for per host
    3405. 

  3405. trk3options.conf or in /&lt;trkpxefiles&gt;/pxeconfig/ to have this
    3406. 

  3406. file for general use for all local TRK hosts.<br>
    3407. 

  3407. The same principle goes for trklocscript, a script that will get
    3408. 

  3408. executed when found. Place this script in /&lt;trkpxefiles&gt;/trk3/
    3409. 

  3409. and it will get executed on startup.</p><br>
    3410. 

    3411. 

  3411. </div>
    3412. 

    3413. 

    3414. 

    3415. 

    3416. 

  3416. <!-- Author: Tom Kerremans Prints: 0 Created: 5/15/2006 Updated: 8/11/2010 -->
    3417. 

    3418. 

    3419. 

    3420. 

  3420. </div><!-- close page-container -->
    3421. 

    3422. 

  3422.   </div>
    3423. 

  3423.   <br class="brclear">
    3424. 

  3424.   <div id="print-footer">
    3425. 

  3425.     <!-- Document Footer --> 
    3426. 

  3426. Trinityhome.org
    3427. 

  3427. <script language="JavaScript" type="text/javascript">
    3428. 

  3428. <!--//--><![CDATA[//><!--
    3429. 

  3429. window.print();
    3430. 

  3430. //--><!]]>
    3431. 

  3431. </script><br class="brclear">
    3432. 

  3432.     <div class="copyright">Copyright&nbsp;1996-2010&nbsp;Trinityhome&nbsp;All rights reserved.</div><div style="color: rgb(204, 204, 204); font-style: italic; padding-left: 5px;">Powered by <a style="color: rgb(204, 204, 204);" href="http://trinityhome.org/barts_cms/" title="Bart's CMS [Business Edition] Version 4.0.110 [Stable]">Bart's CMS</a></div><div style="padding: 2px;"><a href="http://trinityhome.org/barts_cms/" title="Powered by Bart's CMS [Business Edition] Version: 4.0.110 [Stable]"><img src="helpdocs_files/el_powered.gif" alt="Powered by Bart's CMS [Business Edition] Version 4.0.110 [Stable]" style="border: 0px none ;" height="23" width="103"></a></div> 
    3433. 

  3433. <!--<div style="color:#ccc;font-style:italic;padding-left:5px;">Powered by <a style="color:#ccc;" href="http://trinityhome.org/barts_cms/"  title="Bart's CMS [Business Edition] Version 4.0.110 [Stable]" >Bart's CMS</a></div> -->
    3434. 

  3434.   </div>
    3435. 

  3435. </div>
    3436. 

  3436. </body></html>
    3437.