GNU/Linux Desktop Survival Guide
by
Graham Williams
Desktop Survival
Project Home
Preface
Advocacy
History
Distributions
Installation
Basic Survival
Wajig
Audio
AbiWord
APM
Backup
Bash
Booting
Cameras
CD
Chinese
ChRoot
Clock
Commercial
Conference Management
Configuration
CRON
CVS
Databases
DIA
Directories
Disks
Documentation
DVD
Email
Eye of Gnome
Evolution
File Systems
Firewalls
Floppy Disks
Fonts
Ghemical
GIMP
Glade
Gnome
GnuCash
Gnumeric
GQView
Graphics
Groups
HTML Editors
ImageMagick
Initialisations on Booting
Java
KDE
Kernels
Keyboard
Konqueror
KVM Switch
LaTeX
Log System
Login
Magellan
Mathematics
Memory
Modems
Mounting Devices
MS/Windows
Music
MySQL
Nautilus
Networks
NFS
NT File System
OpenOffice.org
Oracle
Packages
Partitions
Passwords
PDF
Photos
PPP
Presentations
Printing
Python
R
Remote Desktops
Rsync
Samba
Scanning
Science
Security
SH File System
Sketch
Spell
SPlus
Spruce
SSH
SUDO
Subversion
Swap
Themes
USB
Video
Virtualization
Web
Word
X
XML
Sample Installations
Troubleshooting
Index
Incremental change
Some strategies for moving, bit-by-bit, to GNU/Linux include:
You servers can start running GNU/Linux with Samba installed to share their resources to end user desktops running MS/Windows
You can then replace your MS/IIS web server with apache and continue to use the dynamic scripting technologies you are used to.
By moving to the reliable and widely used sendmail you will never need to pay licensing fees for the MS/Windows Mail Server again.
Open Source print managers (including CUPS) provide seamless interoperability.
Copyright © 1995-2006
[email protected]
Contribue and access the
PDF Version