Mainframe vs. xSeries 3282
it use to be that homework sounding questions were clustered in sept-oct timeframe with the new croup of freshman attempint to get others to do their homework.
for a whole slew of reasons ... the mainframe systems of the 60s tended to evolve a paradigm that provided clearcut design & implementation separation of command&control (of the system) from the use of the system. you saw this further evolving in the late 60s with much of the command&control infrastructure starting to be automated. part of this was number of commercial interactive timesharing use that provided 7x24, continuous operation with offshift being unattended in lights-out kind of environment
the implicit separation of system command and control (as well as automating much of the command and control functions) from system use has tended to permeate into all aspects of the design and implementations over the past 40 years.
the evolution of the desktop systems partly included the enormous simplification that could be achieved if there was no differentiation of the system command and control from the system use (i.e. single user system where the same person that used the system was also responsible for the command and control of the system).
what was the very first Linux distro 3286
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 in rather less rigid...
many of the current things commonly referred to as "servers", have tended to be platforms that evolved from the desktop paradigm with no implicit differentiation between the command and control of the system (along with little or no automation of the command and control functions) from the use of the system. many such "servers" may have a patchwork facade applied on top of the underlying infrastructure to try and create the appearance that there is fundamental separation of command and control from use (with some degree of automation). trivial scenario is frequent situations where remote user may acquire system "command and control" capability (via a wide-variety of different mechanisms)
Mainframe vs. xSeries 3283
Yes. This is another bad side effect of ATT not being in the OS biz. When you pick and choose your customers to the point of eliteness (their awful licensing scheme), your product doesn't...
the lack of clearcut and unambiguous separation of system command and control from system use ... permeating all aspects of design and implementation can lead to large number of integrity and security problems.
for instance would you prefer to have the financial infrastructure (that you regularly use,) managed by 1) dataprocessing operation that has strongly differentiated system command and control from system use or 2) a system that has constant and frequent reports of vulnerabilities and exploits.
then there are all sorts of feature-function-capability that will tend to evolve over a period of forty years ... where the operational environment includes basic premise of unattended operation as well as strong separation of system command and control from system use.
slight drift ... lots of posts on fraud, exploits, vulnerabilities, and treats
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...
misc. past posts raising the issue of answering questions that appear to be homework: replacement LOSES DATA digit lock? (or: Help, my brain hurts) solution for network intruders? national ID card? SSL located? Address for addressing the Cache main memory ? require whole program 2 b loaded in for small clusters key encryption