Jump to content

The Linux advantage - Why Linux is the best OS


Recommended Posts

Linux is more than a hip buzzword in computing. It is more than the latest fad. It was modeled on the Unix operating system first developed by Dennis Ritchie and Ken Thompson at AT&T. Unix was developed to run the largest network in world, the AT&T telephone system, and it did. The Unix operating system was designed to be scalable, reliable, modular, secure and portable with network extensibility.

The development of Unix eventually led to the POSIX standard which defines much of the Linux architecture. Unlike many single user desktop console based operating systems, Linux is a multi-user, multi-tasking, network enabled operating system accessible from anywhere on the network. Multiple users can access a Linux computer remotely, each running their own individual desktop instance, all at the same time. The Linux/Unix X-Windows network enabled multi-user windowing system allows full remote access. This is a sharp contrast to a single user console based OS which requires the user to be physically present at the computer in order to access his desktop and applications, limiting access to one user at a time. The Linux/Unix OS was designed to support remote and secure multi-user access using ssh. This gives all Linux/Unix administrators and users a powerful flexible standard remote interface while the automobile is often the primary remote access tool of other OS administrators (i.e. Windows 98 and NT).

The use of Linux/Unix pipes, tees and redirection allow a modular approach to the design of Linux/Unix tools. They allow the capability of any tool to be extended, chaining input and output with other tools. In operating systems like DEC/VMS, paging and formatting capabilities were built into a tool, instead of leveraging the capabilities of standard Linux/Unix tool components like "more", "sort", "less" and "awk".

Linux/Unix shell scripts provide a batch scripting capability which can be scheduled, propagated to other systems or used to create new commands. GUI only interfaces may require physical point and clicks on each system to perform a task. While some debate GUI vs commands and scripts, Linux/Unix embraces both.

The system startup and shutdown is controlled by the system initialization configuration file /etc/inittab and the init scripts in /etc/rc.d/init.d/... The system startup and shutdown procedures are configurable and extensible. One may control which services are started upon system boot and which are terminated on system shutdown, as well as the sequence dependencies. This allows for the orderly shutdown of databases and other sensitive programs which should be shutdown by the application itself, rather than killed while processing, which could lead to data corruption or loss. The system can be booted to various "init" states allowing the system to operate in various configurations to support maintenance and system debugging. On many competing operating systems, the shutdown procedure is not extensible or modifiable.

Linux avoids the MS/Windows "DLL HELL", which causes Windows or its applications to fail when a newer or incompatible run-time dynamic linked library (DLL) is installed. (See Microsoft DLL database used to help avoid conflicts.) Linux employs version numbers in its run-time shared object libraries, which can therefore coexist on the system with different versions of the same libraries. The Linux RPM package management system also helps resolve dependencies and conflicts with files and libraries.

Network settings and many other MS/Windows parameters require a reboot to take effect. This is also true when MS/Windows registry settings are modified. Linux is modular enough to allow the particular service (i.e. networking) to be cycled without shutting down the entire computer. Linux also has many kernel parameters which can be set through the "/proc/" interface to allow dynamic changes to a running kernel. This greatly increases Linux system uptime and eliminates the time wasted performing system reboots.

The file system directory structure is completely configurable and not limited to drive letters such as A, C or D as a top level mount point. Thus MS/Windows has a limit of 23 mount points. (22 + Floppy: A, B & System: C & DVD/CD: D.) Note: MS/Windows Server 2003 Server and Datacenter Edition can use volume mount points to get around this limitation. Linux file system mount points can be created at anywhere in the directory hierarchy. Multi-user versions of MS/Windows such as the server edition will allow a single user to map a network file system to a letter which is a local mount point. The MS/Windows OS will not allow a second user to map the same letter. Thus if an application is configured to read data from this mount point, the application is immediately limited to operation by a single user. The Linux/Unix file system is network enabled (using NFS) to extend it's reach. Both directly attached storage and networked file systems are mountable at any point in the file system directory hierarchy and can be simultaneously used by all users on the system.

