Slashdot Mirror

See the article http://www.computerwire.com/industries/research/?p id=9681B83E-A348-42A5-9DA5-BEF13EE1A835 -- they maintain SCADA systems that may originally have been on a separate physical network have slowly bled connectivity to corporate networks and are now open to those who compromise those networks.

They also describe a Hewlett-Packard/SenSage software package to monitor in real time and also archive network events on SCADA networks -- allowing for real time alerts of ongoing crimes, or at least an archive of all activity related to external or insider bad activity. Historical analysis at all network levels (physical, computer, server process levels) is very important -- without it you can't find the perps or track how they compromised your network.

Assuming you run ten RHEL guest instances per server, that means a saving of $7990/$12990 pa per server.

Not to mention that XEN itself doesn't cost anything extra, unlike VMWare. Having said that, VMWare ESX is certainly in a different class to XEN and has a much better support for enterprise environments. But XEN's improving and this licensing change will show large license cost savings for migrating to XEN.

I would have no objection to to MS totally taking security in house. Locking down the kernel and only allowing API access would eliminate most of the defects in Vistos. The only difference is the end use pays MS a yearly subscription instead of McAfee $274.5, Symantec $4.14 billion) and the rest. Of course charging after the fact for defects in the product is a very odd way of doing business. Myself don't plan to pay either of them a cent for 'security'.

I just posted a similar thing to an individual post, but I think it's more appropriate to this thread

This is nothing new, it's just a repeat of the previous analysis of SCO's slides, but since a lot of people haven't read the whole article in question, they're just getting information from these partial posts people are making here and forming opinions based on that.

Please, everyone, look at the Original Article before posting. Or, if you don't want to register with computerwire, the article also posted on Yahoo. Perens is talking about the code snippets from the slides a couple weeks ago. Nothing new. He's talking about the code that was released into the public domain by Caldera.

SCO's including a partial quote from Perens without context. This is why partial quotes are dangerous. You get to see the included line, but not the context so it makes it look like someone said something completely different, which in this case is McBride's purpose.

So, read the original article from Perens, and read the Letter from McBride. And please, if you're going to make a post using a quote, make sure it represents the whole idea, otherwise it could end up meaning something else from what someone acutally said.

Other column-oriented databases? Yes, there is Sybase IQM and Alterian. Sometimes they are mistakenly called tokenized dabatases, but is that a misnomer (it is really an orthogonal feature as Aruna shows being a tokenized databased, but not column-oriented). KDB is the fastest, smallest, and simpliest though (most of the time this simplicity is good, but sometimes it is bad). I don't know of any free versions. It might make a good project, since they are (I think) conceptually easier than the standard row-oriented B-Tree based systems.

Here is an older article on KDB and a high-level view of some of the tricks that it uses: Kx Systems: The Lord Nelson Of Software Companies?

I received an e-mail from William Fallows, the US editor of Computergram, giving me permission to post the complete article, which you'll find below.

For that, I figure it's worth allowing Computerwire a plug - I received an e-mail from Richard MacPherson, the West Coast Accounts manager of Computerwire, offering businesses a 10 day free trial of their various publications. See the web site or send him an e-mail for more detail.

SUN PLANS OPEN SOURCE SOLARIS
Sun Microsystems Inc is working on a strategy that will enable it to move its Solaris Unix to the open source development model without stepping on the toes of the Linux community and being branded the evil empire. It says that its dilemma is that
"Linux is good for Solaris, but that Linux is not a corporate community" and "our intentions must not be misunderstood." One route would be to turn over Solaris intellectual property and source for development by the open source community but retain all branding, packaging and testing considerations, as with its Java community source model. However, Solaris isn't as young as
Java and Sun is not sure what the effect might be on its large code set and hefty installed base. Other major considerations include the paper chase of royalty, IP and branding rights in the agreements it has made since buying out its Unix license from Novell Inc in 1994 for $82.5m. It is looking for anything that could prevent it taking Solaris open source, such as rights that may belong to other companies. Sun, which is already making Solaris APIs compatible with Linux, says it is also still working out how it will market the initiative and what image it wants to present. It expects to move quickly but until there's a method "we can't say bombs away," it says.