00-Basic Linux Training

December 5, 2009 – 10:12 pm

Please note… This information no longer exists at the referenced locations.  This is only a copy of what was available in 2003.

Basic Linux Training™

This reference is from http://www.linux.com/archive/feature/22104

Henry White and Anita Lewis run this low-key mailing list and Web site that is the best free program on the ‘Net, dedicated to the Linux newbie who is willing to do some studying to learn the basics. They’re so low-key they didn’t want us to give them too much publicity because “idle-curiosity seekers” take up too much bandwidth, according to Henry White, and he pays for that out of his own pocket. So, no visiting unless you’re a serious newbie who’s ready to learn!

They’re tolerant of all questions that come up on the “BLT” list, and don’t allow flaming or “RTFM” comments. But don’t expect to get your hand held too much — after all, this is Linux, and you have to be ready to read up.

Potential students should be prepared to wait; the class size is limited and there’s usually a backlog of registrants, says White. Once you’re in, you’ll get two or three lessons at a time to work through on your own. The mailing list is for lesson-related questions or other difficulties.

From the site: “Basic Linux Training is a brief, introductory level course written specifically for those coming from a DOS/Windows background, without any knowledge of Unix or programming. (Those coming from Apple/Mac are welcome and should get a lot out of this course despite the orientation. Just be aware that Mac users have always been rare on the mailing list so you’ll almost certainly have to supplement this course with other Mac users who have Linux installed.) The course is designed to be used with virtually any introductory Linux textbook, and is vendor and distribution neutral.”

Read this entire page CAREFULLY!
Everything you need to know about the course is on this page or one of the links.

This is NOT a prep course for Linux certification!

Table of Contents

  1. Course description
  2. Who will benefit from this course?
  3. Digital classroom
  4. Hardware requirements
  5. Computer experience
  6. Time requirement
  7. Registration

Course description

Basic Linux Training™ is a brief, introductory level course written specifically for those coming from a DOS/Windows background, without any knowledge of Unix or programming. (Those coming from Apple/Mac are welcome and should get a lot out of this course despite the orientation. Just be aware that Mac users have always been rare on the mailing list so you’ll almost certainly have to supplement this course with other Mac users who have Linux installed.) The course is designed to be used with virtually any introductory Linux textbook, and is vendor and distribution neutral.

The lessons cover the initial installation and configuration of GNU/Linux on your PC. They begin with a brief overview of the history and origins of UNIX, GNU, and Linux, describing the ‘philosophy’ underlying the system design. The lessons also address the choice of a distribution, preparing your hard disk, and the actual installation of the base system. Once the basic system is properly installed and configured, we continue with lessons on making your ISP connection, adding additional programs, setting up the graphical user interface, rebuilding the kernel, updating software packages, understanding the filesystem, the basic commands and programs, and the essentials of administering your new system. There are also lessons to give you a more in-depth introduction to shells and shell programming, booting and boot managers, XFree86 and X applications, networking, text editors, programming tools, bug tracking, software testing, security, customizing your system the way you want it, and tips for performance tuning.

Who will benefit from the course?

Anyone looking for systematic and detailed basic information about GNU/Linux should benefit from this course, whether you already have it installed, or have not yet decided on a distribution.

Learning a new operating system will take some time and effort on your part. There is a lot of new information you need to know before any of it begins to make any sense because it is essentially a whole new way of doing things. This course and the mailing list will guide you through that as quickly and painlessly as possible.

