slitaz-tools rev 666

Tiny edits
author Paul Issott <paul@slitaz.org>
date Wed Aug 17 20:16:21 2011 +0100 (2011-08-17)
parents 2b69f8b15b5a
children b88f5042481a
files doc/tazinst.en.html installer/README
line diff
     1.1 --- a/doc/tazinst.en.html	Mon Aug 15 22:33:56 2011 +0200
     1.2 +++ b/doc/tazinst.en.html	Wed Aug 17 20:16:21 2011 +0100
     1.3 @@ -29,14 +29,14 @@
     1.4  <h2>DESCRIPTION</h2>
     1.5  <p>
     1.6  	Tazinst is a lightweight SliTaz HDD installer (~ 31 KB). It installs SliTaz
     1.7 -	to a hard drive from a Live-CD, LiveUSB key, a SliTaz ISO image, or from 
     1.8 +	to a hard drive from a Live-CD, a LiveUSB key, a SliTaz ISO image, or from 
     1.9  	the web by downloading a stable, cooking or rolling version or by giving
    1.10  	the http link of another iso (eg: Development ISO).
    1.11  </p>
    1.12  <p>
    1.13  	Tazinst can format the target partition to ext2, ext3, ext4 or other formats
    1.14  	if the matching packages are installed. The home partition can be installed
    1.15 -	on another partition and if need be formatted before installation into any
    1.16 +	on another partition and if need be, formatted before installation into any
    1.17  	one of the available formats. Tazinst may upon request install the Grub
    1.18  	bootloader in the MBR of the target disk. A dual-boot with an existing 
    1.19  	Windows© partition is possible, finding the Windows© partition can either be
    1.20 @@ -63,7 +63,7 @@
    1.21  	a simple setup file with clear variables such as: 
    1.22  	<code>INST_TYPE="iso"</code>, <code>TGT_PARTITION="/dev/hda1"</code>.
    1.23  
    1.24 -	With this way, it allows developpers to create a different kind of frontend:
    1.25 +	With this way, it allows developers to create a different kind of frontend:
    1.26  	Dialog, GTK and CGI/web in TazPanel. The frontend just has to create a 
    1.27  	setup file and start the cmdline installer and report steps in a nice way 
    1.28  	(progress bar or/and messages). 
    1.29 @@ -177,8 +177,8 @@
    1.30  	<li class="level1"><div class="li">
    1.31  	<strong>TGT_WINBOOT</strong>: if this variable is entered, it indicates the
    1.32  	partition containing Windows© to implement a dual-boot. It can also be set
    1.33 -	to 'auto', in this case the	dual-boot will be on the first partition
    1.34 -	Windows© detected, 
    1.35 +	to 'auto', in this case the dual-boot will be on the first partition
    1.36 +	Windows© detects, 
    1.37  	ex: <code>TGT_WINBOOT=auto</code>
    1.38  	</div></li>
    1.39  </ol>
    1.40 @@ -216,8 +216,8 @@
    1.41  <p>
    1.42  	Performs a SliTaz install on a HDD based on data in the setup file.
    1.43  	If you decide to format your HDD, all data will be lost. If you do not 
    1.44 -	format, all data but an existing /home directory will be removed, the
    1.45 -	home directory will be kept as is.
    1.46 +	format, all data except for any existing /home directory will be removed, 
    1.47 +	the home directory will be kept as is.
    1.48  </p>
    1.49  <pre>
    1.50  tazinst install /var/lib/tazinst.conf
    1.51 @@ -278,9 +278,9 @@
    1.52  
    1.53  <h2>SYSTEM FILE</h2>
    1.54  <p>
    1.55 -	The /etc/slitaz/tazinst.conf configuration file allows you to change default
    1.56 -	settings of tazinst, if you want to use custom values for URL, directories
    1.57 -	and files, you'll have to create it and modify the following variables:
    1.58 +	The /etc/slitaz/tazinst.conf configuration file allows you to change the default
    1.59 +	settings of tazinst, if you want to use custom values for URLs, directories
    1.60 +	and files, you'll have to create one and modify the following variables:
    1.61  </p>
    1.62  
    1.63  <ul>
    1.64 @@ -330,9 +330,9 @@
    1.65  	<code>DEBUG=0</code>
    1.66  	</div></li>
    1.67  	<p>
    1.68 -		It is highly recommended to set <code>DEBUG=1</code> and join the
    1.69 -		content of the resulting Log file when sending a bug report to
    1.70 -		developpers.
    1.71 +		It is highly recommended to set <code>DEBUG=1</code> and attach the
    1.72 +		contents of the resulting Log file when sending a bug report to
    1.73 +		developers.
    1.74  	</p>
    1.75  </ol>
    1.76  </div></li>
     2.1 --- a/installer/README	Mon Aug 15 22:33:56 2011 +0200
     2.2 +++ b/installer/README	Wed Aug 17 20:16:21 2011 +0100
     2.3 @@ -2,9 +2,9 @@
     2.4  ================================================================================
     2.5  
     2.6  
     2.7 -The first SliTaz installer was using ncurses Dialog within a SHell script. It 
     2.8 -was the last SliTaz home made tool that doesn't have a desktop integrated 
     2.9 -interface, and had some crappy code since it was written at the start of the 
    2.10 +The first SliTaz installer was built using ncurses Dialog within a SHell script. 
    2.11 +It was the last SliTaz home made tool that didn't have a desktop integrated 
    2.12 +interface, and had some crappy code as it was written at the start of the 
    2.13  project.
    2.14  
    2.15  Tazinst is the new installer written entirely in SHell script and usable from 
    2.16 @@ -12,7 +12,7 @@
    2.17  is able to perform an installation automatically based on a simple config file
    2.18  with clear variables such as: INST_TYPE="iso", TGT_PARTITION="/dev/hda1".
    2.19  
    2.20 -With this way, it allows developpers to create a different kind of frontend: 
    2.21 +With this way, it allows developers to create a different kind of frontend: 
    2.22  Dialog, GTK and CGI/web in TazPanel. The frontend just has to create a config 
    2.23  file and start the cmdline installer and report steps in a nice way (progress 
    2.24  bar or/and messages).