Just a guess:
Client systems are decended from desktops, which were normally powered off
at the end of the day, every day. They never had the same uptime
requirements in terms of the hardware and software design. Those
requirements have been 'retrofitted' on to systems while maintaining
backward compatibility, and were not designed in from the beginning.
Then someone decided that those Clients could also themselves be Servers,
but they still had the same maintenance baggage from their Client days. I
guess that means that it's OK to have to reboot NT/2K and other PC based
server OSs ( OS/2 & Linux included if you consider lack of hot plug
hardware ) every time you need to add a network card.
my $0.02
Jay Brenneman
"Abruzzese, Pat"
<Pabruzzese@Thomc To: [EMAIL PROTECTED]
omp.com> cc:
Sent by: Linux on Subject: Down time
390 Port
<[EMAIL PROTECTED]
IST.EDU>
02/03/2003 10:12
AM
Please respond to
Linux on 390 Port
I know this is off the board but I would like to know why is the
"mainframe's" down time limited when the "client/servers"
seem to going down whenever. In the middle of the morning, afternoon or
night unscheduled. My VM/ESA 2.4.0 was IPL'ed 1/09/2002 and have been up
since. I will take it down this Sunday to put Z/VM 4.3.0 in service. Why
are
there two sets of standards???
vr,
P. Abruzzese