A few words of caution:

  1. If you’re having an anxiety attack and are in a rush to get through the installation as quickly as possible, this is definitely NOT the place for you to be. Go to the printed manual or homepage for whichever distribution you intend to use for detailed instructions specifically for the distribution you intend to install. (S.u.S.E. is the only major distribution does not have an online HTML version of the manual; it is available, however, in PDF, Postscript, etc.). You can easily be finished with the initial install, up and running, and connected to your ISP within two to three of hours (once your hard disk has been prepared for installation, which may take another 2 to 4 hours) – provided you take a few minutes to read the instructions first. Then you can relax, and take this course to round out your education, and together we can level the notoriously steep learning curve to something you can manage.
  2. On the other hand, ‘this definitely is not Windows anymore’ so if you try to bluff your way through it, as you’ve been getting away with in Windows, chances are you’ll not only get hopelessly lost and frustrated, there is also a strong probability you’ll completely ‘hose’ your system. You’re going to have to start thinking and acting in a completely different way.
  3. If you’re looking for a ‘Windows that works’ or instant solutions without effort, you might as well bail out now. Most of the alleged ‘ease of installation’ is a trade off – a la Microsoft – that someone else knows more about your needs and preferences than you do. However, the default configuration only gets you in the ballpark – after that it’s entirely up to you how much customizing you do. Most distributions make this extremely easy with specialized tools and utilities. (What is emphasized throughout the course is using a plain text editor to manually edit the configuration files.)
  4. GNU/Linux is not the right choice for everybody! Most of the applications you are familiar with in DOS/Windows are not available, and running them through one of the Windows emulators may not be entirely satisfactory. The GNU/Linux community has no control over this – it’s purely economics on the part of the software manufacturers, and often a matter of copyrights and software patents they don’t own. Once there is ‘critical mass’ they will have no choice but to port their most popular applications or risk losing their user base to the competition. Meanwhile, there are plenty of GNU/Linux-native alternatives that are available now.
  5. Linux is not for PC-weenies and lamers! If you’re “too busy” to be bothered with the fundamentals – like reading the available documentation – you might as well forget about Linux right now; the rest of us are probably too busy to do all the work for you ;-) You can fake your way through other operating systems, not reading the documentation and just randomly typing in commands or clicking on the pretty icons until you find something that works, but not for very long. With administering any Unix variant, reading is NOT optional – it’s absolutely, positively required. Similarly, there is a certain amount of ‘trial and error’ involved – particularly in customizing the ‘look and feel’ you want.

Most Linux users are dual-booting with Windows or NT . (It’s just a guess, but much better than 95% are dual-booting, and less than 5% of users are 100% pure GNU/Linux.)

Digital classroom

Getting Linux installed is not going to do much for you unless you know how to use it, and that’s what this course is really about.

This course is not going to be easy – you’re going to have to make a commitment to get much out of it. You will have to put some effort into learning about many things that are not required with pre-installed operating systems – for example, exactly what hardware is installed on your system, exactly where your partitions start and end, your ports and IRQs. If all goes well during the installation, you’ll probably have to do very little tweaking here and there to get Linux and XFree86 up and running. None of this is particularly difficult it you approach it systematically and take time to understand what is happening BEFORE you just barge in and expect everything to work perfectly. This is an extremely powerful operating system, and virtually everything can be customized to suit your needs or preferences. Understandably, there are a lot of new things that you have to know and be able to do; new terms and concepts, etc.

I try to keep the length of the lessons to a minimum, and provide links to relevant, quality information. Almost all of these links do not rely on graphics, so the course is very useful for the blind and visually impaired, those with a low-speed connection, paying by the kilobyte, or using a text-based browser. There is, however, considerable duplication among many of the links – I suggest you look at all of them though.

The restricted mailing list set up especially for this course has been moderately active; only one or two messages on a very slow day, but often averaging 25 to 40 messages a day, occasionally much more. For the most part, students helping other students has many advantages – you’re reading the same lessons and documentation, and trying to get the same tasks done.

  1. One thing that is not tolerated on this mailing list is a hostile attitude! There are no religious wars, flame baiting, trolling, or ambushes. You won’t be ridiculed, called names, or get the usual curt ‘RTFM!’ ;-) Of course, you will have to read – a LOT - and that is not optional, it’s required! The difference is you will be pointed to a specific file or URL, and probably a brief summary so you can get the most out of the readings. So don’t be embarrassed or shy about asking any question!
  2. Another thing you will appreciate here is the lack of spam! There’s a nice spam filter on the server; only members can post to the list, and only members can read the archives.
  3. Both the mailing list archives and the lessons (including the IRC logs) are restricted access; attachments are automatically deleted before they get into the archives.
  4. We lost the archives (8000+ messages!) when we moved the mailing list. Many of these messages will be uploaded later in a separate directory. We’re working on recovering all or most of these from members’ folders.

