The Future of Linux
Is Linux superior, comparable, or inferior to commercial operating systems? [or something like that]
Jeremy Allison (Samba): [I think he was one of the panelists who made the comment that “Linux is a commercial OS”; his answer amounted to choice #1:]
Linux is very standards-compliant (e.g., Posix); a good approach is to develop first on Linux, then port to a proprietary UNIX system. For example, Samba has three separate pieces of code to deal with some aspect of file-system stuff; Linux supports all three interfaces, so they just choose the one that runs the fastest.
He gave a wish list of improvements he'd like to see, though: 64-bit file-system support (“for those 20GB Exchange databases”); access control list (ACL) support; asynchronous I/O support; NFS file-locking and improved performance [amen to that]; and a thread model like Solaris.
He noted that Linux has current support for more platforms than any other OS: x86, SPARC, Alpha, Power PC, 68k, etc. Bugs are fixed the fastest, especially security leaks.
There's been a Linux “iBCS” module to support SCO UNIX binaries for a couple of years; at this year's USENIX, SCO announced (and demoed) a module to run Linux applications.
Larry Augustin (VA Research): His answer was “yes”. Linux is not (yet) as far along as Solaris in supporting 64-way symmetric multi-processing (SMP). [I thought the SPARC-based Fujitsu AP1000+ on which David S. Miller reported success last year was a big SMP box, but as Jason Riedy pointed out, it's a distributed-memory multi-computer similar to the Connection Machine CM5.]
In his slides of user ratings (Datapro survey, which was mentioned several times during the evening), Linux was not only the overall winner in a field of half a dozen operating systems (Windows NT placed last), it also won in all but two categories—and only Digital UNIX was rated higher in those two (availability and performance). The other categories included reliability, technical support, price, etc.
Robert Hart (Red Hat): Linux is a commercial operating system. It is sold and supported commercially (Red Hat, Caldera and others); it is used commercially; its only difference is that the source code is freely available.
Key “commercial OS” features like a journaling file system and database access that bypasses the file system layer are coming very soon.
Many of Red Hat's users (more with every release) have never installed an OS, which means Red Hat has to “reverse engineer” their hardware configuration.
Why is Linux not ubiquitous? It's still not suitable for everyone (he mentioned his “75-year-old mum”), and although there are good office applications for Linux, there aren't any killer ones yet. (There were follow-ups to the suitability comment by some of the other panelists.)
Sunil Saxena (Intel): He presented some slides that amounted to a “yes” response as well.
Strengths: Linux is becoming the OS of choice of ISPs; on 32-bit Intel systems, Linux has broader device-driver support than any other UNIX (e.g., SCO, Solaris/x86, etc.); its Open Source model means that updates, patches and bug fixes happen in “Internet time.”
Weaknesses: SMP support and scalability is still evolving (although he noted that Leonard Zubkoff did a successful two-day port to the brand-new, four-way Pentium II Xeon system that Intel and VA Research showed off); good server management is missing (e.g., using a remote serial line or modem to update things, including the BIOS); drivers for high-end hardware tend to be lacking; and large-memory support (say, multi-gigabyte range) isn't there.
Making it better: he said (and repeated several times throughout the evening) that Intel really wants to help and do more to support Linux, and in particular, they see the following as likely areas of collaboration:
more than 4-way SMP (serious scalability, at least 16 to 32 processors)
drivers for high-end platforms
direct server control and management
support for PII features such as 36-bit addressing (up to 64 GB of RAM), enhanced system calls and save/restore, MMX instructions, the page attribute table, and on-chip performance monitors
Linus Torvalds: He started off with a comment to the effect of, “What can I say? I came to listen to the others.”
He noted that Linux originally was a one-person OS; it was never intended to be useful to others. He also pointed out that it has just shown up on the list of the world's most powerful supercomputers (in a cluster design); he thought it made #316. [Actually #315 in the June 1998 list—see the press release for details.] At the other end of the spectrum, it's being ported to Palm Pilots. “I don't see that [its broad portability and usefulness] ending any time soon.”
He responded to a couple of Sunil's comments:
36-bit addressing on Intel: “We've been doing that on Alpha for awhile.”
Page Attribute Table: he didn't know about Intel's implementation but said that he'd suggested it to an Intel engineer a few years ago; “I don't know if they did it right, but if so, I'll be happy to use it.”
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide