Article Source: http://EzineArticles.com/?expert=Yao_Chuanghai

Which Linux distribution is right for you? There is no one right answer because it depends on your experience and specific needs. Listed below are the top seven Linux operating systems for 2011. Each program was ranked based on ease of installation, user-friendliness, and amount of support available.

Ubuntu is one of the most popular Linux distributions for desktops. New versions are released about every six months. This program is easy to install and use. The ample support comes from both technical professionals as well as end users. Ubuntu is a great program for beginners.

Mandriva originally appeared to be a restructured version of Red Hat Linux. The current software has added user-friendly features including better hardware detection and intuitive disk partitioning. Mandriva also utilizes a KDE desktop and has great support which makes it a good program for beginners.

PCLinuxOS is great for new Linux users due to its intuitive graphical installer. It provides users with current desktop software and fast boot times. This program received our lowest rating for support because it does not provide support in any language other than English. Additionally, the program is only available in a 32-bit version and new releases are not scheduled regularly.

Gentoo was designed for power users, allowing them to have ultimate customization capabilities. It also has exceptional security. One of its best features is the ability to keep the system current without re-installing the software. However, long compilation times and occasionally instability makes it less of a crowd pleaser than other available software.

OpenSUSE has an extensive and intuitive configuration tool. The program also includes user-friendly desktop environments (GNOME and KDE). The program gets high marks for help and support. However, its heavy use of resources for desktop setup and graphical utilities tend to slow the program down.

Debian GNU/Linux supports more infrastructures than any other Linux distribution program and contains more than 20,000 software packages. It has become the largest Linux distribution ever created and has inspired over 120 Debian-based distributions. The program has a reputation for stability and being the most bug-free Linux distribution system on the market. However, their intensive testing has led to lengthy intervals between releases, typically 1-3 years.

FreeBSD was introduced into the market in 1993. The program is not in the same league as the other programs listed. However, it is fast, stable and has over 15,000 software applications available. FreeBSD lacks a graphical installer and the convenient features of hardware detection and system configuration which must be performed manually by the user.

Ultimately, you must choose the program that is right for you. Ubuntu and PCLinusOS enable beginners to use Linux without requiring a steep learning curve to produce results. Gentoo and FreeBSD are definitely for more advanced users. Mandriva, Debian GNU/Linux, and openSUSE are the best programs if you are willing to trade some advanced features for stability and continuing support.

Article Source: http://EzineArticles.com/5780077

Linux Commands Training Tips: The Linux System Administration concepts and tasks covered here apply to ALL other Linux distributions, including: Red Hat, Fedora, Slackware, Ubuntu, Kubuntu, Edubuntu, Debian, SUSE and openSUSE.

5 Things to Consider When You Need to Get Linux Books:

1. Linux Books – In General

Linux books are often outdated as soon as they’re printed, due to the slow nature of the publishing and printing process.

Some look current, but only the cover and the “free” Linux CDs inside have changed. For example, there are some popular books that continually come out with a new cover and new CDs, for a “new” version, but the content in the book isn’t updated nearly as frequently as the cover!

If you are new to Linux, getting confused by outdated books is the last thing you want.

2. “Easy Linux” books or “Simple” books

Although promoted as “Easy Linux” books or “Simple” books, a lot of these books start training you at an intermediate or advanced level and never cover the basics that are required for new users.

These types of books can be extremely frustrating for someone trying to learn Linux. Many books are written at a very basic level, and not specifically for someone new – and these are often just a waste of time.

3. Free Linux Books Online, including eBooks

There are free books online at lots of web sites, but they are often written by highly technical people . . . for highly technical people – they are often far too advanced for people who are new.

Once you’ve short-listed a few books, try to find the table of contents and one or more sample chapters of each and read them. This will give you an idea of how well they describe the concepts and commands you need to learn.

4. “Vendor Neutral” Linux Books

There are over 130 Linux distributions (versions) and about 5 of these are the “major” (very popular) ones. And there are lots of Linux books for each of these, such as Red Hat and Ubuntu Linux. There are also books that are “vendor neutral” – they are general and not for a specific distro.

