tazinst diff README @ rev 2

Use UUIDs, boot delay on mobile disks, GPT support, boot flag, new slitaz-installer and web frontends
author Dominique Corbex <domcox@slitaz.org>
date Thu Feb 14 13:12:12 2013 +0100 (2013-02-14)
parents ced519734730
children 14c1b0fdb94a
line diff
     1.1 --- a/README	Thu Feb 14 12:48:04 2013 +0100
     1.2 +++ b/README	Thu Feb 14 13:12:12 2013 +0100
     1.3 @@ -1,29 +1,21 @@
     1.4  SliTaz Installer
     1.5  ================================================================================
     1.6  
     1.7 -
     1.8 -The first SliTaz installer was built using ncurses Dialog within a SHell script. 
     1.9 -It was the last SliTaz home made tool that didn't have a desktop integrated 
    1.10 -interface and had some crappy code as it was written at the start of the 
    1.11 -project.
    1.12 -
    1.13 -Tazinst is the new installer written entirely in SHell script and usable from 
    1.14 -the cmdline without dialog or any other gui-like interface! This new installer
    1.15 +Tazinst is the SliTaz installer written entirely in SHell script and usable from 
    1.16 +the cmdline without dialog or any other gui-like interface! This installer
    1.17  is able to perform an installation automatically based on a simple config file
    1.18  with clear variables such as: INST_TYPE="iso", TGT_PARTITION="/dev/hda1".
    1.19  
    1.20  With this way, it allows developers to create a different kind of frontend: 
    1.21 -Dialog, GTK and CGI/web in TazPanel. The frontend just has to create a config 
    1.22 -file and start the cmdline installer and report steps in a nice way (progress 
    1.23 -bar or/and messages).
    1.24 +Dialog, CGI/web. Two frontends are included: slitaz-installer, a ncurses frontend,
    1.25 +and a CGI/web frontend.
    1.26  
    1.27  
    1.28  i18n
    1.29  ----
    1.30  Tazinst has been coded from the beginning with gettext support. Please
    1.31  forget 'echo' and use gettext, but remember that gettext "" is equivalent
    1.32 -to echo -n. All scripts use the same TEXTDOMAIN and the same pot files, all
    1.33 -translations go in the po/ folder.
    1.34 +to echo -n. All translations go in the po/ folder.
    1.35   
    1.36  To start a new translation please use msginit from the pot file directory. 
    1.37  Example for French/France locale (fr_FR):