Letter to the US Department of Commerce on Exporting Linux to Iraq
Silicon Valley Linux Users Group
99 E. Middlefield Road #17
Mountain View, CA 94043
December 9, 2003
Ms. Sheila Quarterman
Regulatory Policy Division
Bureau of Industry and Security
Department of Commerce
P.O. Box 273
Washington, DC 20044
Re: Comments on foreign policy-based export controls
Dear Ms. Quarterman,
On behalf of the Silicon Valley Linux Users Group, I would like to thank you for the opportunity to comment on the "Effects of Foreign Policy-Based Export Controls" published in the October 21, 2003 Federal Register (68 Fed. Reg. 60050).
Headquartered in San Jose, California, the Silicon Valley Linux Users Group (SVLUG) is the oldest and one of the largest Linux user groups in the world. It is a group of hobbyists, professionals and enthusiasts in the vicinity of San Jose, California, which is also internationally known as Silicon Valley. SVLUG members share interests in Linux and other free, or open source, software. The group was originally formed in 1988 as the PC-Unix Special Interest Group of the Silicon Valley Computer Society.
SVLUG would like to provide comments on Section 746.3 of the EAR regarding the foreign policy controls for Iraq. SVLUG believes that open source code and the corresponding object code resulting from the compiling of such source code should be exempt from the licensing requirements for Iraq.
Linux is the Free/Open Source UNIX-like operating system kernel that runs on many modern computer systems. Linux is available under the GNU General Public License, which means that users may freely copy, change, and distribute it, but must make source code available to recipients and may not impose any restrictions on further distribution. Linux does contain some security features that use encryption. As such, it is classified under ECCN 5D002. Because Linux is open source, it is eligible for export under License Exception TSU in accordance with 15 CFR 740.13(e).
On May 7, the President exercised his authority under the Wartime Supplemental Authorization Act of 2003 to suspend most of the provisions of the Iraq Sanctions Act of 1990. On June 27, 2003, the Treasury's Office of Foreign Assets Control (OFAC) published an interim final rule (68 Fed. Reg. 38188) amending the Iraqi Sanctions Regulations, 31 CFR part 575, to include a general license authorizing certain new transactions. The export of items controlled by the Department of Commerce was addressed in 31 CFR 575.533(b)(2):
The exportation from the United States or, if subject to U.S. jurisdiction, the exportation or rexportation from a third country to Iraq of any goods or technology (including technical data or other information) controlled by the Department of Commerce under the Export Administration Regulations (15 CFR chapter VII, subchapter C) for exportation to Iraq must be separately authorized by or pursuant to this part.
The term "controlled by the Department of Commerce" means subject to a license requirement under the Department of Commerce's Export Administration Regulations (EAR). Items subject to a license requirement under the EAR include items on the Commerce Control List that are listed in 15 CFR 746.3 as requiring a license for exportation or reexportation to Iraq.
Under Section 746.3 of the EAR, an export license is required to export or reexport to Iraq any item on the CCL containing a NS Column 1 in the Country Chart Column of the License Requirements section of an ECCN. Software classified under ECCN 5D002 is controlled for NS Column 1.
It is important to note that proprietary operating system software such as Microsoft Windows and Sun Solaris have been classified as mass-market encryption products and are eligible for export under ECCN 5D992. These products may be exported to Iraq without a license under the interim final rule (68 Fed. Reg. 38188) amending the Iraqi Sanctions Regulations.
Under the provisions of License Exception TSU, open source and the corresponding object code may be exported to all destinations except Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria. Thus, open source and the corresponding object code are treated as if subject only to AT (anti-terrorism) controls. Items subject to AT controls may be exported to Iraq under the interim final rule (68 Fed. Reg. 38188) amending the Iraqi Sanctions Regulations.
It is incongruous that publicly available software such as Linux has more restrictions than proprietary operating system software. Thus, we respectfully suggest that BIS amend Section 746.3 to permit exports to Iraq of open source and the corresponding object code.
In the alternative, we suggest modifying Section 740.13(e)(4) to permit exports to Iraq. This would reflect the change in policy toward Iraq allowing AT controlled items to be exported to Iraq.
Thank you for the opportunity to submit these comments. We hope they prove helpful and would be pleased to discuss them in more detail with you. If you have any questions, you may contact me at 650-967-1840 or via e-mail at firstname.lastname@example.org.
Silicon Valley Linux Users Group
Don Marti is Editor in Chief of Linux Journal.
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader 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