The best Linux administration books to get are ones that describe commands and spend little or no time on GUI (Graphical User Interface) utilities – and here’s why.

Linux GUI utilities can be used to do system administration tasks, but they are very slow and cumbersome to use, in comparison to using commands. Also, GUIs are usually different from one distro to another!

However, the way a Linux command works in one distribution is usually identical, or very similar, to the way the same command works on a different distribution. And the best way to do system administration is by running commands.

You need to get books to get training on how to use commands and in this way, you’re learning how to use Linux on all distros!

Linux Training Tips: Try to find books that are not written for just a single Linux distribution and that provide training on the use of commands.

Although rare, some will even compare the way various distributions work. This includes describing the minor differences between how a Linux command works in one distro and how the same command works in another.

5. Reviews of Books at Linux Forums

Linux book reviews may be able to help you in your selection, but you need to try to determine if the review is unbiased.

To get accurate, unbiased book reviews, try going to some forums and looking for a “Linux Books” category. Some forums even show ratings of and comments by the members of the forum.

Also, try posting a question at one or more forums describing the type of books you are looking for.

Linux Training Tips: Do an internet search for “linux forums reviews of books” to find what you need.

An excellent alternative to Linux books are Linux training videos (nudge, nudge, wink, wink).

By Clyde Boom

Overview:

Both Linux and Windows (2000, NT, XP, Vista) are operating systems. Linux was inspired from Unix, while Windows was inspired from VMS.

While no single company “owns” Linux, Windows is owned by Microsoft. Various distributions (often referred to as “distros”) of Linux come from different companies (e.g. Red Hat, Novell SuSE, Mandrake etc.), while all Windows flavors (95, 98, 2000, XP, Vista) come from Microsoft.

Both Linux and Windows come in Desktop and Server editions.

Cost:

As far as cost is concerned, Linux is very cheap or free. I used the word “very cheap” for enterprise users. While anybody can download, install and use Linux, the distribution companies usually charge for technical support.
Windows is expensive. You first pay for the copy of the software and then again for the technical support if you ever want it.
There is another catch though; Windows enforces you to use a single copy on a single computer. This is not the case with Linux though, once you purchase Linux, you can run it on an unlimited number of computers.

GUI:

Both Windows and Linux are GUI based operating systems.
I’m afraid but, Windows has better GUI than Linux and it will get far better with the upcoming Windows Vista release. Linux has two GUIs: Gnome and KDE. Linux is fast catching up and is evolving from a server operating system to a desktop operating system.

Command Line:

Both Windows and Linux comes with command line interface. Windows calls it the “DOS prompt”, while Linux refers to it as the “shell”. Linux’s shell is far more superior than Window’s DOS prompt. It can do a whole lot of things that are not possible in Windows. Linux support various command line shells such as BASH, Bourne, Korn, C shell and many other.

Third Party Application Software Availability:
Both Windows and Linux run third-party applications. Windows, compared to Linux, has far greater number of third party applications available for use. A program written for Windows will not run under Linux (although it can be made to emulate, but it will be very annoying and hence not recommened).

Linux’s application base is, however, increasing threefold. On a more close examination, the average computer user uses the following applications 90% of the time: Word Processor (Office suite), E-mail client, Web browser, Media software, and Instant Messenger. Linux has all these applications and in fact has many flavors for each.

Like Linux, all third party applications are very cheap or free. Whereas, Windows applications can cost a leg and a limb.

Security:

Simply put it this way, Windows is not secure. If you are using Windows and don’t have Antivirus, Anti Spyware, and firewall (memory and resource eating applications), your computer can get affected by a virus in less than 10 minutes. I remember restoring a fresh copy of Windows XP on my Toshiba A40 notebook. I was browsing the Internet with Microsoft Internet Explorer and my machine got infected with loads of spyware in less than 15 minutes!

Microsoft came up with Firewall and Anti Spyware products, but these programs run in the background and eat up your computer’s precious memory.

Linux, on the other hand, doesn’t have these issues. I’m not aware of any spywares for Linux. One can safely run a Linux distro without ever worrying about installing Anitvirus or Anti-Spywares.

