7. Conventions

The file contents and line commands and install screen-shots are always in typewriter font, like this:

     #!/bin/bash
     #############################################
     #### This is the great file /bin/Windows ####
     #############################################
     
     while [ "1" ]; do
             echo "I do my best because I'm the best"
             echo "Very soon, next Y2Kill (the 01/01/0000)"
             echo "A new marvelous 64 bit release !"
             echo "Please wait a little more"
             sleep 18446744073709551615 # 2^64-1
     done
    

or this:

     $ killall Windows
     Terminated
    

The file content lines should never begin with white space. You'll have to remove them, if any. Sorry, I'm fed up with C-a M-AltGr-\ (remember, I'm a French azerty writer). Tab-emacs reflex is untameable (coders who use Emacs always press the tabular key like a twitch).

Command input lines begin with a dollar $ (the prompt), you don't have to type the dollar, just type the rest of the line; other lines are the command output, you don't have to type them either.

Because all the configuration commands are important, you'll need to use a system administrator shell, like root, on the source and the target computers.

     $ su
     Password: blabla
     # 
    

The prompt will be shown as "$" in the remainder of this documentation "$", even if it should be "#". This is because "#" often means comment, so it is ambiguous. I don't like ambiguity in computer science.

mirror server hosted at Truenetwork, Russian Federation.