Monday, December 3, 2012

El Reg Movember lads sprout mighty Unix beards for cancer charity alert print comment Your LAST CHANCE to donate cash to razor-free fundraiser

What is it about facial hair and computing? From the greats of SmallTalk and C++ to Java and Ruby, beards and moustaches are not a rare sight in the world of computer science.

James Gosling, Barjne Stroustrup, Alan Kay and Yukihiro "Matz" Matsumoto have expressed their genius not just through the curly braces in the machine but also the curly wurlies on their chins.

From data centers to dev teams, from the Ruby hipsters to Unix admins, top-lip warmers and jowl scratchers are more than well represented.

Inspired by these legends, El Reg staffers have been sending their top lips into the world unshaved for the whole of November in the name of a good cause: Movember.

The Reg Movemberists have been growing their tashes to raise money for the global fight against testicular and prostrate cancer. One in nine UK men will be diagnosed with prostate cancer in their lifetime, according to the Movember movement.

So far our Movemberists have raised £392. Last year, Mo Bros and Mo Sisters across the world raised £79.3m; this year we’re all hoping for more.


Monday, November 19, 2012

Setting limits with ulimit

Administering Unix servers can be a challenge, especially when the systems you manage are heavily used and performance problems reduce availability. Fortunately, you can put limits on certain resources to help ensure that the most important processes on your servers can keep running and competing processes don't consume far more resources than is good for the overall system. The ulimit command can keep disaster at bay, but you need to anticipate where limits will make sense and where they will cause problems.

It may not happen all that often, but a single user who starts too many processes can make a system unusable for everyone else. A fork bomb -- a denial of service attack in which a process continually replicates itself until available resources are depleted -- is a worst case of this. However, even friendly users can use more resources than is good for a system -- often without intending to. At the same time, legitimate processes can sometimes fail when they are run against limits that are designed for average users. In this case, you need to make sure that these processes get beefed up allocations of system resources that will allow them to run properly without making the same resources available for everyone.

To see the limits associate with your login, use the command ulimit -a. If you're using a regular user account, you will likely see something like this:
$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 32767
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 50
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
One thing you might notice right off the bat is that you can't create core dumps -- because your max core file size is 0. Yes, that means nothing, no data, no core dump. If a process that you are running aborts, no core file is going to be dropped into your home directory. As long as the core file size is set to zero, core dumps are not allowed.

Tuesday, November 6, 2012

Learning Unix for OS X Mountain Lion

This was a perfect size book for what I needed. What I needed was a book that would get me back up to speed quickly on UNIX. I have not used UNIX since the late 80's, and I have not used Mac since the early 90's.

The book starts off with a nice introduction to you Unix and why you would want to use it. The second chapter using the Terminal, is a nice introduction to Terminal's capabilities and shows you how to customization.

After the first two chapters the book starts digging into the details of what you can do with Unix on the Mac. I have listed the chapters below.

1. Why Use Unix?
2. Using the Terminal
3. Exploring the Filesystem
4. File Management
5. Finding Files and Information
6. Redirecting I/O
7. Multitasking
8. Taking Unix Online
9. Of Windows and X11
10. Where to Go from Here

As you can see from the chapter names the author covers some of the most important topics you need to know with a chapter dedicate to each.

The only chapter that is not completely clear on what it covers is Taking Unix Online. That chapter digs into remote login, web access, and FTP.

Although the book talks about using the code samples that come with the book, I could not find any online. That did not take anything away from the book. The samples are short enough to be able to type them yourself. I found that I wanted to read this book with my Mac turned on to try the different samples that the author covered.

The author has a great writing style that makes the book an easy read. I have some other UNIX books where that is not true.

Overall I think this is a great book for getting up to speed with UNIX quickly. This book along with my Macintosh Terminal Pocket Guide have covered everything that I had to look up to date.

Source  http://www.sys-con.com/node/2431885

Wednesday, October 10, 2012

The true legal vulnerability of Linux

A recent focus on the problem of software patents raises the question: could Linux be sued off the face of the Earth?

The not-so-random thought came up this weekend when I read the New York Time's special report, "The Patent, Used as Sword." This article, which I highly recommend you read when you get a chance, comprehensively examines the broad landscape of software patents without really coming down too hard on one side or the other. It does, I should add, leave you with the sense that something is wonky with this whole idea that billions can be spent and companies can go down just because one side's lawyers are quicker on the draw than others.