Windows also has more security flaws than Linux. By security flaw, I mean a hacker can compromise the Windows operating system and break into your machine and destroy your files. But, flaws on Windows are quickly fixed and patches are often made available almost instantly after the flaw is reported.

Supported Hardware:

Windows was originally designed for Intel based machines. Earlier version of Windows NT also ran on RISC and Alpha architectures, but not anymore.
Linux run on a wide variety of hardware. And can support some very old legacy hardware. I’ve seen a Linux distro running on a 486 based machine.

Diver Availability:

As one author once said, “Windows is a bag of drivers”. I think that is quite true. Installing a new hardware device is a piece of cake in Windows, whereas it can be a nuisance on Linux especially for average Joe. I can’t in my wildest dreams imagine my dad installing a sound card successfully in Linux.

Things however will not stay the same for long. Manufacturers are also offering Linux drivers for their hardware, which will simplify the process.

Network Support:

Linux beats Windows bad in this area. Windows was never designed for the Internet. Unix, on which Linux is based, was designed for Internet (or Network) and is far more efficient compared to Windows. A senior Network Administrator working for a Fortune-500 company, recently pointed to me that if we monitor the traffic between exchange Windows based Exchange Server and Client, we can see that hundreds of packets are going to and from even when both are idle. He said that such is not the case with Linux.

However, our average Joe will never see or feel any difference. Windows Internet is good enough for him.

File System:

Windows Vista will use a new file system called WinFS. Earlier version used FAT (FAT16 and FAT32) and NTFS file systems, with NTFS being the preferred choice. Linux supports ext2 and ext3 file systems.

FAT file systems were mediocre, but NTFS can be compared with the Linux file systems.

Both file systems allows us to create directories, sub directories and file. Linux file systems are case-sensitive whereas, NTFS is not.

Normally, Linux systems cannot access NTFS file systems, but with the help of add-on software, it can.

Help and Documentation:
Linux help and documentation is quite good, accurate and to the point compared.

I’ve been using Windows for well over 8 years now. Frankly speaking, I hardly ever checked the accompanying documentation or the help file because everything is so simple that nobody needs to venture in the help file.

What should I buy?

OK. Truth hurts, but let it be. If you are average Joe, that extra $300 on Windows are worth spending. If you are looking an OS for your server, never even think about Windows. Buy Linux.

By Umer Mansoor

Each side has made some good points and each side, in my opinion, has also twisted the facts and figures to serve their own arguments and opinions. Whether you love Microsoft and hate Linux or Love Linux and despise Microsoft, the fact is that both operating systems are here to stay. Both operating systems have been adopted in the enterprise and both operating systems serve a purpose that the other is not able or capable of fulfilling to the extent required within the enterprise. With that said, lets turn our attention away from the war and to the reasons that Linux has not been more widely adopted in the enterprise environment.

When I discuss Linux in the enterprise I am not speaking to Linux on the end-user desktop. We all know that Microsoft simply beats Linux on the desktop, hands down. Today’s Linux desktop is more cumbersome to use and support, but the primary reason for the lack of desktop adoption is the lack of business and productivity applications supported on Linux. As enterprises have grown and continue to grow, however, they have discovered that there is a need for Linux. They have discovered that Linux excels in the enterprise when it is deployed in the data center.

Linux has become a common enterprise back-office platform for many types of enterprise applications. Database servers, portal applications, web servers, server virtualization and even firewalls are all common enterprise applications that utilize Linux as the network operating system. In these types of roles Linux delivers the performance and reliability that an enterprise needs to meet business goals.

With the major benefits that Linux can bring to the table why have we not seen a more rapid adoption of Linux technologies in the enterprise? There are several reasons, but it most instances the issue revolves around the lack of experienced support personnel and a lack of understanding in terms of Linux in the data center.

One of the primary reasons for a slower adoption of Linux is support. Microsoft supporters continually point out that Linux is more complex to administer when compared to Microsoft Windows Server, and they are right. Linux is a very flexible platform, and with this flexibility comes complexity. Microsoft Windows Server is designed to operate one way reliably and consistently. While you can configure some parameters on Microsoft Windows Server it is in no way as flexible as Linux. Linux allows you to customize practically every conceivable parameter to suit your needs. Again, it is this flexibility that introduces the complexity of managing a Linux platform.

