So those two coroutines are still slaves to it, and any Linux hardware requests get sent through it.įor the most part, it does.

However, in order to work properly, especially since most hardware isn’t set to handle talking to two different masters in two different languages at once, the host OS still holds instructive sway. The Linux kernel accomplishes this by converting the two operating systems into equal coroutines. The term “cooperative” is meant to signify the fact that, once installed, the kernels of the Linux OS and host OS work together, communicating back and forth with each other as needed to share machine resources. Unlike other methods of virtualization, though, Linux doesn’t quite so much run “under” it as “down and across” from it. This presents its own problems, though, namely that you don’t want to have to be constantly rebooting just to switch back and forth between the two.ĬoLinux works by allowing the installation of a kernel on the host OS (usually some Windows variant, but it can be anything, so long as it sends certain types of operating data the installation needs to run). A bit more common is to have a dual-boot machine. Some users solve this with multiple machines: an answer doesn’t get much easier, but that’s certainly not the cheap route. While the strong and weak points of each are well known, the bottom line is that whichever you prefer, there is an advantage to having each of them. This means that webmasters are similarly torn. With a few UNIX, Macintosh and scattered other exceptions, the hosting world is torn between Windows and Linux.

Placing the Windows logo and Linux penguin in opposite ends of the yin yang summarizes not just this software, but the problem it is attempting to address. We describe an implementation of this proposal, which we call BodySnatcher, which has demonstrated proof of concept by acquiring memory from Windows 2000 operating systems.The logo for Cooperative Linux, more popularly known as coLinux, sums up the attempted approach to the platform. Our method is to inject an independent, acquisition specific OS into the potentially subverted host OS kernel, snatching full control of the host's hardware. Additionally the method is more resistant to subversion due to its reduced attack surface. In this paper we propose a method of acquiring the contents of volatile memory from arbitrary operating systems in a manner that provides point in time atomic snapshots of the host OS volatile memory. The emergence of kernel level rootkits, anti-forensics, and the threat of subversion that they pose threatens to undermine the reliability of such memory images and digital evidence in general. Recently there has been a surge in interest in memory forensics: the acquisition and analysis of the contents of physical memory obtained from live hosts.

Colinux 64 bit windows 7