If I were the uncharitable type, I would say that this is also the article that shows where The Times finally gets a clue, but that's not really the case. The staff at the Grey Lady knows full well what's going on in the land of software patents, having covered it for quite some time. But reading the piece, I could now help but feel a little sense of relief that the Times was finally giving the topic the level of detail that a lot of us in the tech media have been hollering about for years.

I hope that the increased attention on the issue helps bring some pressure on the patent system to bring some real reform. But then I also hope I'll win the lottery, so there's that.

Reading some of the ugly anecdotes of companies going down, it was very hard not to imagine someone pulling the trigger like that on a Linux company. Which led to the central question of this blog: why hasn't someone fired the litigious missiles at Linux yet, and is it just a matter of time before Linux gets big enough that someone will make the effort?

Well, for one, companies have come at Linux already, and thus far their efforts have been either blocked in court or elegantly countered. 

The first, and most infamous major example of this was, of course, The SCO Group's clumsy attempt to try to muscle Linux users into a licensing program based on the (wrong) premise that they (a) owned the rights to Unix and (b) Linux infringed on Unix and therefore Linux users owed SCO some coin. (For further background, see Groklaw. Pretty much all of it through 2010.)

Now, as we all know, in 2003 SCO went after some big-pocketed customers (AutoZone and DaimlerChrysler) and the richest Linux player at the time, IBM. This would be the first real case that all of us at the time were waiting for and dreading: Linux now had some money behind it, and now someone wanted to get their share.

But then things went sideways for SCO, and the real test of the case, that Linux allegedly infringed on Unix, never got a strong test in court. Novell started making noises that SCO did not have the right to sue on the basis of the Unix copyrights because, lo and behold, Novell still owned those rights. SCO immediately sued Novell to shut them up and maintain that it owned Unix… and lost. 

Crash, boom, bye bye SCO.

There have been others, mostly directed at Red Hat, which has established that there's gold in them thar hills, and therefore the inevitable lawyers chasing after what they can get. Red Hat successfully fended off Acacia-owned IP Innovations in a 2010 East Texas jury trial (I know, go figure!), invalidating three of IP Innovations' patents.

But later that same year, Red Hat would settle with another Acacia-owned company, Software Tree LLC, for an undisclosed amount. 

Early in 2010, Red Hat was dragged into Canadian company JuxtaComm-Texas Software LLC's infringement claims for a patent (US Patent No. 6,195,662) covering the manipulation and exchange of data between computer systems, along with companies like British Air. A quick check of Pacer reveals that while that case in the Eastern Texas district court ended just last month, Red Hat seems to have settled again on August 22, 2011.

That's too bad, because in July of this year one of the other remaining defendants in the case, Pervasive Software, blew a hole in two claims within '662 and rendered the patent invalid. On September 19, JuxtaComm would end up being ordered to pay the remaining defendants' court costs.

Red Hat doesn't always settle… in another case it's defending itself against from Twin Peaks Software, Red Hat took the unique step in defending itself from a patent infringement claim by leveling a counterclaim that Twin Peaks is in copyright violation on mount, the file management app that is licensed under the GPLv2. Not only is Red Hat seeking GPL compliance, it's also going after Twin Peaks for damages and is seeking an injunction on Twin Peaks' own product sales.

On one level, using the GPL as a weapon is pretty funny, but in seriousness it really only work against companies that are actually practicing entities, not the non-practicing entities colloquially known as patent trolls.

It should not be taken away from this article that I'm picking on Red Hat. But as the most visible Linux player these days that's making some real money, Red Hat will no doubt find itself embroiled in other lawsuits.
But what about the Big One? The mother of all lawsuits destined to Destroy All That Is Penguin?
Many in the Linux community believe that, as a proxy for Microsoft, that SCO case was just that. Rather than the death through a thousand cuts approach all of these individual trolling cases seem to be taking, the SCO case was the biggest concerted effort against Linux that would have (if they could have pulled it off) potentially put Linux under the boot of a decidedly unfriendly company. But the case was bungled so badly, if there was a conspiracy, then I have little doubt that the actors in such a cadre were left feeling very burned by the experience.