Given the fact that a Linux server requires a more skilled administrative resource when compared to Microsoft Server it is this requirement that is a primary factor in the slower adoption rate of Linux in the enterprise. To be clear: I am not saying that Microsoft professionals are less skilled; what I am saying is that the complexity of Linux requires a Linux administrator to possess a more in-depth level of understanding and experience with the Linux OS. Because these skills are not yet as prevalent in the industry today as Microsoft skills, the adoption rate of Linux is slowed as IT managers and CIOs are reluctant to introduce a system they view as potentially harder to maintain.

Further impacting the adoption of Linux is the lack of understanding in the industry when it comes to Linux. When IT professionals think of Linux there is a natural tendency to think about Linux on the desktop. In fact, most Microsoft supporters base their entire anti-Linux argument on the Linux GUI desktop compared to one of the several flavors of Windows still in use today. More often than not this comparison is carried over to the Linux server platform, where the differences in raw capability between Linux and Microsoft Windows Server are far fewer. Put bluntly, comparing Linux deployed on the desktop to Linux deployed on the server is like comparing Microsoft Windows 3.1 to Microsoft Windows Server 2003. The comparison holds no merit in this example, just as it holds no merit when comparing Linux on the desktop to Linux deployed as a server platform.

The only true advantage Microsoft Windows Server has over Linux is in the numbers of supported applications available for each platform. While Linux is far from being an acceptable option as an enterprise email platform, for example, this is not because Linux is a poorer choice for such an application but rather because of the position Microsoft has in terms of third-party application support. If tomorrow an email platform equal in functionality to Microsoft Exchange Server were to be released for the Linux OS, Microsoft would be hard-pressed to retain the deployment numbers they enjoy today in enterprise Exchange customers. As major industry software developers such as Oracle, IBM and SAP continue to expand their software offerings to the Linux platform it will become increasingly more difficult to ignore Linux based simply on its name.

Understanding the performance and reliability that can be gained from a Linux deployment is key to understanding the benefits of deploying Linux-driven technologies along side Microsoft solutions in the enterprise data center. As the numbers of IT professionals with Linux skills continues to grow so too will the adoption rate of Linux in the enterprise.

By Mike Dailey

With a Linux script, you put a series of routinely run commands in a text file, and then run all of them by simply typing in the name of the file and pressing Enter.

Linux Script Example to Create a Script to Automatically Run A Series of Linux System Administration Commands

Follow along with the steps in the example below to create and run your first Linux script!

1. Run a Linux text editor.

2. Put the following text at the top left of the text file (indented below for emphasis):

#!/bin/bash

This indicates that the text file is a Linux script file.

Press Enter twice to have a blank line below the line above.

3. Put the Linux command(s) in the script file.

The Linux commands below are used to provide an example. You can put any commands in a script.

The Linux commands below will: clear the screen, change into the /etc directory path, and then show the current path with the Linux pwd (path to working directory) command.

Then provide a long list of the fstab file (to show you that it’s there) and then change into your home directory (represented by the ~ symbol) and then show the path of the current directory.

The Linux echo command is not required, but has been put in the file to show the progress of the execution of the script.

Also, you don’t need to indent the commands below in the Linux script – they are just indented here for emphasis.

clear
echo The screen has been cleared

cd /etc

pwd

echo This is the etc directory

ls -l fstab

echo This is a long listing of the fstab file

cd ~

pwd echo Now in my home directory

Linux Commands Training Tips: A Linux script can contain hundreds of lines of text if necessary – and also include complex programming logic, such as if . . . then statements.

4. Save the text / script file with a meaningful name to create it and by give it a name.

For example, if you want to list files in a few directories, call the file: listdirs

5. Run the Linux chmod command to change the permissions of the file and make the Linux text file “executable”.

In our example, the file is named: listdirs

Below is a Linux chmod command example for running the chmod command to change the permissions of the Linux script file – and to make the listdirs text / script file “executable”, so that you can run the script file in the same way as you run a command.

The $ (dollar sign) below is the Linux command line prompt. Don’t type in the $ (dolar sign), type in the command that appears at the right of the $ prompt.

