Differences between version 5 and revision by previous author of HowToDOSWintoLinuxHOWTO.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Wednesday, May 12, 2004 12:14:55 pm | by CraigMckenna | Revert |
| Older page: | version 2 | Last edited on Friday, June 7, 2002 1:06:27 am | by perry | Revert |
@@ -1,7 +1,4 @@
-
-
-
From DOS/Windows to Linux HOWTO
@@ -119,15 +116,10 @@
*10.2 C for Yourself
*10.3 X11 Programming
-
-
-
-
!!11. The Remaining 1%
-
*11.1 Running DOS/Windows Apps
*11.2 Using tar and gzip
@@ -146,12 +138,8 @@
*11.9 Converting Files
*11.10 Free Office Suites
-
-
-
-
!!12. The End, for Now
@@ -161,21 +149,10 @@
----
!!1. Introduction
-
-
-
-
-
-
!!1.1 Is Linux Right for You?
-
-
-
-
-
Let's start politically correct. Throughout this document I say ``Linux'',
but I mean ``GNU/Linux''. Please go to
http://www.gnu.org/gnu/linux-and-gnu.html to see why.
@@ -189,727 +166,285 @@
-* Windows runs Microsoft Office and lots of games; is perceived to be
-
-
+* Windows runs Microsoft Office and lots of games; is perceived to be easy to install and configure; is notoriously unstable; performs poorly; crashes are frequent.
+* Linux runs !StarOffice, scores of technical software and fewer games; can be tricky to install and configure; is rock solid; performs impeccably; crashes are extremely rare
.
-*
-
-* Linux runs !StarOffice, scores of technical software and fewer games;
-can be tricky to install and configure; is rock solid; performs
-impeccably; crashes are extremely rare.
-
-*
-
-
-
-
-
-
-
-.
-
-
-Work is underway to make Linux simpler to use, but ''don't expect to be
-proficient with it unless you read a lot of documentation and use it at
-least for a few months''. Linux won't give you instant results. In spite
-of these warnings, I'm 100% confident that if you are the right user
-type you'll find in Linux your computer Nirvana. By the way, Linux + DOS/Win
-can coexist happily on the same machine
.
+It's up to you to decide what you need. Furthermore, Linux gives you power, but it takes some time to learn how to harness it. Thus, if mostly need commercial sw, or if you don't feel like learning new commands and concepts, you had better look elsewhere. Be aware that many newcomers give up because of initial difficulties.
+Work is underway to make Linux simpler to use, but ''don't expect to be proficient with it unless you read a lot of documentation and use it at least for a few months''. Linux won't give you instant results. In spite
+of these warnings, I'm 100% confident that if you are the right user type you'll find in Linux your computer Nirvana. By the way, Linux + DOS/Win can coexist happily on the same machine.
Prerequisites for this howto: I'll assume that
-
-
-
-
* you know the basic DOS commands and concepts;
-
-*
-
-
-
-
-*
-
+* Linux, possibly with X Window System (X11 for short), is properly installed on your PC;
* your shell (the equivalent of COMMAND.COM) is bash.
-*
-
-
-
-
-
-
-
-
-
-Please also note that this work is neither a complete primer nor a
-configuration guide!
-
-
-The latest version of this document is available in several formats on
-http://www.linuxdoc.org.
-
+Unless specified, all information in this work is aimed at bad ol' DOS. There is information about Windows here and there, but bear in mind that Windows and Linux are totally different, unlike DOS that is sort of a UNIX poor relation.
+Please also note that this work is neither a complete primer nor a configuration guide!
+The latest version of this document is available in several formats on http://www.linuxdoc.org.
!!1.2 It Is. Tell Me More
+You installed Linux and the programs you needed on the PC. You gave yourself an account (if not, type adduser yourname ''now!'') and Linux is running. You've just entered your name and password, and now you are looking at the screen thinking: ``Well, now what?''
+Now, don't despair. You're almost ready to do the same things you used to do with DOS/Win, and many more. If you were running DOS/Win instead of Linux, you would be doing some of the following tasks:
-
-You installed Linux and the programs you needed on the PC. You gave yourself
-an account (if not, type adduser yourname ''now!'') and Linux
-is running. You've just entered your name and password, and now you are
-looking at the screen thinking: ``Well, now what?''
-
-
-Now, don't despair. You're almost ready to do the same things you used to do
-with DOS/Win, and many more. If you were running DOS/Win instead of Linux,
-you would be doing some of the following tasks:
-
-
-
-
-
-
-
-
-*
-
+* running programs and creating, copying, viewing, deleting, printing, renaming files;
* CD'ing, MD'ing, RD'ing, and DIR'ring your directories;
-
-*
-
* formatting floppies and copying files from/to them;
-
-*
-
* tailoring the system;
-
-*
-
* surfing the Internet;
-
-*
-
* writing .BAT files and programs in your favourite language;
-
-*
-
* the remaining 1%.
-
-*
-
-
-
-You'll be glad to know that these tasks can be accomplished under Linux in a
-fashion similar to DOS. Under DOS, the average user uses very few of the
-100+ commands available: the same, up to a point, applies to Linux.
-
-
-
+You'll be glad to know that these tasks can be accomplished under Linux in a fashion similar to DOS. Under DOS, the average user uses very few of the 100+ commands available: the same, up to a point, applies to Linux.
!Introductory Concepts
+The best way to learn something new is to get your feet wet. You are strongly encouraged to experiment and play with Linux: unless you login as ``root'', you can't damage the system that way. A few points:
+* first of all, how to quit Linux safely. If you see a text mode screen, press <CTRL-ALT-DEL>, wait for the system to reboot, then switch off the PC. If you are working under X Window System, press <CTRL-ALT-BACKSPACE> first, then <CTRL-ALT-DEL>. ''Never'' switch off or reset the PC directly: this could damage the file system;
+* unlike DOS or Windows, Linux has built-in security mechanisms. Files and directories have permissions associated to them; as a result, some cannot be accessed by the normal user; (see Section Permissions and Ownership). DOS and Windows, on the contrary, will let you wipe out the entire contents of your hard disk;
-The best way to learn something new is to get your feet wet. You are
-strongly encouraged to experiment and play with Linux: unless you login as
-can
't
damage the system that way
. A few points:
+* there's a special user called
``root'': the system administrator, with full power of life and death on the machine. If you work on your own PC
, you'll be root as well. Working as root is ''dangerous'': any mistake can seriously
damage or destroy
the system just like with DOS/Windows
. Don't work as root unless absolutely necessary;
+* much of the complexity of Linux comes from its extreme configurability: virtually every feature and every application can be tailored through one or more configuration files. Complexity is the price to pay for power;
-
-
-
-* first of all, how to quit Linux safely. If you see a text mode
-screen, press <CTRL-ALT-DEL>, wait for the system to reboot, then
-switch off the PC. If you are working under X Window System, press
-<CTRL-ALT-BACKSPACE> first, then <CTRL-ALT-DEL>. ''Never''
-switch off or reset the PC directly: this could damage the file system;
-
-*
-
-* unlike DOS or Windows, Linux has built-in security mechanisms. Files
-and directories have permissions associated to them; as a result, some
-cannot be accessed by the normal user; (see Section
-Permissions and Ownership). DOS and Windows, on the contrary, will
-let you wipe out the entire contents of your hard disk;
-
-*
-
-* there's a special user called ``root'': the system administrator,
-with full power of life and death on the machine. If you work on your own
-PC, you'll be root as well. Working as root is ''dangerous'': any
-mistake can seriously damage or destroy the system just like with
-DOS/Windows. Don't work as root unless absolutely necessary;
-
-*
-
-* much of the complexity of Linux comes from its extreme
-configurability: virtually every feature and every application can be
-tailored through one or more configuration files. Complexity is the price to
-pay for power;
-
-*
-
-
-
-
+* redirection and piping are a side DOS feature, a very inportant one and much more powerful under Linux. Simple commands can be strung together to accomplish complex tasks. I strongly suggest that you learn how to use
them.
-
-*
-
-
-
-
-
!Getting Help
-
-
-
There are many ways to get help with Linux. The most important are:
+* ''reading the documentation''---I mean it. Although the HOWTO you are reading may serve as an introduction to Linux, there are several books that you really should read: at least, Matt Welsh's [Linux Installation and Getting Started|http://www.linuxdoc.org/LDP/gs/gs.html] and [the Linux FAQ|http://www.linuxdoc.org/FAQ/Linux-FAQ/index.html]. Feel a guiltyconscience until you have read at least one of them;
+* the documentation of the packages installed on the machine is often found in subdirectories under /usr/doc/;
+* to get some help about the ``internal commands'' of the shell, type help or, better, man bash or info bash;
+* to get help about a command, type man command that invokes the manual (``man'') page of command. Alternatively, type info command that invokes, if available, the info page pertinent of command; info is a hypertext-based documentation system, perhaps not intuitive to use at first. Finally, you may try apropos command or whatis command. With all of these commands, press `q' to exit.
-
-
-* ''reading the documentation''---I mean it. Although the HOWTO
-you are reading may serve as an introduction to Linux, there are several
-books that you really should read: at least, Matt Welsh's ``Linux
-Installation and Getting Started'' (
-http://www.linuxdoc.org/LDP/gs/gs.html) and the Linux FAQ (
-http://www.linuxdoc.org/FAQ/Linux-FAQ/index.html). Feel a guilty
-conscience until you have read at least one of them;
-
-*
-
-* the documentation of the packages installed on the machine is often
-found in subdirectories under /usr/doc/;
-
-*
-
-* to get some help about the ``internal commands'' of the shell, type
-help or, better, man bash or info bash;
-
-*
-
-* to get help about a command, type man command that invokes
-the manual (``man'') page of command. Alternatively, type info
-command that invokes, if available, the info page pertinent of
-command; info is a hypertext-based documentation system, perhaps
-not intuitive to use at first. Finally, you may try apropos command
-or whatis command. With all of these commands, press `q' to exit.
-
-*
-
-
-
-
-
-
-*
-
-
-
-
-
-
+* finally, on the Internet: the right place for getting help is Usenet, like news:comp.os.linux.setup. Please don't email me for help, because I'm quite overloaded.
!!1.3 Conventions
+Throughout this work, examples will often follow the following format: <...> is a required argument, while [[...] an optional one.
-
-
-
-
-Throughout this work, examples will often follow the following format:
-<...> is a required argument, while [[...] an optional one.
Example:
+ $ tar -tf <file.tar> [[> redir_file]
+file.tar must be indicated, but redirection to redir_file is optional.
+``RMP'' means ``please Read the Man Pages for further information''. I can't stress enough how important reading the documentation is.
-
-$ tar -tf <file.tar> [[> redir_file]
-
-
-
-
-file.tar must be indicated, but redirection to redir_file
-is optional.
-
-
-``RMP'' means ``please Read the Man Pages for further information''. I can't
-stress enough how important reading the documentation is.
-
-
-
-
-
-
-
-
-
+When the prompt of a command example is #, the command can only be performed by root.
----
!!2. For the Impatient
-
-
Want to strike out? Have a look at this table:
+|DOS|Linux|Notes
+|ATTRIB (+-)attr file|chmod <mode> file|completely different
+|BACKUP|tar -Mcvf device dir/ |ditto
+|CD dirname\ |cd dirname/|almost the same syntax
+|COPY file1 file2| cp file1 file2|ditto
+|DEL file|rm file| beware - no undelete
+|DELTREE dirname| rm -R dirname/|ditto
+|DIR| ls|not exactly the same syntax
+|DIR file /S| find . -name file|completely different
+|EDIT file| vi file|I think you won't like it
+||jstar file|feels like dos' edit
+|EDLIN file|ed file|forget it
+|FORMAT|fdformat,mount, umount|quite different syntax
+|HELP command|man command,info command|same philosophy
+|MD dirname|mkdir dirname/|almost the same syntax
+|MORE < file|less file|much better
+|MOVE file1 file2|mv file1 file2|ditto
+|NUL|/dev/null|ditto
+|PRINT file|lpr file|ditto
+|PRN|/dev/lp0,/dev/lp1|ditto
+|RD dirname|rmdir dirname/|almost the same syntax
+|REN file1 file2|mv file1 file2|not for multiple files
+|RESTORE|tar -Mxpvf device|different syntax
+|TYPE file|less file|much better
+|WIN|startx|poles apart!
-
-
-
-
-
-
-DOS Linux Notes
-------------------------------------------------------------------------------
-ATTRIB (+-)attr file chmod <mode> file completely different
-BACKUP tar -Mcvf device dir/ ditto
-CD dirname\ cd dirname/ almost the same syntax
-COPY file1 file2 cp file1 file2 ditto
-DEL file rm file beware - no undelete
-DELTREE dirname rm -R dirname/ ditto
-DIR ls not exactly the same syntax
-DIR file /S find . -name file completely different
-EDIT file vi file I think you won't like it
-jstar file feels like dos' edit
-EDLIN file ed file forget it
-FORMAT fdformat,
-mount, umount quite different syntax
-HELP command man command, same philosophy
-info command
-MD dirname mkdir dirname/ almost the same syntax
-MORE < file less file much better
-MOVE file1 file2 mv file1 file2 ditto
-NUL /dev/null ditto
-PRINT file lpr file ditto
-PRN /dev/lp0,
-/dev/lp1 ditto
-RD dirname rmdir dirname/ almost the same syntax
-REN file1 file2 mv file1 file2 not for multiple files
-RESTORE tar -Mxpvf device different syntax
-TYPE file less file much better
-WIN startx poles apart!
-
-
-
-
-
-
-
-
-
-
+If you need more than a table of commands, please refer to the following sections.
----
!!3. Meet bash
+Good news: with Linux you type much less at the prompt, because the bash shell types for you whenever possible, and features cool line editing capabilities. To begin with, the arrow-up key recalls previous command lines; but there's more. Pressing <TAB> completes file and directory names, so typing
-
-
-Good news: with Linux you type much less at the prompt, because the
-bash shell types for you whenever possible, and features cool line
-editing capabilities. To begin with, the arrow-up key recalls previous
-command lines; but there's more. Pressing <TAB> completes file and
-directory names, so typing
-
-
-
-
-
-
-
-
-
-
+
$ ls /uTABloTABbTAB
is like typing
-
-
-
-
-
-
-
-
-
+
$ ls /usr/local/bin
If there were ambiguities, as typing
+ $ ls /uTABloTABiTAB
+bash stops because it doesn't know if you mean /usr/local/info or /usr/local/include. Supply more characters then press <TAB> again.
-$ ls /uTABloTABiTAB
-
-
-
-
-bash stops because it doesn't know if you mean
-/usr/local/info or /usr/local/include. Supply more
-characters then press <TAB> again.
-
-
-
-
-
-
-
+Other useful key presses are <ESC-BACKSPACE> that deletes a word to the left, while <ESC-D> deletes a word to the right; <ESC-F> moves the cursor one word to the right, <ESC-B> to the left; <CTRL-A> moves to the beginning of the line, <CTRL-E> to the end. The <ALT> key is equivalent to <ESC>.
Enough for now. Once you get used to these shortcuts, you'll find the DOS
prompt very annoying...
-
-
-
-
----
!!4. Files and Programs
-
-
-
-
-
-
-
-
-
!!4.1 Files: Preliminary Notions
+Linux has a structure of directories and files very similar to that of DOS/Win. Files have filenames that obey special rules, are stored in directories, some are executable, and among these most have command switches. Moreover, you can use wildcard characters, redirection, and piping. There are only a few minor differences:
+* under DOS, file names are in the so-called 8.3 form; e.g. NOTENOUG.TXT. Under Linux we can do better. If you installed Linux using a file system like ext2 or umsdos, you can use longer filenames (up to
+255 characters), and with more than one dot: for example, This_is.a.VERY_long.filename. Please note that I used both upper and lower case characters: in fact...
+* upper and lower case characters in file names or commands are different. Therefore, FILENAME.tar.gz and filename.tar.gz are two different files. ls is a command, LS is a mistake;
+* Windows users, beware when using long file names under Linux. If a file name contains spaces (not recommended but possible), you must enclose the file name in double quotes whenever you refer to it. For example:
-Linux has a structure of directories and files very similar to that of
-DOS/Win. Files have filenames that obey special rules, are stored in
-directories, some are executable, and among these most have command
-switches. Moreover, you can use wildcard characters, redirection, and
-piping. There are only a few minor differences:
-
-
-
-
-
-* under DOS, file names are in the so-called 8.3 form; e.g.
-NOTENOUG.TXT. Under Linux we can do better. If you installed Linux
-using a file system like ext2 or umsdos, you can use longer filenames (up to
-255 characters), and with more than one dot: for example,
-This_is.a.VERY_long.filename. Please note that I used both upper
-and lower case characters: in fact...
-
-*
-
-* upper and lower case characters in file names or commands are
-different. Therefore, FILENAME.tar.gz and filename.tar.gz
-are two different files. ls is a command, LS is a mistake;
-
-*
-
-* Windows users, beware when using long file names under Linux. If a
-file name contains spaces (not recommended but possible), you must enclose
-the file name in double quotes whenever you refer to it. For example:
-
-
-$ #
the following command makes a directory called "My old files"
-$ mkdir "My old files"
-$ ls
-My old files bin tmp
+the following command makes a directory called "My old files"
+ $ mkdir "My old files"
+ $ ls
+ My old files bin tmp
Further, some characters shouldn't be used: some of those are
-!*$&#.
-
-*
-
-* there are no compulsory extensions like .COM and .EXE for programs,
-or .BAT for batch files. Executable files are marked by an asterisk
-`*' at the end of their name when you issue the ls -F
-command. For example:
-
-
-$ ls -F
-I_am_a_dir/ cindy.jpg cjpg* letter_to_Joe my_1st_script* old~
-
-
-The files cjpg* and my_1st_script* are executables, that
-is ``programs''. Under DOS, backup files end in .BAK, while under Linux they
-end with a tilde `~'. Further, a file whose name starts with
-a dot is considered as hidden. Example: the file
-.I.am.a.hidden.file won't show up after the ls command;
-
-*
-
-* DOS program switches are obtained with /switch, Linux
-switches with -switch or --switch. Example: dir
-/s<tt> becomes ls -R. Note that many DOS programs, like
-PKZIP or ARJ, use UNIX-style switches.
-
-*
-
-
-
-You can now jump to Section
-Translating Commands from DOS to Linux, but if I were you I'd read on.
+
!*$&#
+* there are no compulsory extensions like .COM and .EXE for programs, or .BAT for batch files. Executable files are marked by an asterisk `*' at the end of their name when you issue the ls -F command. For example:
+ $ ls -F
+ I_am_a_dir/ cindy.jpg cjpg* letter_to_Joe my_1st_script* old~
+The files cjpg* and my_1st_script* are executables, that is ``programs''. Under DOS, backup files end in .BAK, while under Linux they end with a tilde `~'. Further, a file whose name starts with a dot is considered as hidden. Example: the file .I.am.a.hidden.file won't show up after the ls command;
+* DOS program switches are obtained with /switch, Linux switches with -switch or --switch. Example: dir /s<tt> becomes ls -R. Note that many DOS programs, like PKZIP or ARJ, use UNIX-style switches.
+You can now jump to Section Translating Commands from DOS to Linux, but if I were you I'd read on.
!!4.2 Symbolic Links
-
-
-
-
-
-
-
-
-
-
-
+UNIX has a type of file that doesn't exist under DOS: the symbolic link. This can be thought of as a pointer to a file or to a directory, and can be used instead of the file or directory it points to; it's similar to Windows shortcuts. Examples of symbolic links are /usr/X11, which points to /usr/X11R6; /dev/modem, which points to either /dev/ttyS0 or /dev/ttyS1.
To make a symbolic link:
-
-
-
-
-
-
-
-
+
$ ln -s <file_or_dir> <linkname>
Example:
+ $ ln -s /usr/doc/g77/DOC g77manual.txt
-
-
-
-$ ln -s /usr/doc/g77/DOC g77manual.txt
-
-
-
-
-
-
-
-
-
-
-
-$ ls -F
-g77manual.txt@
-$ ls -l
-(several things...) g77manual.txt -> /usr/doc/g77/DOC
-
-
+Now you can refer to g77manual.txt instead of /usr/doc/g77/DOC. Links appear like this in directory listings:
+ ls -F
+ g77manual.txt@
+ $ ls -l
+ (several things...) g77manual.txt -> /usr/doc/g77/DOC
!! 4.3 Permissions and Ownership
+DOS files and directories have the following attributes: A (archive), H (hidden), R (read-only), and S (system). Only H and R make sense under Linux: hidden files start with a dot, and for the R attribute, read on.
+Under UNIX a file has ``permissions'' and an owner, who in turn belongs to a ``group''. Look at this example:
+ $ ls -l /bin/ls
+ -rwxr-xr-x 1 root bin 27281 Aug 15 1995 /bin/ls*
+The first field contains the permissions of the file /bin/ls, which belongs to root, group bin. Leaving the remaining information aside, remember that -rwxr-xr-x means, from left to right:
-DOS files and directories have
the following attributes: A
(archive)
, H
-(hidden)
, R
(read-only)
, and S (system). Only H and R make sense under
-Linux: hidden files start with a dot
, and
for the R attribute
, read on
.
+- is
the file type
(- = ordinary file
, d = directory
, l = link, etc); rwx are the permissions for the file owner
(read, write
, execute); r-x are the permissions
for the group of the file owner (read
, execute); (I won't cover the concept of group, you can survive without it as long as you're a beginner ;-) r-x are the permissions for all other users (
read, execute)
.
+The directory /bin has permissions, too: see Section Directories Permissions for further details. This is why you can't delete the file /bin/ls unless you are root: you don't have the permission to do so. To change a file's permissions, the command is:
-Under UNIX a file has ``permissions'' and an owner, who in turn belongs to a
-``group''. Look at this example:
-
-
-
-
-
-$ ls -l /bin/ls
--rwxr-xr-x
1 root bin 27281 Aug 15 1995 /bin/ls*
-
-
-
-
-The first field contains the permissions of the file /bin/ls, which
-belongs to root, group bin. Leaving the remaining information aside,
-remember that -rwxr-xr-x means, from left to right:
-
-
-- is the file type (- = ordinary file, d =
-directory, l = link, etc); rwx are the permissions for the
-file owner (read, write, execute); r-x are the permissions for the
-group of the file owner (read, execute); (I won't cover the concept of
-group, you can survive without it as long as you're a beginner ;-)
-r-x are the permissions for all other users (read, execute).
-
-
-The directory /bin has permissions, too: see Section
-Directories Permissions for further
-details. This is why you can't delete the file /bin/ls unless you
-are root: you don't have the permission to do so. To change a file's
-permissions, the command is:
-
-
-
-
-
-
-
-
-
-
-where who is u (user, that is owner), g (group),
-o (other), X is either + or -, perm is r
-(read), w (write), or x (execute). Common examples of
-chmod use are the following:
-
-
-
-
-
-$ chmod +x file
-
+ $ chmod <whoXperm> <file>
+where who is u (user, that is owner), g (group), o (other), X is either + or -, perm is r (read), w (write), or x (execute). Common examples of chmod use are the following:
+ $ chmod +x file
this sets the execute permission for the file.
-
-
-
-
-
-
-
-
+
$ chmod go-rw file
this removes read and write permission for everyone but the owner.
-
-
-
-
-
-
-
-
+
$ chmod ugo+rwx file
this gives everyone read, write, and execute permission.
+ # chmod +s file
+this makes a so-called ``setuid'' or ``suid'' file---a file that everyone can execute with its owner's privileges. Typically, you'll come across root suid files; these are often important system files, like the X server.
-
-
-# chmod +s file
-
-
-
-
-this makes a so-called ``setuid'' or ``suid'' file---a file that everyone
-can execute with its owner's privileges. Typically, you'll come across root
-suid files; these are often important system files, like the X server.
-
-
-
-
-
-
-
-
-
-
-
-
-
+A shorter way to refer to permissions is with digits: rwxr-xr-x can be expressed as 755 (every letter corresponds to a bit: --- is , --x is 1, -w- is 2, -wx is 3...). It looks difficult, but with a bit of practice you'll understand the concept. root, being the superuser, can change everyone's file permissions. RMP.
!! 4.4 Files: Translating Commands
-
-
-
-
-
On the left, the DOS commands; on the right, their Linux counterpart.
-
-
-
-
chmod
-COPY:
cp
-DEL:
rm
-MOVE:
mv
-REN:
mv
-TYPE:
more, less, cat
-
-
+|
ATTRIB:|
chmod
+|
COPY:|
cp
+|
DEL:|
rm
+|
MOVE:|
mv
+|
REN:|
mv
+|
TYPE:|
more, less, cat
Redirection and plumbing operators: < > >> |
Wildcards: * ?
-
nul: /dev/null
prn, lpt1: /dev/lp0 or /dev/lp1; lpr
-
-
!Examples
-
-
-
-
-
-
DOS Linux
---------------------------------------------------------------------
@@ -2758,14 +2293,15 @@
anyway: it offers a lot of functionality not found in Microsoft Office. It
can also read and write Word and Excel files, although the conversion isn't
always perfect.
+!OpenOffice.org (
+
+http://www.openoffice.org
Another good package is Corel !WordPerfect, a free edition of which is
available for download. Need I say more? Go fetch it:
http://www.corel.com.
-
-
@@ -2793,9 +2329,21 @@
-!!12.1 Copyright
+!!12.1 See Also
+
+
+
+ *[HowToBootUSBFromDOS].
+
+
+
+
+
+
+
+!!12.2
Copyright
@@ -2817,9 +2365,9 @@
-!!12.2
Disclaimer
+!!12.3
Disclaimer
