SoluWorks Company blog

Dear Customers,

This is to inform you of a recent migration affecting your domain name(s).

No changes are required on your part.

Your website(s)  now resides on a sever of the following specifications:

Dual Processor Quad Core Xeon 5520 (16 CPU Threads)
12 GB DDR3 Registered 1333 RAM
4x500GB RAID-10 Storage
cPanel with RVSkin

The above specifications are over four times as powerful as our previous configurations. We strive to be at the cutting edge in server technologies to order to serve you better as our client. In addition to making your services more reliable, they are more energy efficient and come pre-loaded with a much stronger spam protection software suite.

All combined, you are guaranteed a far superior experience on this hardware. If you have any questions or comments, please feel free to contact our support team at any time.

For more information on these migrations please see contact us by opening a ticket at the following links:
http://www.soluworks.com/contact-us.html

You can also discuss any issues or related server performance issues on the forum at http://forums.soluworks.com/viewtopic.php?f=4&t=6

If you noticed any issues/problems with your migration please contact our Technical Support by Opening a Ticket immediately.

Thank you!

SoluWorks Tech Team

Date: Sunday, 07 March 2010 – 14:00 – 15:30
Room: Shimba

Remote Participation – Low Bandwidth
Audiocast: English 16kbps
Chat Room: http://nbo.icann.org/chat/shimba

Remote Participation – High Bandwidth
Audiocast: English 64kbps
Virtual Meeting Room: http://icann.na3.acrobat.com/shimba/
Two-Way Audio (Remote Dial-In / Teleconference): Contact session leader for details.Transcript to be provided

What it is | An open workshop on issues relating to the delegation, redelegation and retirement of ccTLDs.

Why it’s important | The ccNSO has established a Working Group to look at the Delegation, Re-delegation and Retirement of ccTLD’s, essentially reviewing the existing policies and guidelines used by IANA, and comparing these to the actual procedures adopted by IANA. The working group’s aim is to make recommendations to the ccNSO on any gaps between policies and practices, and is not empowered to engage in any policy development process.

While the working group can not have any specific delegation, redelegation or retirement procedure re-litigated, members of the working group are interested in specific issues that have arisen in the past, where ccTLDs have been through this process.

The Working Group is convening a 90 minute open workshop to be held on Sunday 7 March (14:00 – 15:30 hours, local time) at ICANN Nairobi, and invites stakeholders to provide presentations on issues relating to the delegation, re-delegation or retirement of ccTLDs, and their experiences with IANA. Stakeholders may be any group comprising the local Internet community.

Presentations should be concise, and will be confined to a maximum of 10 minutes per speaker, and should seek to address any perceived shortfalls between the policies and guidelines (including RFC1591, ICANN ICP1, and the Government Advisory Committee Principles on delegation and re-delegation of ccTLDs) and the actual procedure used by IANA. The session will be, at a minimum, audio recorded, and remote participation will be enabled.

This Working Group is a large and diverse group who would appreciate the opportunity to hear from the ccTLD community.

Who should attend | ccTLD managers, Government, people interested in the topic – Details >> http://nbo.icann.org/node/8902

ASF Flagship Project is World’s Most Popular Web Server, Powering More than 112 Million Websites

FOREST HILL, MD, 23 February, 2010 — The Apache Software Foundation (ASF) — developers, stewards, and incubators of 138 Open Source projects — today announced the 15th anniversary of the Apache HTTP Web Server.

The ASF’s first project became the world’s most popular Web server software within the first six months of its inception. The Apache HTTP Server today powers nearly 112 million Websites world-wide.

A triumph for the all-volunteer Foundation, the Apache HTTP Server reliably delivers petabytes of data across the world’s most demanding uses, including real-time news sources, Fortune 100 enterprise portals, cloud computing clusters, financial services platforms, mission-critical military intelligence applications, aerospace communications networks, and more. The server software can be downloaded, modified and installed by anyone free of charge.

History

The Apache Server started as a fork (an independent development stream)
of the NCSA httpd, a Web server created by Rob McCool at the National Center for Supercomputing Applications.  Further development to the server ceased after McCool’s departure from NCSA in 1994, so an online community of individuals was formed to support and enhance its software via email collaboration. The founding members of that community (the Apache Group) included Brian Behlendorf, Roy Fielding, Rob Hartill, David Robinson, Cliff Skolnick, Randy Terbush, Robert Thau, and Andrew Wilson.

Within less than a year of the Apache Group’s formation, the Apache server surpassed NCSA httpd as the #1 server on the Internet.

In March 1999, members of the Apache Group formed The Apache Software Foundation to provide organizational, legal, and financial support for the Apache HTTP Server. An additional goal for the Foundation was to serve as a neutral, trusted platform for the development of community-driven software.