$ chmod u+x listdirs

The Linux command above is chmod and it is being used to assign the x (executable) permission to the u (user) of the file with: u+x and the script file name is listdirs.

Running a Linux Script to Run System Administration Commands

To run a Linux script (that is in the “current” directory), such as the listdirs script, simply type in a period (dot) and a space and then the name of the file and press Enter.

$ . listdirs

The concepts and Linux command examples shown above work in Red Hat, Ubuntu, Fedora, Slackware, and Debian Linux – and also ALL Linux distributions.

By Clyde Boom

Here’s an easy-to-use checklist of things to look for when choosing a Linux distribution.

Linux OS Distribution Characteristics Checklist – Linux Distro Checklist Summary – Linux Distro Training

Here is a summary of the main characteristics to look for in a Linux distribution:

A Comprehensive and Easy-To-Use Linux Installation Routine

Make sure the Linux distribution you’re considering using has an easy-to-follow installation routine – that shows you step-by-step – how to put the Linux OS, commands and other software programs on the hard disk(s) in your system.

One or More Linux Desktops – For A Point-And-Click GUI Environment

When you boot a Windows system, you are automatically at the Windows desktop and there is only one desktop to use. However, with Linux there are several desktops to choose from.

So try out the main Linux desktops (GNOME or KDE) and possibly try out others to see which one you like the “look and feel” of the best.

Linux Commands Training Tips: You may want to get free (by download) or very inexpensive (by mail) Linux “live” CDs or DVDs to find out which desktop you like the best. And then be sure that the Linux distro you decide to use offers that Linux desktop.

Just do an Internet search for “linux live cds” (without the quotes) and find a vendor that will mail you several Linux “live” CDs or DVDs by mail very inexpensively. Then boot your system with the “live” CDs or DVDs in your CD or DVD drive – and Linux will start up, load and run automatically in your system so you can give it a try!

Linux Application Software Programs – Open Office Suite And “Others”

Make a list of the Linux application software programs you need and be sure your Linux distro has these software programs (by trying them when using your “live” version) – and if not, see if you can get the software you need at: http://sourceforge.net

Other Hardware Drivers – Provide Communication Between Linux and Hardware

Before you make your decision on the Linux distribution that’s right for you – and before installing it – be sure to do a very detailed check that ALL of your computer system hardware components – especially your modem (if you use one), your printers, and your video card – to make sure your hardware components will work with your Linux distribution and allow you to access ALL the features of your hardware, such as all the features of your printer.

Linux Distribution Documentation

Make sure you read some sample sections of the software manuals (and any other Linux training materials) for the distribution that you’re thinking of using – and that the manuals are easy-to-use, up-to-date and easy to read.

By Clyde Boom

This article is not about the history of Unix; however, Unix is such a complex issue that it deserves few words in this respect: BSD family of Unix systems is based upon the source code of real Unix developed in Bell Labs, which was later purchased by the University of California. Thus, the name of the family of Unix systems called BSD is derived from “Berkeley Software Distribution”. The contemporary BSD systems stand on the source code that was released in the beginning of 1990′s (Net/2 Lite and 386/BSD release).

No one person or any entity owns BSD. Enthusiastic developers create it and many of its components are open-sourced.

BSD is behind the philosophy of TCP/IP networking and the Internet thereof; it is a developed Unix system with advanced features. Except for proprietary BSD/OS, the development of which was discontinued, there are currently four BSD systems available: FreeBSD, NetBSD, OpenBSD and Mac OS X, which is derived from FreeBSD. There are also various forks of these, like PC-BSD – a FreeBSD clone, or MirOS, an OpenBSD clone. The intention of such forks is to include various characteristics missing in the above BSD systems, on which these (forks), no matter how well they are designed, only strongly depend. PC-BSD, for example, has more graphical features than FreeBSD, but there are no substantial differences between these two. PC-BSD cannot breathe without FreeBSD; FreeBSD or OpenBSD are independent of one another.

What is Linux?