The kernel is at the heart of the Linux/Unix operating system. It is responsible for enabling multi-tasking, multi-user, multi-threading, multi-processing, security, interfacing with hardware and the network. It is this kernel which Linus Torvalds developed, based on the Posix/Unix design, which gives Linux its name. Shells, user applications and everything else interfaces with this kernel. Linux kernel development is currently supported by OSDL.org, a consortium of telecommunications and computer software and hardware companies. The source code is published under the GNU General Public License (GPL). This license for Open Source software has led to the rapid development, debugging, deployment and acceptance by allowing and defining terms under which people can copy, modify and share the source code.

Hardware vendors such as IBM, Hewlett Packard and SGI have bet their future on Linux. Oracle has made it their development platform and thus the platform of first release. Deployment of corporate enterprise software such as SAP and Oracle on Linux as a primary platform have ensured that Linux is a cornerstone of the corporate computing infrastructure. The open source license has rid Linux of any suspicion of monopoly extension or restrictive and expensive licensing structures. It is also the nature of the Linux open source kernel software to be more bug free and secure than its competitors, as it is reviewed by developers everywhere rather than by a limited group of security analysts. Linux has been deployed commercially on a vast array of hardware from PDA's (Sharp Zaurus) to laptops, wokstations, servers, mainframes (IBM S/390) and supercomputers (SGI Altix, Beowulf clusters) and is making its way into more devices each day (routers, satellites, automobiles, ...).

Future and advanced development is ensured as the source code is available to all. It is studied in universities and institutions worldwide. PhD candidates and corporate researchers use Linux to try advanced computing concepts. The improvements when made available, must compete with other advanced concepts, and those which withstand the rigors of first users, and scrutiny of the development community, are approved and included into the Linux kernel. Once adopted as part of Linux, they then must also continue to survive challengers. This will help ensure that Linux is always the best it can be. Developers who submit source code know that it will face scrutiny from a worldwide pool of developers and reviewers, which motivates them to put forth well-written code.

Linux is here to stay; it is getting stronger day by day, and that is good from a technical, financial and economic point of view.

Link to comment
Share on other sites

Looks like FUD can be used by both sides. :(

I'm not a M$ fanboy. I use both Win7 & Linux. They're tools. I don't favor one brand of screwdriver for the same reasons.

This article is so full of lies I don't know where to start.

Network settings and many other MS/Windows parameters require a reboot to take effect. This is also true when MS/Windows registry settings are modified.

False. The only time a reboot is required is when the change affects the currently logged in user permissions or when a change to an in-use file is required. Linux acts in a similar way when applying patches. The changes are either applied immediately to files not in use or 'staged' for the next reboot for core system files.

Multi-user versions of MS/Windows such as the server edition will allow a single user to map a network file system to a letter which is a local mount point. The MS/Windows OS will not allow a second user to map the same letter.

False. In my organization we've been mapping drive letters in the user space in our multi-user environments for at least the past 6 years. On 2k3 server/XP through 2k8 server/Vista configurations. All works perfectly fine.

We always use the same 3 letters (of course others are available): O-Official, R-Restricted, S-Shared. All are available to each machine regardless of how many users are logged in at the same time.

Damn, even my home network works fine mapping my two NAS shares to multiple users AT THE SAME TIME.

Although I agree that hard-mapping A & B to a non-existent floppy drive is just plain stupid for a modern OS.

Hardware vendors such as IBM, Hewlett Packard and SGI have bet their future on Linux.

Again false. No company "bets their future" on one technology. The phrase "all the eggs in one basket" comes to mind.

I don't have time to pick out all the lies in this (old?) article but there are loads more. In fact, the whole article stinks like bullsh*t and is probably just troll-bait.

Linux has one MAJOR downfall that WILL prevent it from going mainstream (if it hasn't killed it's chances yet). And that is OS fragmentation. (Android is just beginning to see this affect)

If you install an app written for "MacOS" or "Windows", it will work on that platform.

Try doing that for Linux and be prepared to answer way more questions than you should need to.

1) what distro?

2) what architecture?

3) what package type?

4) what package manager?


If Linux is to succeed, then the core upstream vendors (RedHat, Debian, Gentoo, Slackware, etc.) need to get together and UNIFY the application installer spec. I shouldn't have to care if an app is distributed as a .deb, .rpm, .tar.gz, or any other package types. Once the core vendors step in line, the rest of the downstream distros will also.

I should just be able to download, click, and run.

Until that happens, Linux will ultimately fail on the desktop.

Edited by Mr_Smartepants
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...