Does that mean the Big One will never come? No one can predict for sure, but I have a gut feeling that no, it won't really happen. While there will always be the odd troll, I don't think it's in the interest of a major competitor to try a take down of Linux in the courtroom.

Why not? Simply because Linux is so pervasive now. Suppose patentgeddon did somehow happen, and Linux were forced to change drastically in order to comply? Do you know how many core infrastructures would be blown up were that to happen? And where would these IT departments go? To Microsoft? To Oracle? If one of these companies happened to be the Plaintiff, then I think not. More likely Linux customers would be so angry at having to give up or overhaul their Linux machines, they would start to resent said Plaintiff's products with a vengeance.

And then there's the simple reason of: why bother? Why would Microsoft try to destroy Linux when it can simply co-opt the technology and use it within its own products as needed? In fact, that's exactly what the company is doing, and is actually becoming a larger player in the Linux kernel space.
Free software, whether as in freedom or as in beer, just makes it less productive to mount a shock and awe campaign.

That's not to say Microsoft and other players won't keep trying to whittle away at Linux through various licensing campaigns and veiled threats. This is a war of slow attrition and the ultimately the goal will not be the destruction of Linux, but the control.

Wednesday, September 26, 2012

Army releases $5B ITES hardware RFP

The Army has released the solicitation for its $5 billion Information Technology Enterprise Solutions 3- Hardware contract.
Proposals for the five-year contract are due Oct. 22.

The Army will use the contract, known as ITES-3H, to buy a variety of IT equipment to support the Army’s IT infrastructure. The hardware has to be compatible with the Army’s network operations and net-centric operations.

The equipment to be purchased will fall into nine broad categories, such as Unix and non-Unix services; workstations, desktops and thin clients; storage systems; networking equipment; video equipment; and cable, connectors and accessories.

The contract will have multiple winners, who will compete with each other for task orders. ITES-3H has a three-year base and two one-year options.

ITES-3H replaces ITES-2H, which is held by CDW, Iron Bow Technologies, Dell Inc., GTSI Corp., IBM Corp. and World Wide Technology.

According to Deltek, $4.1 billion in task orders have been awarded under the contract over the last five years. Iron Bow and World Wide have captured the most business, each taking in over $1 billion in awards. IBM had the lowest amount with $136.6 million in business.

Source  http://washingtontechnology.com/articles/2012/09/25/ites-3h-solicitation-released.aspx

Sunday, September 9, 2012

Enterprise Networking: Centrify Brings Centralized User Management to Heterogeneous Networks

Sold in suite form, Centrify Suite 2012 Enterprise Edition brings several elements together to create a user and system management suite that leverages Active Directory while incorporating Linux/Unix/Macintosh systems into the mix. Centrify's centralized user management helps tame the new security paradigm created by multidevice user access scenarios to servers, applications and endpoint systems in the cloud and on-premises. The product's centralized management screen makes it easy to define roles, groups, zones and other container-level directory elements, while incorporating a single sign-on methodology for end users. With Centrify Suite 2012 Enterprise Edition, administrators can remotely deploy software, as well as enable advance auditing capabilities, transparently to users of Windows, Linux, Unix and Macintosh systems and servers. Unlike meta-directory synchronization tools, Centrify brings direct integration capabilities, allowing just a single directory to hold all account data, eliminating the need for cross directory synchronization.   

Wednesday, July 25, 2012

Zsh gets new stable release after four years

The developers of the Z shell have announced the release of zsh 5.0.0, the first major stable version of the tool since zsh 4.2 was released in 2004. Zsh is a shell for Unix and Unix-like operating systems that is mainly designed for interactive use, but is also suited to other tasks. The latest stable release of the project was zsh 4.2.7 in 2008.

The 5.0 release includes the features that have been developed in the unstable 4.3.x branch of the project; this includes support for highlighting, colour display and job control in non-interactive use. This new release also adds support for multibyte character strings. 

Version 5.0 of zsh includes new options that improve POSIX compliance, debugging and the history functions of the shell. New shell variables give users information about the current sub-shell level and the exact patch level of the tool, providing more granularity between release versions. Users can define patterns to be ignored by spelling correction. Z shell 5.0 also includes several new features that improve text completion, command evaluation and expansion of parameters. A full list of new features is available in the NEWS file for the release.

The source code for zsh is licensed under its own MIT-like licence and can be downloaded from the project's mirrors and FTP server.