Albeit users like to use the term “Linux” for any Linux distro including its packages (Red Hat Linux, Mandrake Linux, etc.), for IT professionals Linux is only the kernel. Linux started in 1991, when its author, Linus Torvals, began his work on a free replacement of Minix. Developers of quite a few Linux system utilities used the source code from BSD, as both these systems started parallelly in about the same time (1992-1993) as Open Source.

Today, there are a few, if not many developers of their own kernels/operating systems (FreeDOS, Agnix, ReactOS, Inferno, etc.), but these guys simply missed the right train in the right hour. They did not lose anything except for the fact that they may be even better programmers, but without the public opinion acknowledging this at large. Linus built his fame also from work of many developers and he went on board in the right time. Linus deserves a credit as a software idea policy maker and he helped very much in this respect.

(Open)BSD vs Linux

It is often difficult to say what is better if you compare two things without regarding the purpose of their use. Mobile Internet may appear better for someone who travels often, but for people working at home such mobility is not necessary. In this view, it is a stupid question when someone asks: “What is better, a mobile or static Internet?” It all depends…

If you compare Linux and OpenBSD in their desktop environment features, Linux offers more applications than OpenBSD; but in a server solution BSD systems are known to be robust, more stable and secure, and without so many patches distributors release soon after their new version of Linux slithered to light.

BSD systems are based upon real Unix source code contrary to Linux, which was developed from scratch (kernel).

Differences between BSD and Linux

1) BSD license allows users/companies to modify a program’s source code and not to release changes to the public. In other words, BSD licenses allow commercial use and incorporation of a code into proprietary commercial products. This is how Microsoft incorporated BSD networking into their products and how Mac OS X earns money through muscles of FreeBSD.

Linux uses GPL license for most of the time (applications in Linux can also have a BSD license – or any license; it is up to developers how they decide). With a GPL-licensed program anybody can change the source code, but he or she MUST share it with the Open Source community to make sure that everybody will benefit from such a change.

2) BSD has the so-called “core system” (without packages). The core system consists of basic utilities (like ssh, fdisk, various commands like chmod or sysctl, manual pages, etc.) and anything beyond this is strictly seen as an add-on. Linux (not only the kernel, of course) is usually packaged as the whole system where this difference is not seen.

3) On BSD systems, all add-on packages are strictly installed into the /usr/local directory: documents to user/local/share/docs/application_name; themes and other things to /usr/local/share/application_name; binaries to /usr/local/bin/application_name. By application_name we mean a program’s name, so if you install IceWM, for example, its binary will be here: /usr/local/bin/icewm. With Linux, on the other hand, all applications get mostly installed into the /usr/bin directory.

4) BSD systems use the system of “ports”, which are fingerprints of applications in the /usr/ports directory, where a user may “cd” and execute a make command, which will download, via a directive contained in such a fingerprint’s code, the application’s source and the system will compile it as well. “Ports” are actually add-on packages for BSD systems and they are also packaged in packages repository of a concrete BSD system. They can be installed as binaries, too, with use of the “pkg_add” either directly from the Internet or locally. But “ports” have that advantage that if an author of any package makes a new version, a user can immediately get its newest/updated version. Packages released for a particular BSD version (like OpenBSD 4.1) are not updated and users have to wait for a new BSD release (like OpenBSD 4.2).

5) BSD systems have also their stable version. With FreeBSD, for example, you have a FreeBSD-Release (a version that can be used normally), FreeBSD-Stable (system more profoundly audited for bugs and security holes), and a development version – Current, which is not stable and not recommended for a regular use. Some Linux distributions started to imitate this philosophy, but with BSD systems this way of making distributions has become a rule.

6) Of course, the kernel is absolutely different.

7) BSD has FFS file system; it is the only file system on BSD’s contrary to Linux, where you can use dozens of file systems like ext2, ext3, ReiserFS, XFS, etc.

BSD systems divide their partitions internally. This means that after installing a BSD system to a hard disk, programs like fdisk, Partition Magic, Norton Ghost and many others will not see this internal division of a BSD (FFS) disk; thus, repartitioning of a disk is not such a pain when administrators require a rigorous partitioning (for /home, /tmp, /var, /etc directories). As a consequence, the naming convention also differs a little: a disk – /dev/ad0s3b in FreeBSD indicates that you deal with “slice” 3 (“s3″), which is the equivalent of Linux /dev/hda3; the internal “partition” has the name of a letter: “a”, “b”, “e”, etc. (“b” is a swap partition). BSD systems also use different naming conventions for devices (disks, etc.).

