Mainframe vs. xSeries 3285
 |
part of the issue in timesharing was that there was a much greater need to separate system command&control from system use. the desktop systems were able to greatly simplify because that separation wasn't really required.
I first installed Linux at around kernel 0.12; back then there were no distributions as such (in fact, there weren't even basics like login) and you built your system pretty...
however, when attachment of desktop systems to networks expanded from purely local non-hostile environment to world-wide, and potentially extremely hostile environment, some of the parbreastioning requirements re-emerged. to some degree the network attachment allowed remote attackers to reach into many of the desktop systems ... these hadn't provisions for separation-parbreastioning of system use and system command&control (they hadn't been designed and built from the ground up with extensive countermeasures to hostile attacks).
in the past, virtualization has been used for variety of different purposes; 1) timesharing services, 2) simplification of testing operating systems, 3) using different operating systems and operating environments, as well as 4) providing parbreastioning and separation of system command&control from system use.
On Thu, 27 Apr 2006 05:01:33 -0000 ^^^^^^ Those would be the old style CDs in rigid plastic cases a bit over three inches square ? Or perhaps the older ones...
some of the current activity is layering some additional parbreastioning of system command&control (from system use) to environments that weren't orginally intended to operate in such hostile and adversarial conditions (might be thought of as akin to adding bumpers to horseless carriages).
past postings on this topic:
--