News from the Rookery
Vocalizations! "Unfortunately, these interfaces come with a common problem in the high tech world. Quoting Dr. McCoy as he returned to the Enterprise in Star Trek I: 'I know engineers; they looooove to change things.' And in their current states, GNOME and KDE are constantly changing. The reason for this is that engineers are building what they basically don't want to use for those who don't want to use it. It's hard to find something that satisfies both ends of the equation ..." Michael J. Hammel, Linux Evangelist and Author, from his article, "The 30-Year Cycle of Acceptance, and Why Linux Is Immune" posted at Linsider.
Clever M$ Hackers Open Door for Crackers: Sometimes even the smartest among us can out-think themselves. Microsoft confirmed yesterday that engineers added a secret password--allegedly a phrase close to "Netscape engineers are weenies"--that could be used to gain surreptitious access to thousands of Internet sites. Manager of Microsoft's security-response center (no part time job this one), Steve Lipner, reportedly noted that such a password would be "absolutely against our policy" and called the inclusion of the password a "firing offense." And the company has encouraged its customers to delete the file "dvwssr.dll" in which the witty "you suck/we rule" style quip was hidden. According to the CBS MarketWatch story, the security flaw is limited to Microsoft's Front Page 98 extensions, and is not a part of W2K. The password allows crackers potentially to gain access to web site management files, through which crackers could access such personal information as credit card numbers. Moral for Microsoft: smackdowns make poor software.
Pulling Standards Out of a Hat: Yesterday, the Rookery brought you news from the Linux Standard Base announcing the release of the File Hierarchy Standard, Version 2.1. The goal of the Linux Standard Base is, among other things, to help prevent the sort of fragmentation that plagued UNIX by encouraging compatibility among Linux distributions. According to much of the buzz on the Internet, FHS 2.1 is an excellent example of the sort of compatibility worth encouraging. FHS 2.1 will standardize the placement of files in Linux distributions, to avoid what OSOpinion writer, Nikato Muirhead called "the problem of files being in different locations on different implementations of Linux." Nikato notes that many of the most popular Linux distributions--Corel, Stormlinux, Debian "and the other Debian based distributions"--will adopt the LSB and, by default, FHS 2.1. Notably absent from this list, is Red Hat. Nikato continues by saying that when he queried Red Hat co-founder, Bob Young, about Red Hat's adoption of the LSB, Bob answered that Red Hat was the market leader. Multiple mental question marks ensued. But for anybody who is wondering just what Bob might have meant, the answer is fairly obvious: Red Hat is, for mass consumption purposes, Linux. And when Red Hat says that it isn't competing with other Linux distributions (and is, instead, only competing with Microsoft), it isn't necessarily because they're being nice. The reason is that Red Hat isn't wasting time looking over its shoulder at what it considers also-ran Linux distros. To be sure, Red Hat has endorsed the LSB before (read what Donnie Barnes had to say to Linux Journal in our Standards issue last June). But that was a far different Red Hat in the pre-IPO, summer of 1999 from the Red Hat we have now--sitting astride the Linux distribution market as the most recognizable version of the operating system outside of the Linux community proper. Certainly Red Hat has become a Linux "market leader". The question is whether this will encourage Red Hat to lead Linux distributions toward non-Red Hat-centered standards, or deliver them to the doorstep of fragmentation.
VA Linux Left Out? Earlier this week, the Rookery mentioned a report from IDG announcing dramatic increases in server shipments from the close of 1998 to the close of 1999 (a 166% jump, to be specific). On IDG's list, Compaq led the field with 25% market share for Linux servers, with IBM coming in second at 10%. Others mentioned with smaller market penetration included Hewlett-Packard, Dell and Fujitsu Siemens. But the omission of Linux hardware companies like Penguin Computing and VA Linux Systems caused at least some observers of the Linux server boom to cry foul. A story on the subject appeared at The Register on Friday, which pointed out both that VA Linux was likely included in the report's sizeable "Other" category (which represented 43% of the Linux server market) and the time frame examined in the report, which may have excluded January 2000 sales that would have vaulted VA Linux, at least, over Fujitsu Siemens. Of course, what the study also points out are the significant challenges some of the smaller hardware companies like VA Linux Systems face in going mano a mano with hardware heavyweights like Compaq and IBM, both of whom have made their Linux commitments very clear.
Clued-in/Clued-out "(Sun) still wants to control the Java brand at all costs (because) they value the Java brand over the industry's technology. At this point, they're burning trust--they have to admit that it's proprietary or make it a standard." Simon Phipps, chief e-business "visionary", IBM, as quoted in Tech Web.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
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