Roughly half the subscribers are taking the course, and not all of them are entirely new to GNU/Linux and other Unix variants. (Remember, even a newbie only needs to be a few hours ahead of where you are at any given time to help you ;-) ) Some have had their GNU/Linux system(s) up for several years; collectively they have a wide variety of hardware, special interests and experience as users; we also have several programmers and sysadmins; all have volunteered to help new users get off on the right foot. Frankly, without them we’d both be in a world of hurt ;-)

There are also weekly IRC sessions (optional) over the weekend. There will be a reminder of the schedule and channel sent to the mailing list every Friday. (Since this is an international class, we will try to schedule at reasonable times to accommodate the majority of those interested in participating; so the schedule may change from time to time. If there is sufficient demand, supplemental IRC sessions can be scheduled.)

How much you get out of this course will depend entirely upon you – how much time and effort you put into the learning process, and, of course, how much knowledge, training, and skill you bring with you. There is virtually no limit to how much help you can get from the mailing list, but no one can do all the work for you. If you put a little effort into it, the members of mailing list will help; but rest assured we’re not in the baby-sitting business and this is not a therapy group for co-dependents ;-)

The bottom line is simply that all of us would like for you to succeed. There’s a certain amount of ‘grief’ factor that we cannot eliminate, that’s just the nature of doing things (like defragging your hard disk, making partitions, knowing what hardware you actually have installed and what ports your modem and mouse are on, who your ISP is, etc.). This is really not insurmountable from your end – with a little effort, but nearly impossible for the rest of us to guess! We’ve been there, done that, so we can help make this as quick and painless as possible.

Hardware requirements

Before you buy a distribution or attempt to install Linux, make sure that your hardware is compatible. There are some hardware devices that simply will not work with Linux, or require some effort on your part to get them up and running (usually with a patch freely available by anonymous ftp). See <http://www.tldp.org/HOWTO/Hardware-HOWTO/> for specific details. If any of your hardware is incompatible, you have no alternative but to replace it with something that will is supported and will work. Generally, this will be less than US$100, and more often less than US$50, but may be cost prohibitive for some of you if you have to replace several components, and may not be worth it on some machines.

Linux can be installed on a ’386 with 4 MB of RAM – but it’s terribly slow, not practical for production, and certainly is not recommended. I recommend at least a ’486 and at least 16 MB of RAM for command line, and at least 32 MB for GUI. (The more RAM you have installed, the better the performance; there is no top end as far as the operating system is concerned.)

You can install Linux in 10 MB – but that’s too spartan to be practical and certainly not nearly enough for the graphical user interface (X Window System, or, more commonly X); XFree86 which is the GNU version of X runs about 55 MB by itself). I would recommend an absolute minimum of 100 MB free hard disk space (250 MB or more if you need the compiler and source code to recompile your kernel, and upward of 500 MB if you’re interested in X, the office suites, graphics, programming or multimedia development). We’ll get into this in detail in the early lessons. Fortunately, all new computers are being shipped with multi-gigabyte hard disks, 32 MB RAM, and a 56 K modem. A “complete install” of any of the distributions will require better than 1 or 2 GB – plus whatever space you need for your data, and roughly twice that if you install all the source code.

Computer experience

You really don’t have to be a computer technician or a programmer to use Linux. This course assumes that you have some knowledge about your computer and are comfortable at the command line. In other words, if you can drop out of Windows and type in commands correctly in DOS, you probably will not have much problem with adjusting to Linux. On the other hand, if you are totally dependent upon clicking icons, you’re in for some pretty rough going. Be prepared to learn some basic Unix commands, its filesystem, and some basic utilities and programs. You will have to do a little ‘hacking’ – usually nothing more than editing a couple of lines of code in one or two of the configuration files. Again, if you have any experience editing your AUTOEXEC.BAT or CONFIG.SYS in DOS, you’ll find that it’s as easy to do in Linux as it was in DOS.

Linux will peacefully coexist with your current operating system on a separate partition on your hard disk, or on a separate hard disk. You do NOT need to delete your current operating system or any of its applications! And there are a number of ways to boot into your Linux partition without interfering with your other operating system(s).

Time requirements

Conscientious students should expect to devote an hour to an hour and a half per lesson to course work. That is a lot of time, and basically why the lessons are uploaded twice a week. An hour to 90 minutes a day devoted to Linux is about the optimum. Most can comfortably cover all the material here and a lot more from the mailing list in two months. If you need more time or want to stick around and help others get started, that’s fine, too ;-)

Depending on the textbook, you’ll probably need to allow for an additional half hour each day for reading; some sections you will read through only once, and others will require intense study. For example, modes and permissions are undoubtedly new concepts for Windows users, so be prepared to spend some extra time getting a good understanding of these new terms and concepts. Similarly, you’ll have to spend some extra time learning the basics of vi regardless of your preference for an editor. (vi is likely to be the only editor available to you on ‘rescue’ disks. Things like this will be pointed out during the course.)

There is always the temptation to skip those parts that you feel you are familiar with, but I strongly advise against it – I’d rather have you be bored for a few minutes skimming though material you do know than to have you spend hours later trying to figure something out that was discussed in a section you skipped entirely because you thought you knew everything there was to know about it ;-) Again, to use modes as an example, there is a subtle difference between how these work on directories as opposed to files; and the permissions will likely be different for the ‘owner’ of the file or directory than for other users.

Similarly, the URLs are there to help you, not to waste your time. Some of them are more useful than others, and some of them present basically the same information. You are NOT expected to read every word of every link, but unless you check each one of them you’ll never know what you’re missing. Read the ones that grab your attention, bookmark those that you might want to come back to later.

The course has been online continuously since August 1997. Since then, over thirty thousand have registered. The course has also been adapted by several Linux Users’ Groups and other non-profit organizations for local training and presentations. As with most things on the Internet, the course is still very much a work in progress. These webpages are actively maintained, so if you find a link that’s broken, or have another that should be included, let me know about it <mailto:webmaster@basiclinux.net> .

Registration

The next steps are:

Read the Terms of Service <terms.html> and the <privacy.html> statement.

Register <register.html> for the course.

Subscribe <subscribe.html> to the mailing list.

(Note that all hotmail, bigfoot, yahoo , and mydeja addresses will automatically be denied due to a chronic problem with spam and/or harvesting email addresses – any other domains will be acceptable, subject to change.)

(Also note that Outlook has been banned from the mailing list because of of the inherent security risk it poses to the rest of the subscribers.)

You will need to get a copy of the distribution <textbooks.html> of your choice; and, a <textbooks.html> (preferably one that matches your distribution)

The next term begins Monday, 3 March 2003. Registration for that class closes Saturday, 1 March 2003.

Course Objectives

These are the six major objectives you should accomplish by the completion of the course.

  1. Hardware & Software Compatibility
  2. Choosing a Distribution
  3. Installing the Base System from CDROM
  4. Connecting to the Internet
  5. Customizing Your System
  6. Glossary – Terms and Concepts

Objective 1: Hardware & Software Compatibility

Hardware

First, check that your hardware is currently supported in Linux. The Hardware-HOWTO and Hardware-Compatibility list should cover most hardware.