Growth, the “Apache Way”

Beyond the Apache HTTP Server, dozens of ASF projects – from build tools to Web services to cloud computing and more – lead the way in Open Source technology.

At the ASF, community plays a vital role in the collaborative development of consensus-driven, enterprise-grade solutions. The number of projects led by the Apache community has grown from the singular Apache HTTP Server at the ASF’s inception in 1999 to nearly 140 projects today.

The ASF’s commitment to fostering a collaborative approach to development has long served as a model for producing consistently high quality software and helping advance the future of open development. Through its leadership, robust community, and meritocratic process known as the “Apache Way”, the ASF continues to gain recognition as one of the most successful influencers in Open Source.

Through the Apache Way, the ASF is able to spearhead new projects that meet the demands of the marketplace and help users achieve their business goals. With the Apache Incubator mentoring more projects than ever before, the ASF continues to meet the growing demand for quality Open Source products.

“Community Over Code”: among the Foundation’s core tenets is open collaboration through respectful, honest, technically-focused interaction. The ASF’s success is testament to its outstanding community efforts that serve as best practices widely embraced by organizations and individuals alike.

“If it didn’t happen on-list, it didn’t happen”: building upon the transparency-oriented culture of the Apache Group, whose collaboration took place on email lists, millions of messages are archived on Apache publicly-accessible mailing lists, documenting the ASF’s achievements over the past decade.

“Meritocracy in Action”: the ASF’s tagline reflects an average of 10,000 code contributions (commits) made each month. The ASF is responsible for millions of lines of code by more than 2,000 ASF Committers and countless contributors across the Open Source landscape. Nearly 500 community-driven modules have been developed to extend functionality of the Apache HTTP Server alone.

Milestones  — Read details >

Mike Muuss authored the PING Program. Interesting read from his website.

Sadly, Mike Muuss was killed in an automobile accident on November 20, 2000.
His work lives on in testament to his intellect and indomitable spirit — Lee A. Butler

Yes, it’s true! I’m the author of ping for UNIX. Ping is a little thousand-line hack that I wrote in an evening which practically everyone seems to know about.

I named it after the sound that a sonar makes, inspired by the whole principle of echo-location. In college I’d done a lot of modeling of sonar and radar systems, so the “Cyberspace” analogy seemed very apt. It’s exactly the same paradigm applied to a new problem domain: ping uses timed IP/ICMP ECHO_REQUEST and ECHO_REPLY packets to probe the “distance” to the target machine.

My original impetus for writing PING for 4.2a BSD UNIX came from an offhand remark in July 1983 by Dr. Dave Mills while we were attending a DARPA meeting in Norway, in which he described some work that he had done on his “Fuzzball” LSI-11 systems to measure path latency using timed ICMP Echo packets.

In December of 1983 I encountered some odd behavior of the IP network at BRL. Recalling Dr. Mills’ comments, I quickly coded up the PING program, which revolved around opening an ICMP style SOCK_RAW AF_INET Berkeley-style socket(). The code compiled just fine, but it didn’t work — there was no kernel support for raw ICMP sockets! Incensed, I coded up the kernel support and had everything working well before sunrise. Not surprisingly, Chuck Kennedy (aka “Kermit”) had found and fixed the network hardware before I was able to launch my very first “ping” packet. But I’ve used it a few times since then. *grin* If I’d known then that it would be my most famous accomplishment in life, I might have worked on it another day or two and added some more options.

The folks at Berkeley eagerly took back my kernel modifications and the PING source code, and it’s been a standard part of Berkeley UNIX ever since. Since it’s free, it has been ported to many systems since then, including Microsoft Windows95 and WindowsNT. You can identify it by the distinctive messages that it prints, which look like this:

PING vapor.arl.army.mil (128.63.240.80): 56 data bytes
64 bytes from 128.63.240.80: icmp_seq=0 time=16 ms
64 bytes from 128.63.240.80: icmp_seq=1 time=9 ms
64 bytes from 128.63.240.80: icmp_seq=2 time=9 ms
64 bytes from 128.63.240.80: icmp_seq=3 time=8 ms
64 bytes from 128.63.240.80: icmp_seq=4 time=8 ms
^C
----vapor.arl.army.mil PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 8/10/16

Details >> http://ftp.arl.army.mil/~mike/ping.html

That’s right, SoluWorks is now on Twitter!

Please follow us at: http://www.twitter.com/SoluWorks

You will always find important updates, network notifications, and much more on our twitter. The main thing being network notifications as it’s not hosted on any of the SoluWorks networks so in case of emergency you can always check twitter.