The term emulation means to either equal or exceed something or someone else. As computer jargon, however, emulation means recreating another computer or console’s operating system on another system; e.g., recreating a Nintendo Entertainment System on your Sega Dreamcast so you can boot up a _Super Metroid _ROM, or playing classic arcade games like _Ms. Pac-Man _or _Omega Race _on your Gameboy Advance SP. Certainly, neither Nintendo nor Sega ever meant for their systems to be used for such purposes.

For those of us who grew up in the 80s, playing games in arcades or on our computers and game consoles was a major part of our childhoods, and we often have the nostalgic desire to replay those beloved titles. Others not only want to play, but have dedicated their scholarly attention to the study and preservation of videogame history. Sometimes companies who own the copyright to these games are able to repackage them and make them available on the shelf; there are countless “Games in a Stick” mini-consoles and plenty of “Arcade Classic” compilations for the PC and modern consoles.

You are a system administrator for a small company—the captain of the firm’s computers. Doing your job well means that you may sail through the seas of information technologies unhindered, in short, the company’s IT infrastructure will stay in place. Should you mess up you will find that the email has stopped working, the web surfers are stranded and you have pinned your ship on the reefs and rocks that scatter the virtual world, or in other words, the company will not be functioning well and you be burning its money.

Free software is fast becoming the standard in quality software. It’s now possible for anyone to find a quality, free replacement for almost any proprietary program. In many cases, the free program is better than its proprietary counterpart.

You may not realize it, but there’s probably a free software replacement for every software program you own: from your word processor to your photo editor to the actual operating system.

There’s probably a free software replacement for every software program you own

I have my kids to blame, that is certain. There I was, last Christmas, in this auditorium, listening to the crunching of popcorn from my son on my left, and the slurping of soda from my daughter on the right, trying to behave like a responsible father. The lights had dimmed and we were being inflicted with the inevitable advertisements and trailers. When, at last, the fan fair that accompanied the main feature at the cinema trumpeted out of the speakers an anticipating hush spread around the audience. Even my daughter took a break from her munching.

The free culture movement is growing, from its inception in the free software movement to the relatively recent establishment of Creative Commons. Across the world, localised teams are adapting CC licenses to their particular legal systems. Record labels, indie film studios and well over 10 million web pages are using CC licenses. Are we on an inexorable ascendency? Well, not quite. In this article I will show that we still have a lot of issues to iron out.

Let us begin with a story about art. In this story, art produces aesthetic works of durability and stability — things that “stand up on their own”. The act of artistic production doesn’t come from nowhere; neither is it born in the heads of private individuals. It doesn’t dwell in a social nothingness. Nor does it start with a blank canvas. Any moment of production involves the reassembling and rearranging of the diverse materials, practices and influences that came before it and which surround it.

The free software and open source communities are changing what it means to write code. Specifically, they are extending its audience from a few fellow employees to, theoretically, anyone in the world who wants to read it. Code isn’t just for computers and colleagues anymore and, gradually, we are seeing the beginnings of a body of literary critics and an appreciative readership for source code.

Everyone is eager to virtualize their working environment to take advantage of the abstraction layer it provides. Some may require resource isolation for enhanced security, others may need development environments for testing and debugging. Whatever your needs are, virtualization will save you resources through utilizing them more efficiently. This is done by exploiting synergies built on proven technologies, improving availability and reducing downtime, adding scalability through duplication and gaining a certain degree of hardware independence.

Gains from virtualization

Back in the good old days, when men were men, women were women and the standard way for two computers to talk to each other was through a cable plugged into the serial port, was when I first took the plunge into this “internet” thingy and signed up with an ISP. Then, armed with a modem, a telephone line that doubled as a fax, Netscape 1.1 and a sense of adventure, I surfed web sites, emailed the few others I knew who had also taken the plunge and joined in on worldwide discussions on what we called “News Groups”.

Virtualization is set to become a key requirement for every server in the data center. This trend is a direct consequence of an industry-wide focus on the need to reduce the Total Cost of Operation (TCO) of enterprise computing infrastructure. In spite of the widespread adoption of relatively cheap, industry standard x86-based servers, enterprises have seen costs and complexity escalate rapidly.

Virtualization is set to become a key requirement for every server in the data center

Developing software within the free software model can be achieved with all sorts of different tools, but choosing the right tools can make a big difference to the success of your project. Even if you are developing a proprietary solution, there are benefits to using free software tools to achieve it. But what free software tools are available? In this article I’m going to look at the development tools available, from languages and libraries to development environments, as well as examining the issues surrounding the use of free software tools by comparison to their proprietary equivalents.

About one out of every 200 people is allergic to peanuts. Depending on the extremity of the allergy, a person suffering from peanut allergies who was accidentally exposed to peanuts might develop an itchy rash. Others might experience anaphylaxis, a severe reaction that can prove fatal. People who are allergic to peanuts have a tough time in America, where more and more foods are manufactured in factories that also process peanuts.

Every software developer faces a choice when deciding how to release a new software product. That choice is whether the program will be free or non-free. Unfortunately, many otherwise knowledgeable programmers aren’t sure just what this choice means, and may complain that programmers with families really don’t have a choice at all—if they want to earn a living, they must charge for their work. However, free software is not about giving software away without cost.

In a dream world, all software would be free. However, we spend enough time with our eyes open to realize that some situations call for proprietary software, either as a desktop or as a server application, on a free system. On the other hand, those stuck with a proprietary operating system can still enjoy free software applications. This article will list a few situations where free software and proprietary software can mix, and give three examples of each.

Why free and proprietary can mix

If you are reading this you probably use free software. In fact, I think the probability that you are reading this article using free software is extremely high, whether it is “free-as-in-speech” as in Firefox, or “free-as-in-beer” as in Internet Explorer. Free software is increasingly being taken for granted and is almost treated as some kind of legal right in some quarters. And so it should be. A lot of people have had to put a great deal of effort into ensuring sufficient “free-as-in-speech” software exists for this to be so.

In a recent discussion on the Slashdot web site, free software users and advocates raised the question of whether the KDE project should be ported to the Microsoft Windows platform. Advocates for porting the KDE desktop environment made the argument that porting KDE to Windows would enable a new population of users to experience the software and that this exposure would entice these new users to seek out and adopt free software for use in their daily computing lives.

Dspam filters spam with the best. In my installation, it stops over 98% of all spam: I’ve only had one false positive in the last year, and that was a message to the Dspam list that contained a real spam!

Administering Dspam is a breeze. No rules to configure, new users can automatically benefit from a global dictionary and quarantine management is simple. But getting a Dspam quarantine set up the first time, without losing any email, can challenge the most seasoned mail administrators.

If you are responsible for maintaining an internet-connected mail-server, then you have, no doubt, come to hate spam and the waste of resources which comes with it. When I first decided to lock down my own mail-server, I found many resources that helped in dealing with these unwanted messages. Each of them contained a trick or two, however very few of them were presented in the context of running a real server, and none of them demonstrated an entire filtering framework.

SMTP is an abbreviation for “Simple Mail Transfer Protocol”, and is the standard internet protocol for sending email from one system to another. Although the word “simple” belies the inherent complexity of the protocol, SMTP has proved to be a remarkably robust, useful, and successful standard. The design decisions that made it so useful, though, have given spammers and infectious code an easy way to spread their unwanted messages. Its recent evolution reflects the tug-of-war between those unsavory players and the administrators who want to protect their systems and their users.