There is a wide discrepancy from one distribution (and version of that distribution) to another as far as automatic hardware detection, and you may have to use a generic driver if there is no specific driver for your hardware; these work fine, although you may not get all the whistles and bells, then again you may not even miss them.

Record the data about your specific hardware. Much of this information you can get from the Start Menu > Control Panel > System Properties in Windows (this is often inaccurate, but it’s a starting point). Other little tidbits are sometimes in the Users’ Manuals. Note, however, that PC manufacturers have been known to continue shipping obsolete manuals when they change suppliers and vendors (this is particularly true of older laptops and notebooks). Sometimes you have to resort to popping open the case to see for yourself. (Reminder – DO NOT REMOVE THE CASE ON A LIVE SYSTEM! Shutdown; disconnect the power cord to your computer; and properly ground yourself! Generally touching the power supply with your left hand while probing around with your right hand is sufficient. You may need to use a small flashlight and magnifying glass. DO NOT disconnect anything unless absolutely necessary (make a WRITTEN note of what you disconnected and sketch a diagram if you are not accustomed to doing things like this), and remember to reconnect it exactly as it was before you put the case back on the machine.)

The Linux kernel will auto-detect installed hardware on boot – the majority of this information will be in /var/log/dmesg which you can access with the command

    dmesg > boot.msg
    less boot.msg

(This file is about 5-6 KB long.)

Another great source for help is the mailing list for your distribution of choice. The chances are extremely good that someone on that list will have already run into much the same problem, and be able to point you to a quick solution. Search the archives first – no one likes to rehash a thread that goes on forever.

Software

The alphabet soup of Unix tools and utilities will mean nothing to you unless you have previous experience. As a rule of thumb, you will need to install everything in the ‘base system’ for every installation – whether you’re setting up a network server or a stand-alone dial-up connection.

Some of the more popular applications and suites are ported or are being ported to Linux. For the most part these will be virtually identical in operation to what you are accustomed to – minus problems with the viruses, chronic crashes and security.

What you really should concentrate on is learning the basic tools and utilities first.

There is also a wealth of new applications, native to GNU and Linux, that you can try. http://www.gnu.org/software/software.html has an extensive list. Don’t be in a hurry – they’re not going to disappear.

Objective 2: Choosing a Distribution

General differences

The major differences between the distributions are not trivial:

  • the choice of software packages included and installed by default
  • the installation, package management, and system administration utilities
  • the directory structure and file locations
  • the printed and/or on-line manual
  • the mailing list(s)
  • support from the company

Rather than so-called ‘ease of installation’ (which should be a one-time event of roughly 2 hours) or what someone else is using, try to concentrate on the tools and utilities you’re going to have to live with day after day. Almost any software package can be installed and used on any distribution, so don’t be overly influenced by that either. (If push comes to shove, you can always install the source package and compile it yourself – and this is a LOT easier than you may think!)

I would suggest that for your initial installation you stick with the half dozen or so most popular distributions, read their manual, and get on their mailing list. Keep the initial partitioning scheme simple – / and swap is fine; however, I recommend you also partition /home so you won’t lose your email if things go south or you decide to repartition later.

For the initial installation, I strongly recommend you get any of the multiple-distribution CD sets from any of the third party vendors who offer these for around $US2 per CD. Don’t rely of what someone else who has only tried one distribution tells you – it may be an excellent choice in your situation, or there might be something much better and much more suited to what you want to do.

http://www.cheapbytes.com is one the most popular sources, although there are others.

Also don’t forget about your local Linux Users’ Group – often you can get the latest CD burned for you by one of the members, or borrow a particular distribution set. Best of all, you can get experts to actually install the system for you at just about any of the monthly meetings .

The more you read before you make the first attempt, the better and easier the installation will go. Pay particular attention to the instructions for the installation utility you’re using.

Specific to a distribution

