Voice Your Opinion to the NIH
Editors' Note: For more information about the NIH proposal for open access, read Christopher Frenz's EOF column, "Open Access for Science", in the April 2005 issue of Linux Journal.
In recent months, open access for science has become a heavily debated topic. Many scientists are in full support of an open access publishing model, but many publishers of scientific journals remain stalwart opponents. In early February 2005, however, a partial victory towards achieving open access was scored when the National Institutes of Health (NIH) announced it had decided to establish a voluntary program that would present researchers with the option of archiving their published articles in the open electronic repository PubMed Central.
NIH's new policy is set to go into effect in May 2005, and while it represents a step in the right direction, it still is a far cry from a true open access requirement. In addition to being an optional program, the program also allows articles to be delayed for up to a year before they can appear freely, in order to protect the interests of the publisher.
The value associated with a given research paper often depends on the age of the content, with newer research results generally being of more value and interest to researchers within a given field. The original proposal had called for a mandatory program that would require all NIH-funded studies to be archived within a period of six months. Additionally, NIH policies apply to much of the biomedical research within the United States. But research in other disciplines, such as physics or computer science, largely is unaffected by these decisions, because this type of research funding often stems from other government agencies, such as the National Science Foundation.
Thus, as believers in the ideals of openness and freedom, we as Linux enthusiasts should rally behind the cause of open access to scientific literature. Doing so provides us with yet another forum for showing the world how the free exchange of ideas and information can benefit us all.
In order to voice your support of open access to the National Institutes of Health, e-mail comments can be sent to PublicAccess@nih.gov. Alternatively, you also can write to your local Congressman or Senator in support of open access, as NIH's open access plans were presented to Congress at the end of 2004. Congressional contact information can be found at www.house.gov and www.senate.gov, respectively.
Christopher M. Frenz is a bioinformaticist with more than five years of experience using Linux. He also is the author of the book Visual Basic and Visual Basic .NET for Scientists and Engineers (Apress) and currently is writing a book about Perl programming.
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- 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