9) Unless you make a good kernel hack, BSD systems can only be installed into the primary partition. This is not the rule with Linux. However, as BSD systems offer the above-mentioned internal division of partitions, this is not any pain. PC architecture for disks (IDE) follows the rule that you can have only four primary partitions. We will illustrate this on Linux: /dev/hda1 (note: first partition on master disk on first IDE channel), /dev/hda2 (second partition), /dev/hda3 (third partition), /dev/hda4 (fourth partition). PC architecture allows creation of the so-called logical disk on a physical disk (/dev/hda5, /dev/hda6, etc.). You can have as many logical disks/partitions as you wish and you can also install Linux into these “logical disks”. On the other hand, installing a BSD OS into such a “logical partition” is not normally possible.

10) System configuration is manual for most of the time, but various clones like PC-BSD break this convention. The manual approach is a very good thing, as administrators have everything under control without being pushed to waste time in a labyrinth of bloated configuration menus. A good comparison is to imagine a car mechanic repairing the car’s engine covered by a thick blanket. To give you even a little better example – you will hardly find a Linux distro that does not have a default X startup (graphical environment). Of course, you can switch off the X environment during the installation configuration, but if you keep forgetting like me and forget to switch this off, or you have difficulties to find it in the menu somewhere, you realize that most Linux distributors do indeed impose on us only one approach – to put our fingers first on the thick blanket, then on the engine. If you are a good administrator, you do not usually trust vendors who program you how to use Linux – you are the boss and you must have your own freedom. However, in most cases you lose few hours instead by deactivating various services, which are, unfortunately, not even necessary but almost always activated by default. Linux is praised both for being a good desktop and server, but administrators of a good server do not need X. The more software is stored on your hard disk, the more security problems you will face, because it is impossible to audit every package in every unthinkable situation. Good and secure systems are always tight, light and simple.

11) All BSD systems have a Linux emulation support. Running BSD binaries on Linux is a little harder.

12) BSD systems have less support from driver vendors, thus they lag behind in this view (they are not worse, but many vendors support only Microsoft and Linux). With a BSD system you must carefully research the Internet for supported products/chipsets before purchasing any hardware.

13) BSD systems do not use the Unix System V “runlevel scripts” (initialization startup scripts) like Linux.

14) BSD kernels can be set to several security levels. This is also possible with Linux, but BSD’s have taken a very good care of this kernel-tuning feature, which makes it even impossible to change something in files in higher security levels – you cannot delete them.

15) BSD’s have everything under one ROOF. Various Linux programs are often not even compatible with other Linuces. For example, if you install a SuSE RPM package on Mandrake, it may not work. BSD’s have one solid crown of power. If you move from Linux to FreeBSD, you will soon find out that you got out of this chaos. Do you want a package? Just visit: http://www.freebsd.org/ports/ and download it. Unless its developer made some programming errors, it will always work.

16) Generally, BSD systems boot and reboot faster than Linux. Linux can do this, too, but it must be tuned. It is very surprising that Linux is shipped, on the one hand, on huge DVD’s and, on the other hand, it has a compressed kernel. BSD systems do not use (but they can) a default kernel that is compressed, thus the system boots always faster. As I mentioned earlier in this article, Linux vendors program users to use various, often unnecessary services. I do not need SAMBA (file and print services) and many other things as well. Linux reboot process takes longer because various services running on Linux need time for deactivation. Many Linux users do not even know what is the purpose of these services.

17) In comparison to BSD, most Linux distributions are overbloated. Few good users noticed this some time ago and a new trend in the Linux world started with ideas to get closer to a BSD-style use. One of such distributions is Gentoo Linux, but also Slackware Linux, which has preserved a very good shape since its first release (1993). The Gentoo “About” page (http://www.gentoo.org) says that, “Gentoo is a free operating system based on either Linux or FreeBSD…” Therefore, if you use Slackware or Gentoo, these Linuces will always reboot faster than any other Linux.

18) If you compile programs from ports, you will not stumble into compilation errors. BSD packagers prepare their packages carefully, so that users will always compile them successfully. This does not always happen with Linux.