You can check the list of software packages that are included with the distribution on the web pages for that distribution. As I mentioned above, don’t be overly influenced by some software being included on the CD or not; focus on the tools and utilities you’ll have to use.

(Also, there is a fairly complete list of GNU packages at http://www.gnu.org/software/software.html.
Use the search engine at freshmeat to locate the latest versions of any package.)

Objective 3: Installing the Base System

Once you have selected a distribution, spend a little time reading through the Installation Guide or manual that comes with it. All the distributions have their own unique setup tools and utilities, so the actual interface will deviate from the examples in the lessons, but the sequence is general the same:

Before you get started with the actual installation, you need to prepare your hard disk

  • backup you work (read “anything that is NOT on the installation CD”)
  • prune – get rid of obsolete software and shareware you don’t need (if you especially want to keep a copy, move it to floppies or burn a CD)
  • run defrag to get all the files physically toward the front of your hard disk, making all available free space continuous
  • run fips to resize your current disk partitions

Now you should be ready to insert the CD-ROM, reboot from the floppy (or from the CD), and begin the installation process.

You have a bewildering variety of options with the X Window System (http:/www.xfree.org).

Once you get your basic configuration (i.e., monitor and video card) set, you might want to experiment with the various window managers. A nice one that I prefer is icewm with themes; relatively small footprint, and a nice assortment of predefined configurations. (FWIW, if you’re short on space, wm2 is the smallest window manager I’ve found.)

On the other end of the resource spectrum, if you’re using gnome or KDE, you’ll probably want to subscribe to their respective mailing lists to stay current – both are developing at a rapid pace, with new applications coming on-line almost weekly.

The thing to keep uppermost in mind is that X ships in a mode guaranteed NOT to work right out of the box! This is to protect you from seriously damaging your hardware. And remember, if you can’t find a driver specific to your video card, the generic SVGA driver will give you excellent results – but you probably will not get all the whistles and bells you would if it was a perfect match.

For GUI, your performance will depend greatly on how much physical RAM you have installed. For example, you’ll need a minimum of 32 MB for XFree86, a window manager, and Netscape; you’ll take a big performance hit with 24 MB, and 16 MB is barely tolerable. If you’re planning on running gnome, KDE, etc., you might as well resign yourself right now to at least 48 or 64 MB RAM.

Remember, also, that you can switch to another virtual console with CTRL+ALT+Fn (where n is any console numbered 1 through 6; console 7 is reserved for X), and back into X with CTRL+ALT+F7. Don’t confuse this with the ‘DOS box in Windows’ – this is the real thing, just as if you had several Windows machines connected to your keyboard and monitor; you’ll have to log in and give the appropriate password for ‘user’ or ‘root’ user.

Objective 4: Connecting to the Internet

Unix and Linux were both designed from the ground up for networking. So you will immediately notice a huge difference in performance in command line mode – all the clients/servers come ‘standard equipment’ with Linux. The nicest part is that Linux is true multi-tasking, so you can be downloading your email and a file by FTP and browsing somewhere else, all at the same time. The only limit will be your ISP connection speed and throughput.

Some people get this set up right out of the box; others have to fight it every step of the way. I strongly urge you to read the lesson, the textbook, and the instructions for your distribution carefully.

However, you need to be aware that you might end up doing some manual editing in one or two of these scripts no matter how they are generated. In fact, you could set up your ISP connection entirely by editing the handful of configuration files you need.

Objective 5: Customizing Your System

There are any numbers of ways your system can and should be unique in all the world:

  • your partitions
  • your boot
  • your kernel
  • your prompt
  • your window manager (and ‘theme’)
  • your crontabs

Objective 6: Glossary – Terms and Concepts

There is no need to get terribly fancy or professional about compiling your glossary – the point is to make you aware of what terms and concepts you need to understand, and an understanding of the directory structure, where the configuration files are and what goes in them. As you run across other files, terms or concepts, add them to your list. It’s there to serve you, not impress anyone .

  • FWIW, I tend to put these and all other brief references on 3×5 index cards. If you prefer, keep your notes in a looseleaf binder.