Conclusion

I am the author of One Floppy CD Audio and MP3 Player: freshmeat.net/projects/1fcdbsd and I really like all BSD systems. Some advertisements follow the same pattern as viruses and advertised products are not always good. If you are interested, FreeBSD has the best documentation from all BSD systems, so reading it will only help.

Copyright (c) Juraj Sipos

You can run Linux with or without a desktop. And when it’s going to be used as some type of Linux server, it’s often installed and run without a desktop – as one is not needed on a Linux server.

As a new Linux user getting Linux training, be sure to run Linux with a desktop. Having a Linux desktop makes it easier to run Linux software programs and run Linux commands.

3 Ways to Get a Linux Desktop – So You Can Easily Run Linux Software and Run Linux Commands

1. Using a Linux Live CD / DVD

If you decide to get Linux as a “live” CD / DVD version (which is a fast and fun way to get Linux running), be sure to get a live CD / DVD version that boots to a Linux desktop.

2. Running Linux in Windows as a Virtual Machine

If you download a free Linux virtual machine to run Linux in Windows, be sure to download a version that includes a Linux desktop, as some Linux virtual machines don’t include a desktop – and installing a Linux desktop afterwards can be a real hassle and very time-consuming.

Linux Tips: Check the web site where you get the Linux virtual machine to see if the version you are about to download includes a Linux desktop.

3. Installing Linux onto a Computer System from CD or DVD

When you install a Linux distribution (version) on a computer system, some automatically install one or more Linux desktops and other’s don’t. Again, be sure to select one or more Linux desktops during the installation process.

Linux Tips: Two of the most common Linux desktops are the GNOME desktop and KDE desktop – and sometimes you can install both of them (or others). If you can install more than one desktop, be sure to do so. When you go to log in to Linux after the installation, you can select the desktop you want to use. This will allow you to try out different desktops and see which one(s) you like best!

Once you get Linux and can boot to a Linux desktop, you can use Linux video tutorials to get easy Linux training and learn how to use Linux step-by-step!

By Clyde Boom

Linux Commands – The great thing about Linux commands is that they are virtually identical from one Linux distribution (version) to another. So the way the real pros do Linux administration is to work at the Linux command line and run Linux commands.

Learning how to run a Linux command can be very difficult for someone new to Linux, so here are some Linux tips that will help you to learn how to use Linux commands when working at the Linux command line prompt.

There are three main parts of a Linux command:

1. The Linux command name

2. Options that can be used with the Linux command

3. The “item(s)” that the Linux command is being run “on”

When you run a Linux command, spaces are used between: the Linux command name, the command options and the “item” the command is being run “on”. The “item” could be a Linux directory, file, user or some other Linux software component.

For example, you run the Linux command named ls (for list) “on” a Linux directory to see a list of files in the directory. You run the Linux command named rm (remove) “on” a Linux directory to remove the directory from the Linux file system.

To run a Linux command, you type in the name of the command, and any other parts of the command, such as options, and press the Enter key.

You can see an example of the Linux command that is used to create a new Linux user below. The useradd command is being run “on” the bthatcher user name to create this Linux user.

Linux Tips: Linux commands are run at the Linux command line prompt and this prompt is shown as ]# at the left of the command. You don’t type in the prompt, you type the Linux command at the right of the prompt.

Linux Tips: The Linux command prompt may also appear as: ]$ or as another symbol, instead of # or $.

]# useradd -c “Becky Thatcher” bthatcher

This Linux command creates a new Linux user named bthatcher with the full name of “Becky Thatcher”. The -c (for comment) option is used with this command to add the full name as a comment to the Linux user name of bthatcher.

One of the easiest and best ways to get Linux training is to see Linux commands being run in Linux video tutorials. With this method – you see, hear and do.

With a Linux video tutorial, you see and hear how to run a Linux command and see and hear a description of the output of the command. You can also pause the video so you can run the Linux command yourself!

Copyright © 2007 Clyde Boom