Perhaps the ‘best’ and most famous on-line ‘dictionary’ is Eric S. Raymond’s Jargon File. You can use the on-line version, or download a copy to your own machine (which might be better if you have 3.2 MB for the HTML version).

By the time you complete the final lesson you should have all these entries filled in. If you don’t, that’s a good indication you’ve been going too fast and/or not keeping up with your assignments.

In addition to the links from the bookmarks file

Just a few of the other good links on the Internet are:

Class Schedule

Note that none of these lessons will be uploaded before the scheduled date. Also note that the schedule is subject to change.

every Saturday and Sunday

Week 1:
Monday, 3 November 2003

  • General Instructions for the Course – Anita Lewis [01-instructions.html]
  • An Overview of Linux – Henry White [02-overview.html]
  • Hardware Requirements and Selecting a Distribution – Barrie James [03-selecting.html]
  • Preparing Your Hard Disk – Diane Labrosse [04-preparing.html]http://blair.armeau.net/blt-0-basic-linux-training.html
  • Partitions & Partitioning – Anita Lewis [05-partitioning.html]
  • Booting & Boot Managers – Anita Lewis [06-booting.html]

Week 2:
Monday, 10 November 2003

  • Filesystem – Henry White [07-filesystem.html]
  • Essential System Administration – Henry White [08-sysadmin.html]
  • Basic Unix Commands and Concepts – Gary Leaf [09-commands.html]
  • Installation of Linux from CD-ROM – Henry White [10-installing.html]
  • ISP Dial-up through Linux – Henry White [11-dialup.html]

Week 3:
Monday, 17 November 2003

  • User Clients – Henry White [12-user-clients.html]
  • Linux Tools and Applications – Stefan Waidele [13-tools.html]
  • Printers & Printing – Joe Clark [14-printer.html]
  • Using CDROM-R/CDROM-RW – Henry White [15-burning.html]
  • Sound – Chris Palmer [16-sound.html]

Week 4:
Monday, 25 November 2003

  • Shells – Henry White [17-shell.html]
  • Shell Programming – Henry White [18-shell-programming.html]
  • KDE – Kay Schenk [19-kde.html]
  • Gnome – Henry White [20-desktop.html & 21-desktop-custom.html]

Week 5:
Monday, 1 December 2003

  • Upgrading Software and Other Administrative Tasks – Henry White [22-upgrading.html]
  • gcc and make – John Tilp [23-gcc-make.html]
  • Kernel Rebuilding and Using Kernel Modules – Henry White [24-rebuilding.html]
  • Bugs & Patches – Henry White [25-bugs.html]

Week 6:
Monday, 8 December 2003

  • perl and CGI – Kay Schenk [26-perl-cgi.html]
  • Linux Telecommunications and Networking – Henry White [27-networking.html]
  • Samba – Stefan Waidele [28-samba.html]
  • Linux Networking and Remote access – Stefan Waidele [29-lanremote.html]

Week 7:
Monday, 15 December 2003

  • Wireless Security – Bill Eastman [30-wirelesssec.html]
  • Security – Henry White [31-security.html]

Week 8:
Monday, 22 December 2003

  • Performance Tuning Tips and Techniques – Henry White [32-tuning.html]
  • Beyond This Course – Henry White &nbsp;  [33-beyond.html]

New Term Begins:
Monday, 5 January 2004

Copyright © 1997-2003 Henry White. All Rights Reserved.
Reproduction or redistribution without prior written consent is strictly prohibited. Address comments and inquiries to info@basiclinux.net

Sorry, comments for this entry are closed at this time.

Proudly powered by WordPress. Entries (RSS) and Comments (RSS). Silver Light 3-Column theme by Bob, modified by Ms. Crafty.